From 8376005fd039690be1b95ceaca9c5388ecd1704e Mon Sep 17 00:00:00 2001 From: Neil Booth Date: Fri, 8 Sep 2017 17:29:09 +0900 Subject: [PATCH] Remove exception for onion peers Like clearnet peers, they are only returned in server.peers.subscribe if there was a successful connection. --- PEER_DISCOVERY.rst | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/PEER_DISCOVERY.rst b/PEER_DISCOVERY.rst index c4c87ea..1d264df 100644 --- a/PEER_DISCOVERY.rst +++ b/PEER_DISCOVERY.rst @@ -53,13 +53,8 @@ The server should craft its response in a way that reduces the effectiveness of sybil attacks and peer spamming. The response should only include peers it has successfully connected -to recently. If Tor routing is not available, so their existence -cannot be verified, the response should include some hard-coded onion -peers so that clients always have a choice of onion servers. - -Only reporting recent good peers ensures that those that have gone -offline will not be passed around for long (ignoring for hard-coded -onion peer exception). +to recently. Only reporting recent good peers ensures that those that +have gone offline will not be passed around for long. In ElectrumX, "recently" is taken to be the last 24 hours. Only one peer from each IPv4/16 netmask is returned, and the number of onion