-
Notifications
You must be signed in to change notification settings - Fork 37.7k
chainparams: Add default fixed seeds for signet #20648
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
Conversation
Can be tested as specified in #20637 with an empty datadir:
|
Maybe for mainnet tor v3 as well for bootstrapping connections in 0.21.0 |
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ConflictsReviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
Concept ACK |
I'll leave that for a follow-up |
tyi, long V3 addresses cant be fixed encode, in the old style manner, since ADDRv2 breaks the logic to hide them in ipv6, i.e. btw, that is even backwards and backport compatible since all old node software is capable to do V3 bootstrap over the ADDR message if the Tor stack on there crufts is updated and Tor V3 aware. edit@saibato concept ACK, better than nothing since not all have Tor enabled stacks. |
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.
Tested and this appears to work.
2020-12-14T15:45:25Z init message: Loading P2P addresses...
2020-12-14T15:45:25Z ERROR: DeserializeFileDB: Failed to open file /home/jon/projects/bitcoin/bitcoin/datadir/signet/peers.dat
2020-12-14T15:45:25Z Invalid or missing peers.dat; recreating
2020-12-14T15:45:25Z tor: Got service ID t5acztv2shwvbbyfh6xktlgmryfhsw4ukloo2svlkhllfuwbzahtxlad, advertising service t5acztv2shwvbbyfh6xktlgmryfhsw4ukloo2svlkhllfuwbzahtxlad.onion:38333
2020-12-14T15:45:25Z AddLocal(t5acztv2shwvbbyfh6xktlgmryfhsw4ukloo2svlkhllfuwbzahtxlad.onion:38333,4)
2020-12-14T15:45:25Z ERROR: DeserializeFileDB: Failed to open file /home/jon/projects/bitcoin/bitcoin/datadir/signet/anchors.dat
2020-12-14T15:45:25Z 0 block-relay-only anchors will be tried for connections.
2020-12-14T15:45:25Z init message: Starting network threads...
2020-12-14T15:45:25Z addcon thread start
2020-12-14T15:45:25Z init message: Done loading
2020-12-14T15:45:25Z opencon thread start
2020-12-14T15:45:25Z dnsseed thread start
2020-12-14T15:45:25Z net thread start
2020-12-14T15:45:25Z msghand thread start
2020-12-14T15:45:25Z Loading addresses from DNS seed 178.128.221.177
2020-12-14T15:45:25Z Loading addresses from DNS seed 2a01:7c8:d005:390::5
2020-12-14T15:45:25Z Loading addresses from DNS seed ntv3mtqw5wt63red.onion:38333
2020-12-14T15:45:25Z 0 addresses found from DNS seeds
2020-12-14T15:45:25Z dnsseed thread exit
2020-12-14T15:45:27Z New outbound peer connected: version: 70016, blocks=15997, peer=0 (full-relay)
2020-12-14T15:46:26Z Adding fixed seed nodes as DNS doesn't seem to be available.
2020-12-14T15:46:26Z New outbound peer connected: version: 70016, blocks=15997, peer=1 (full-relay)
2020-12-14T15:46:27Z Synchronizing blockheaders, height: 2000 (~12.21%)
Added to 0.21.1 milestone |
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 fae6558
There's no instructions in the release notes for updating this. I'm not sure this is necessary, but for example the testnet hardcoded seeds haven't been updated in ages, for example, and it's unclear how useful they still are. |
The list was generated with |
Looks okay to me |
What problem is this solving? More signet seeds just in case? |
fixed seeds are used as fallback seeds when the dns seeds can't be queried for some reason |
-BEGIN VERIFY SCRIPT- ./contrib/seeds/generate-seeds.py ./contrib/seeds/ > src/chainparamsseeds.h -END VERIFY SCRIPT-
fae6558
to
fae1a64
Compare
Rebased to get rid of already merged hunks. No other changes. |
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 fae1a64
I suppose running a dns seed and getting statistics from there for populating nodes_signet.txt is the way to get good values here.
178.128.221.177:38333 | ||
103.16.128.63:38333 | ||
153.126.143.201:38333 | ||
192.241.163.142:38333 |
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.
Only:
"address": "178.128.221.177",
"address": "103.16.128.63",
"address": "153.126.143.201",
"address": "192.241.163.142",
seem to still be present?
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.
I think without a dns seeder or other software to track uptime, there will always be nodes in the list that are not reachable
Hadn't really noticed this before it conflicted with the TorV3 one. Why close this? |
Didn't seem a lot of appetite and v3 for mainnet is more important than signet |
This adds some random fixed seeds for signet. They might not work, but it is better than nothing.