aboutsummaryrefslogtreecommitdiff
path: root/doc/dnsseed-policy.md
diff options
context:
space:
mode:
authorMatt Corallo <git@bluematt.me>2014-08-09 20:57:47 -0700
committerMatt Corallo <git@bluematt.me>2014-09-03 00:41:54 -0700
commit550d4fa7a77c9763d4de9e0c0c48bc2655a65017 (patch)
treed7837046ef4baa83bf2a711a501dc96ecf2a1c0a /doc/dnsseed-policy.md
parentb8d92236f61699846f67d8ce6cb55458a46f9de1 (diff)
downloadbitcoin-550d4fa7a77c9763d4de9e0c0c48bc2655a65017.tar.xz
Remove DNS Seeds run by entities which were never well-established.
Diffstat (limited to 'doc/dnsseed-policy.md')
-rw-r--r--doc/dnsseed-policy.md3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/dnsseed-policy.md b/doc/dnsseed-policy.md
index 73e307f7cd..66a1757ac5 100644
--- a/doc/dnsseed-policy.md
+++ b/doc/dnsseed-policy.md
@@ -3,6 +3,9 @@ Expectations for DNS Seed operators
Bitcoin Core 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 the expectations