You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Considering the default hop count is 1, it's no suprise there is little need for relays. Of course, some users will change the hop count and hidden services also requires relays. So, I would at least expect an occosional relay. I'll take a look at this.
In the application tester, I'm seeing tons of timeouts on crawl requests and payouts. If half blocks are not counter-signed, it would explain the negative balances. I will debug it more.
Update: observed the following error in the exit nodes on our testnet:
Mar 24 10:19:36 prxmx3 python3[18491]: Not sending crawl response, the block is invalid. Result (<function ValidationResult.invalid at 0x7fa7a8dc1b70>, ['Total up is higher than expected compared to the next block'])
Users report that 7.5.0 (and possibly 7.4.4) does not work as a relay by default, resulting in no credit gain when Tribler is idle.
The text was updated successfully, but these errors were encountered: