Tribler 7.4.0-exp4 (special science release) is here for you. Try it out!


Dear Tribler Community,

Could you please help us with our science?

Today we are releasing a special science release of Tribler as 7.4.0-exp4. As you might already know, we ship a blockchain called Trustchain which we use for accounting Tribler token balance. Since the balance is used for paying anonymous downloading or seeding, which is used for receiving better speeds, we want to prevent attacks on our blockchain like double-spending & block hiding. At our lab, we developed a few research ideas to provide solutions. This release includes research ideas and solutions on those issues, which may be key to protecting you in the future. We would appreciate if you could try it out and let us know if you have any issues running it.

The binaries are available below or can be downloaded from the official release page at Github repository.
Windows (32-bit)

If you encounter any problems using this release, feel free to report back to us. We’ll appreciate that. You can either create an issue ticket in Github (link here) or simply reply here in this thread. We would also like to hear from you if it works well for you.

For developers willing to contribute to Tribler with bug fixes or new features please check out this page which provides the basic pointers to get started.

And as always, the source code can be found on our Github repository but you can also download it directly here.

Since the last experimental version (7.4.0-exp2) we implemented the version based state directory so it should be safe to upgrade to this version or downgrade to the older experimental version in case something goes wrong.

We hope you’ll enjoy using this version.



This version suffers from one of the same errors as Tribler 7.4.0-exp3:

Traceback (most recent call last):
  File "TriblerGUI\", line 114, in on_read_data
  RuntimeError: Unhandled Error
Traceback (most recent call last):
  File "lib\site-packages\twisted\python\", line 86, in callWithContext
  File "lib\site-packages\twisted\python\", line 122, in callWithContext
  File "lib\site-packages\twisted\python\", line 85, in callWithContext
  File "lib\site-packages\twisted\internet\", line 149, in _doReadOrWrite
--- <exception caught here> ---
  File "lib\site-packages\twisted\internet\", line 249, in doRead
  File "Tribler\Core\Socks5\", line 51, in datagramReceived
  File "Tribler\community\triblertunnel\", line 70, in on_socks5_udp_data
  File "Tribler\pyipv8\ipv8\messaging\anonymization\", line 279, in select_circuit
  File "Tribler\pyipv8\ipv8\messaging\anonymization\", line 274, in select_circuit
  File "Tribler\pyipv8\ipv8\messaging\anonymization\", line 268, in find_circuits
  File "Tribler\pyipv8\ipv8\messaging\anonymization\", line 268, in <listcomp>
builtins.RuntimeError: dictionary changed size during iteration


so you can go to line 114 in TriblerGUI\ and add a Try/Except block to the code and then add some print statements so we can find out exactly what is failing there…

the exception was caught in lib\site-packages\twisted\internet\ on line 249 as part of a doRead, so i guess the next step there would be determining if the issue was with your doRead function or if it is a problem with the data being read.


The MacOS version of the disk won’t open.


Asking this as a fellow tribler user (though not a mac user). Do you have any logs? This way they might help you more.


No, but the funny thing is that to reply to you, I decided to re download the installer, and it seemed like it was working for me this time. I don’t know if it was a total fluke or somehow the file got corrupted during download. :grin:


@LesVerres Thank you for the report. Apparently the issue is still present. There is a new release, could you please try and let us know if you still face this issue:

@darthleecher and @Solomon1732 Thank you for your comments.

@Tedzilla Good to know that the new download is working for you.

@all Best wishes for 2020.


So far, so good. Thnx.


I’m trying Tribler out for the first time, ever!


Now it just crashes. Had to go back to non beta version.


Thanks for testing!

We just released a second experimental version where we fixed a bug when the database contains a significant amount of records. If you are interested, you could check out this release :+1: