- 5 Posts
- 11 Comments
It’s a change to how trades are done in the background.
Before, the taker client would select the arbitrator, now this is done by the maker. Before this change, a rouge arbitrator with a modified client could have taken all open trades, assign themself to them and pay them out to themself.
After this change, the maker-side selects the arbitrator, and a rouge one would lose a bunch of bond in the trades they weren’t assigned to. The more arbitrators there are, the less likely it gets that one of them could go rouge and make a profit. For example: at 20 arbitrators, a rouge arbitrator would be expected to lose the 15% bond for 19 out of 20 trades. That is on average nearly 3 times higher than the expected return of the 1 trade they can actually drain.
This is why we will ask many trusted community members to become arbitrators once the software has become more stable and there aren’t multiple updates per month anymore.
Initially we used github actions to build the installers and have people download them from their, which requires a github account.
Now without the need for a github account!
Presumably once the network has been running stable for a while and there aren’t multiple updates a week. There is also an issue on the main Haveno repo that could make custom binaries unnecessary. In that case you would get them straight from Haveno and only add a reto config file.
From its readme:
Stalled development at this moment, don’t use.
Reto is an instance of Haveno (and currently the only one). The developers of Haveno do not to run an instance themselves and instead put out the code and instructions on how to run it. We hope people decide to join our instance and have a low arbitration fee of 0.6% without any direct network fee. Right now there are already 12 live offers totaling 26.5 XMR and so far 2 real-world trades have been made!
There are currently not many hardcoded arbitrators and one of them is on top of that still offline. We are not entirely sure if simply retrying works or if you have to restart before your client picks an arbitrator that is online. It might also have resolved itself after the network has propagated a bit more.
This can be safely ignored for now.
🥰