Skip to content

Bitcoin Cash Node BCH-relevant DNS seed information

Bitcoin Cash Node uses special seeds under the control of Bitcoin Cash (BCH) network supporting operators to increase the chance of a node to find suitable peers on the BCH network.

The seeds used by Cash Node should distribute peers fairly but in a manner which increases the likelihood that Bitcoin Cash Nodes are able to connect to BCH compatible peers.

General expectations for DNS Seed operators

Bitcoin attempts to minimize the level of trust in DNS seeds, but DNS seeds still pose a small amount of risk for the network. As such, DNS seeds must be run by entities which have some minimum level of trust within the Bitcoin community.

Other implementations of Bitcoin software may also use the same seeds and may be more exposed. In light of this exposure, this document establishes some basic expectations for operating dnsseeds.

  1. A DNS seed operating organization or person is expected to follow good host security practices, maintain control of applicable infrastructure, and not sell or transfer control of the DNS seed. Any hosting services contracted by the operator are equally expected to uphold these expectations.
  2. The DNS seed results must consist exclusively of fairly selected and functioning Bitcoin nodes from the public network to the best of the operator's understanding and capability.
  3. For the avoidance of doubt, the results may be randomized but must not single-out any group of hosts to receive different results unless due to an urgent technical necessity and disclosed.
  4. The results may not be served with a DNS TTL of less than one minute.
  5. Any logging of DNS queries should be only that which is necessary for the operation of the service or urgent health of the Bitcoin network and must not be retained longer than necessary nor disclosed to any third party.
  6. Information gathered as a result of the operators node-spidering (not from DNS queries) may be freely published or retained, but only if this data was not made more complete by biasing node connectivity (a violation of expectation (1)).
  7. Operators are encouraged, but not required, to publicly document the details of their operating practices.
  8. A reachable email contact address must be published for inquiries related to the DNS seed operation.

If these expectations cannot be satisfied the operator should discontinue providing services and contact the active Bitcoin development teams as well as posting on bitcoin-dev. and bitcoin-ml.

Behavior outside of these expectations may be reasonable in some situations but should be discussed in public in advance.

See also