We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
To have a higher chance to connect to peers with NODE_COMPACT_FILTERS support, we could use the service bit filtering functionality of DNS seeds.
NODE_COMPACT_FILTERS
This is not a very well documented feature, but there is some information here: https://bitcoin.stackexchange.com/questions/60373/dns-seeder-options
The filter we'd be interested in is NODE_NETWORK | NODE_COMPACT_FILTERS, so 1 << 0 | 1 << 6 = 65.
NODE_NETWORK | NODE_COMPACT_FILTERS
1 << 0 | 1 << 6 = 65
Since not all seeds support this functionality, we should fall back on a regular DNS query if we're unable to retrieve addresses from the seeds.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
To have a higher chance to connect to peers with
NODE_COMPACT_FILTERS
support, we could use the service bit filtering functionality of DNS seeds.This is not a very well documented feature, but there is some information here:
https://bitcoin.stackexchange.com/questions/60373/dns-seeder-options
The filter we'd be interested in is
NODE_NETWORK | NODE_COMPACT_FILTERS
, so1 << 0 | 1 << 6 = 65
.Since not all seeds support this functionality, we should fall back on a regular DNS query if we're unable to retrieve addresses from the seeds.
The text was updated successfully, but these errors were encountered: