-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Update static and dns seeds for mainnet and testnet #3234
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.
concept ACK, utACK
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.
ACK, looks fine
nACK, as discussed in Slack. The way MNs were selected is suboptimal. Instead, we should update |
Ah, and the list in 8656a6b can be easily verified by using the protx list from block 1185168. Running |
I forgot to run |
mainnet 1185193, testnet 225964
All old nodes are down
eba3630
Rebased and reworked this using new script from #3235 with no manual intervention, tor nodes are in |
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.
ACK
* Drop (test.)dnsseed.masternode.io * makeseeds.py mainnet 1185193, testnet 225964 * generate-seeds.py * Update tor.md with live onion nodes All old nodes are down
Mainnet static seeds are 10% of active MNs plus 100 MNs running behind Tor. Testnet static seeds are all currently enabled MNs.Seeds are generated using updated scripts and instructions now. Onion seeds are not hardcoded but instead a few of them are listed in
tor.md
now with a note that they are hosted by one entity.Dropping
(test.)dnsseed.masternode.io
dns seeds because they are down atm.