dnsseed-policy.md 2.37 KB
Newer Older
barrystyle's avatar
barrystyle committed
1 2 3
Expectations for DNS Seed operators
====================================

Joeldo Holanda's avatar
Joeldo Holanda committed
4
Merge Core attempts to minimize the level of trust in DNS seeds,
barrystyle's avatar
barrystyle committed
5 6
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
Joeldo Holanda's avatar
Joeldo Holanda committed
7
level of trust within The Merge community.
barrystyle's avatar
barrystyle committed
8

9
Other implementations of MERGE software may also use the same
barrystyle's avatar
barrystyle committed
10 11 12 13 14 15 16 17 18 19 20
seeds and may be more exposed. In light of this exposure this
document establishes some basic expectations for the expectations
for the operation of dnsseeds.

0. A DNS seed operating organization or person is expected
to follow good host security practices and maintain control of
their serving infrastructure and not sell or transfer control of their
DNS seed. Any hosting services contracted by the operator are
equally expected to uphold these expectations.

1. The DNS seed results must consist exclusively of fairly selected and
21
functioning MERGE nodes from the public network to the best of the
barrystyle's avatar
barrystyle committed
22 23 24 25 26 27 28 29 30
operators understanding and capability.

2. 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.

3. The results may not be served with a DNS TTL of less than one minute.

4. Any logging of DNS queries should be only that which is necessary
Joeldo Holanda's avatar
Joeldo Holanda committed
31
for the operation of the service or urgent health of The Merge
barrystyle's avatar
barrystyle committed
32 33 34 35 36 37 38 39 40 41 42 43 44 45 46
network and must not be retained longer than necessary or disclosed
to any third party.

5. 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)).

6. Operators are encouraged, but not required, to publicly document the
details of their operating practices.

7. 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
47
discontinue providing services and contact the active MERGE
barrystyle's avatar
barrystyle committed
48
Core development team as well as posting on the
49
[MERGE Forum](https://forum.MERGE.org).
barrystyle's avatar
barrystyle committed
50 51 52 53 54 55 56

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

See also
----------
- [bitcoin-seeder](https://github.com/sipa/bitcoin-seeder) is a reference implementation of a DNS seed.