-
-
Notifications
You must be signed in to change notification settings - Fork 145
"Warning : There are no arbitrators available" #1760
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
BUMP There are a lot of people reporting this problem. Anyone know what is happening? |
What platform are you using? I recommend a fresh install. Just make sure to export your settings and wallet first. |
It is a fresh install. And there are many people who are reporting this issue right now. Today it's working on and off; sometimes it seems to work, then I get the same warning back. |
It's from network problems, arbitrators being intermittently available. It should resolve itself as the network problems clear, and it could help if they apply PoW defense to all seed nodes and arbitrators (highly recommended). |
Is it because of the DOS against TOR as some suggested? As for the "PoW defense", could you please ELI5 what it does and how relevant it is to make the current problem disappear? |
The seed nodes and arbitrators should be running proof of work defense on Tor, which requires clients connecting to them to perform some work in order to receive a prioritized response. It's useful against DDoS because it becomes prohibitively expensive for the attacker to perform the necessary work, while it's not a problem for normal users to perform a small amount of work for regular use. |
Uh oh!
There was an error while loading. Please reload this page.
I got this message when trying to create a new offer. I thought it was because I was on v 1.0.8, so I updated to 1.1.1.
It took forever to get in, but when I was able to get in, I first got this message :
And then, when trying to create an offer, got the same message as before :
And when trying to take an offer already there, I get this message :
What's wrong? I've been using Retoswap for months and never experienced such a problem before.
The text was updated successfully, but these errors were encountered: