From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UYgsA-0004d5-2W for bitcoin-development@lists.sourceforge.net; Sat, 04 May 2013 18:07:50 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of googlemail.com designates 74.125.83.47 as permitted sender) client-ip=74.125.83.47; envelope-from=john.dillon892@googlemail.com; helo=mail-ee0-f47.google.com; Received: from mail-ee0-f47.google.com ([74.125.83.47]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1UYgs9-0007hT-64 for bitcoin-development@lists.sourceforge.net; Sat, 04 May 2013 18:07:50 +0000 Received: by mail-ee0-f47.google.com with SMTP id b47so1174634eek.20 for ; Sat, 04 May 2013 11:07:42 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.14.205.194 with SMTP id j42mr20469812eeo.41.1367690862820; Sat, 04 May 2013 11:07:42 -0700 (PDT) Received: by 10.223.101.82 with HTTP; Sat, 4 May 2013 11:07:42 -0700 (PDT) In-Reply-To: <20130503151157.GA3902@petertodd.org> References: <20130503141801.GA1301@petertodd.org> <20130503151157.GA3902@petertodd.org> Date: Sat, 4 May 2013 18:07:42 +0000 Message-ID: From: John Dillon To: Peter Todd Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.4 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (john.dillon892[at]googlemail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in digit (john.dillon892[at]googlemail.com) -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1UYgs9-0007hT-64 Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Service bits for pruned nodes X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 May 2013 18:07:50 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I think you too should ask yourself why you are putting so much effort into optimizing a centralized service, the DNS seeds, rather than putting effort into optimizing the P2P peer discovery instead. DNS seeds are a necessary evil, one that shouldn't be promoted with additional features beyond simply obtaining your initial set of peers. After all Peter, just like you have implemented alternate block header distribution over twitter, in the future we should have many different means of peer discovery. Right now we have DNS seeds, a fixed list, and IRC discovery that does not work because the servers it was pointed too no longer exist. Not a good place to be. Some random ideas: search engines - search for "bitcoin seed address" or something and try IP's found (twitter is similar) ipv4 scanning - not exactly friendly, but the density of bitcoin nodes is probably getting to the point where a brute force search is feasible anycast peers - would work best with UDP probably, who has the resources to set this up? It is probably not worth the effort implementing the above immediately, but it is worth the effort to ensure that we don't make the DNS seed system so complex and sophisticated that we depend on it. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBCAAGBQJRhU44AAoJEEWCsU4mNhiPtssH/1yb/FZRRaZpr3CwkoaOhbhu pxfRNWgOEOL/mlWKTVgp2812qEnY9DySpJ5DJMjx7/GhSvOtnteza5ts4+pbuWhd l6E1R9zAYxX+VOiBxcBtoZNEXDcS+CjMumuBH5S1v+L5jEntOWS9G8DKasjD2WAQ DzX8YbOuzIOqasEbr5Hpr9Vfl7ZtW/+q/sPhQ1q3a7n7MaaIZrZicisJw3z7T7+0 T0yK8vUdYfstTjs0zLzfI5PW9+TG5T0kvj0kXSCjnK723Mfl7SXp6UZx6yebBi6q tcTVOPo4hfBWk8XryZxaSNCkDYY6kryy5cb2V+BojVfqLWVKgR3pdZqXqnEKNLo= =0XFF -----END PGP SIGNATURE-----