You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

dnsseed-policy.md 2.4KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354
  1. Expectations for DNS Seed operators
  2. ====================================
  3. Bitcoin Core attempts to minimize the level of trust in DNS seeds,
  4. but DNS seeds still pose a small amount of risk for the network.
  5. As such, DNS seeds must be run by entities which have some minimum
  6. level of trust within the Bitcoin community.
  7. Other implementations of Bitcoin software may also use the same
  8. seeds and may be more exposed. In light of this exposure, this
  9. document establishes some basic expectations for operating dnsseeds.
  10. 0. A DNS seed operating organization or person is expected to follow good
  11. host security practices, maintain control of applicable infrastructure,
  12. and not sell or transfer control of the DNS seed. Any hosting services
  13. contracted by the operator are equally expected to uphold these expectations.
  14. 1. The DNS seed results must consist exclusively of fairly selected and
  15. functioning Bitcoin nodes from the public network to the best of the
  16. operator's understanding and capability.
  17. 2. For the avoidance of doubt, the results may be randomized but must not
  18. single-out any group of hosts to receive different results unless due to an
  19. urgent technical necessity and disclosed.
  20. 3. The results may not be served with a DNS TTL of less than one minute.
  21. 4. Any logging of DNS queries should be only that which is necessary
  22. for the operation of the service or urgent health of the Bitcoin
  23. network and must not be retained longer than necessary nor disclosed
  24. to any third party.
  25. 5. Information gathered as a result of the operators node-spidering
  26. (not from DNS queries) may be freely published or retained, but only
  27. if this data was not made more complete by biasing node connectivity
  28. (a violation of expectation (1)).
  29. 6. Operators are encouraged, but not required, to publicly document the
  30. details of their operating practices.
  31. 7. A reachable email contact address must be published for inquiries
  32. related to the DNS seed operation.
  33. If these expectations cannot be satisfied the operator should
  34. discontinue providing services and contact the active Bitcoin
  35. Core development team as well as posting on
  36. [bitcoin-dev](https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev).
  37. Behavior outside of these expectations may be reasonable in some
  38. situations but should be discussed in public in advance.
  39. See also
  40. ----------
  41. - [bitcoin-seeder](https://github.com/sipa/bitcoin-seeder) is a reference implementation of a DNS seed.