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.

You can configure git to use tor, and github currently works via tor.

https://stackoverflow.com/questions/27279359/how-to-make-git-work-to-push-commits-to-github-via-tor

git config http.proxy socks5://localhost:9150 # 9150 for TOR browser, 9050 for TOR service
git config https.proxy socks5://localhost:9150

^ affects the current repository. git config --global if you want it to apply to all repositories, including one you haven't yet cloned.

When cloning a large repository, such as haveno, you then run into the problem that git doesn't retry when the other end hangs up, which it often does over a slow tor connection.

until git clone https://github.com/retoaccess1/haveno-reto ; do true ; done

will retry until it finally succeeds.

You can create and log into a github account using Tor Browser, just be sure to never use that account without tor browser. If you actually want to contribute using that account, you will need to email github customer service and have them un-shadowban you first.

This can be safely ignored for now.

You can compare the diffs like so: https://github.com/haveno-dex/haveno/compare/master...retoaccess1:haveno-reto:master but for extra security build the binaries yourself if their repo's changes look good or as expected from the Haveno setup documentation

@xmr_unlimited @reto

For evaluation just use a vm that you can clone and dispose.

Will do so, thanks.