-
Notifications
You must be signed in to change notification settings - Fork 92
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
Electrum queries are inefficient, may produce server bans #865
Comments
After several tries, I managed to do a successful swap between a local When either or both |
Thanks for writing up the issue. I have not looked into this deeply but It seems like there has been changes to electrum, this is the first time I have seen this message. When we implemented this we put a fair bit of work in making the queries efficient as we were triggering DDoS protection. We are happy to accept a PR on this and happy to provide guidance. Alternatively running a local electrum server might be the best way to go for now. |
On Sun, Dec 12, 2021 at 10:57:52PM -0800, rishflab wrote:
Thanks for writing up the issue.
I have not looked into this deeply but It seems like there has been changes to electrum, this is the first time I have seen this message. When we implemented this we put a fair bit of work in making the queries efficient as we were triggering DDoS protection.
We are happy to accept a PR on this. Alternatively running a local electrum server might be the best way to go for now.
I'm not an electrs or electrum developer, so I can't give any technical
background. I am currently running an electrum server and that fixed the
issue.
Unfortunately the issue also crops up when I run `swap`. I don't think
it's reasonable to expect a client (who is only running `swap`) to run
their own electrum server.
|
I analyzed the outgoing traffic of the Bob and the Cli is making tons of
|
Some info here too |
Queries to the electrum server are done in an inefficient way. When using an
electrs
locally hosted back end, the following log messages are produced:your wallet uses less efficient method of querying electrs, consider contacting the developer of your wallet. Reason: blockchain.scripthash.get_history called for unsubscribed scripthash: c28a[......]
This may be related to #797 where the (public) electrum server rejects our requests, probably to avoid DoS attacks.
The text was updated successfully, but these errors were encountered: