diff options
| author | Matt Corallo <git@bluematt.me> | 2014-08-09 20:57:47 -0700 |
|---|---|---|
| committer | Matt Corallo <git@bluematt.me> | 2014-09-03 00:41:54 -0700 |
| commit | 550d4fa7a77c9763d4de9e0c0c48bc2655a65017 (patch) | |
| tree | d7837046ef4baa83bf2a711a501dc96ecf2a1c0a | |
| parent | b8d92236f61699846f67d8ce6cb55458a46f9de1 (diff) | |
Remove DNS Seeds run by entities which were never well-established.
| -rw-r--r-- | doc/dnsseed-policy.md | 3 | ||||
| -rw-r--r-- | src/chainparams.cpp | 1 |
2 files changed, 3 insertions, 1 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 diff --git a/src/chainparams.cpp b/src/chainparams.cpp index ce99f268f3..bfe50d77d5 100644 --- a/src/chainparams.cpp +++ b/src/chainparams.cpp @@ -99,7 +99,6 @@ public: vSeeds.push_back(CDNSSeedData("dashjr.org", "dnsseed.bitcoin.dashjr.org")); vSeeds.push_back(CDNSSeedData("bitcoinstats.com", "seed.bitcoinstats.com")); vSeeds.push_back(CDNSSeedData("bitnodes.io", "seed.bitnodes.io")); - vSeeds.push_back(CDNSSeedData("open-nodes.org", "seeds.bitcoin.open-nodes.org")); vSeeds.push_back(CDNSSeedData("xf2.org", "bitseed.xf2.org")); base58Prefixes[PUBKEY_ADDRESS] = list_of(0); |