Replace default directory nodes with currently working ones #1810
Conversation
|
Having literally just been looking at this, I sort of half-ACK: 5 seems like a lot? But don't let that stop you if you think this is the right choice :) edit: 'half-ACK' not just conceptually but as in actually connecting :) |
|
It seems that dnodes go down from time to time. I don't see any downsides adding more than less. Am I missing something? My idea now was to just analyze stats and then replace defaults with the most stable known ones in default config. |
You're probably not missing anything. I'm just a little worried about "overburdening" by opening so many connections, I don't have a solid (or probably even, correct!) reason for worrying about it. On reflection I guess it is a bit silly, since we end up opening more than 5 connections at the point where we do the actual coinjoin ... |
|
Fwiw I remembered why I was originally leery of having 5 or more, rather than just 3: it's nice if you're not waiting for the connections, and they don't always work (even if the directory node is working, i.e. Tor connections being flaky), so if you start with only 3 there's a better chance all of the connections work straight away. But, the other side of that is of course the chance of connecting to anyone is higher with 5. |
|
This is main blocker for new release. If there are no strong arguments against having 5 directory nodes in default config, I plan to merge this soon. |
|
tACK the list in d87e7cb across a couple of runs (across several days). There are 5 in the list, across my two tests, the first time they all connected, the second time I wasn't able to connect to 1 out of 5. But in both cases the application succeeded in working as intended. |
2 participants
These ones are currently working ones according both to https://directories.w3ird.tech/ and my local monitoring using jm-dn-uptime.