-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Remove emzy nodes #7129
Remove emzy nodes #7129
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
Thank you!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@devinbileck, 135.181.215.237 should be left in the list and 136.243.53.40 removed.
135.181.215.237 is the only one of @Emzy's four nodes that still has -peerbloomfilters=1
configured. The other three are causing quite a bit of churn with trying and failing connections, especially when it's all happening on the currently stormy Tor network. It also looks, like @mrosseel's btc2.vante.me node suffers the same problems and should be removed. I'm working on a comprehensive list of nodes that still function as we need them to.
Note that I've asked @Emzy to reconfigure |
@cbeams I assume you mean |
yes, fixed, thank you. |
Emzy is planning on shutting down most of his nodes soon, only leaving his mempool explorer (including bisq) and one btc node.