9890058b37
b0c706795cRemove unreliable seed from chainparams.cpp, and the associated README (SatsAndSports) Pull request description: The DNS seed `dnsseed.bitcoin.dashjr-list-of-p2p-nodes.us.` is not returning a representative sample of bitcoin nodes. It currently returns nothing later than 28.1.0, breaching the policy. This PR removes that seed from the list of DNS seeds ### Rationale The [policy for seeds](https://github.com/bitcoin/bitcoin/blob/master/doc/dnsseed-policy.md) includes this: > The DNS seed results must consist exclusively of fairly selected and functioning Bitcoin nodes from the public network A number of comments below, in response to this PR, include apparent breaches of this policy: [1](https://github.com/bitcoin/bitcoin/pull/33723#issuecomment-3458071231) [2](https://github.com/bitcoin/bitcoin/pull/33723#issuecomment-3457655364), [3](https://github.com/bitcoin/bitcoin/pull/33723#issuecomment-3457712557), in particular the first linked comment ([1](https://github.com/bitcoin/bitcoin/pull/33723#issuecomment-3458071231)) comparing the distribution at this seed to other seeds. This seed is not including anything later than 28.2.0, breaching this policy. To ensure the policy is followed, and the seeds include a representative sample of Bitcoin nodes, this PR removes this seed from the list ### Data I ran this: ``` # Get some ip address from that seed: # Repeated multiple times, to get many different IPs: dig +short dnsseed.bitcoin.dashjr-list-of-p2p-nodes.us >> dnsseed.bitcoin.dashjr-list-of-p2p-nodes.us # For each distinct ip gathered from the seed, get basic info about the node, including it's User Agent string: cat dnsseed.bitcoin.dashjr-list-of-p2p-nodes.us | sort -u | while read ip; do echo ===; echo $ip; nmap -p 8333 --script bitcoin-info "$ip"; done > seed_versions.txt ``` and then summarized the agents with `egrep 'User Agent' seed_versions.txt | sort | uniq -c` and got: ``` 1 User Agent: /Satoshi:22.0.0/ 1 User Agent: /Satoshi:22.1.0/ 5 User Agent: /Satoshi:24.0.1/ 1 User Agent: /Satoshi:25.1.0/ 30 User Agent: /Satoshi:27.0.0/ 1 User Agent: /Satoshi:27.1.0/ 1 User Agent: /Satoshi:27.1.0/Knots:20240801/ 1 User Agent: /Satoshi:28.0.0/ 7 User Agent: /Satoshi:28.1.0/ 2 User Agent: /Satoshi:28.1.0/Knots:20250305/ ``` ACKs for top commit: l0rinc: reACKb0c706795cdelta1: reACKb0c706795cCrypt-iQ: crACKb0c706795claanwj: ACKb0c706795cmurchandamus: ACKb0c706795cRandyMcMillan: ACKb0c7067wiz: ACKb0c706795cdergoegge: ACKb0c706795cstickies-v: re-ACKb0c706795cmzumsande: ACKb0c706795cinstagibbs: ACKb0c706795cTree-SHA512: 7230b8dd24560ce6f8247e2e82ae7846ded8b91e230c59cc3643da3f5b9c12b5f025c1bb14490c19ca55f3794e81ce08106b31b3bf883d5c2dced05017123ac4
Repository Tools
Developer tools
Specific tools for developers working on this repository.
Additional tools, including the github-merge.py script, are available in the maintainer-tools repository.
Verify-Commits
Tool to verify that every merge commit was signed by a developer using the github-merge.py script.
Linearize
Construct a linear, no-fork, best version of the blockchain.
Qos
A Linux bash script that will set up traffic control (tc) to limit the outgoing bandwidth for connections to the Bitcoin network. This means one can have an always-on bitcoind instance running, and another local bitcoind/bitcoin-qt instance which connects to this node and receives blocks from it.
Seeds
Utility to generate the pnSeed[] array that is compiled into the client.
Build Tools and Keys
Packaging
The Debian subfolder contains the copyright file.
All other packaging related files can be found in the bitcoin-core/packaging repository.
MacDeploy
Scripts and notes for Mac builds.
Test and Verify Tools
TestGen
Utilities to generate test vectors for the data-driven Bitcoin tests.
Verify-Binaries
This script attempts to download and verify the signature file SHA256SUMS.asc from bitcoin.org.
Command Line Tools
Completions
Shell completions for bash and fish.
UTXO Set Tools
UTXO-to-SQLite
This script converts a compact-serialized UTXO set (as generated by Bitcoin Core with dumptxoutset)
to a SQLite3 database. For more details like e.g. the created table name and schema, refer to the
module docstring on top of the script, which is also contained in the command's --help output.