-
Notifications
You must be signed in to change notification settings - Fork 178
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
config: add directory node 'odpwaf…kptaid.onion' to defaults #1733
base: master
Are you sure you want to change the base?
config: add directory node 'odpwaf…kptaid.onion' to defaults #1733
Conversation
I have nothing against adding a new directory per se, but:
All this mostly to say that if we don't fix the underlying issue, we will simply end up with a longer and longer list of practically unusable directories. |
True.
No, I don't know. I have not done further tests. Only that it is reachable.
I am not able to answer these questions, as I have not done any further tests. Especially not over longer periods of time.
Agree. |
I would not recommend adding this node to the default list of directories. Indeed, it has been online for quite sometime but it is heavily manipulated as it constantly drops connections to peers in the middle of a coinjoin negotiation or privmsg exchange. Our log is full of blocks with 20-30 consecutive lines of:
Directories bql... and 3kx... are more difficult to connect to but once connected they are reliable. |
This PR adds directory node
odpwaf67rs5226uabcamvypg3y4bngzmfk7255flcdodesqhsvkptaid.onion:5222
to the default list of directory nodes. See joinmarket-webui/jam-docker#126 for discussion.Feedback to this node was that it has been online and reliable for a good amount of time. It has been mentioned by @roshii for the first time here: #1445 (comment)