From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Yx7Db-0005rl-M0 for bitcoin-development@lists.sourceforge.net; Tue, 26 May 2015 05:15:59 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of petertodd.org designates 62.13.149.77 as permitted sender) client-ip=62.13.149.77; envelope-from=pete@petertodd.org; helo=outmail149077.authsmtp.com; Received: from outmail149077.authsmtp.com ([62.13.149.77]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1Yx7Da-0006Ad-Dt for bitcoin-development@lists.sourceforge.net; Tue, 26 May 2015 05:15:59 +0000 Received: from mail-c237.authsmtp.com (mail-c237.authsmtp.com [62.13.128.237]) by punt15.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t4Q5Fo2J093815; Tue, 26 May 2015 06:15:50 +0100 (BST) Received: from savin.petertodd.org (75-119-251-161.dsl.teksavvy.com [75.119.251.161]) (authenticated bits=128) by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t4Q5FkkD031108 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 26 May 2015 06:15:48 +0100 (BST) Date: Tue, 26 May 2015 01:15:46 -0400 From: Peter Todd To: Matt Whitlock Message-ID: <20150526051546.GB23502@savin.petertodd.org> References: <2916218.tfdjj1Sv9m@crushinator> <23111107.dfGN69SrR9@crushinator> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="/NkBOFFp2J2Af1nK" Content-Disposition: inline In-Reply-To: <23111107.dfGN69SrR9@crushinator> User-Agent: Mutt/1.5.21 (2010-09-15) X-Server-Quench: 45af0e9b-0366-11e5-9f74-002590a135d3 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR aQdMdAQUFVQNAgsB AmMbW1JeUVh7XWo7 bA9PbARUfEhLXhtr VklWR1pVCwQmRRhg A2hFCW1ydARHeHY+ ZEdjWXIVWEErI0Yo SxxJFW4AY3phaTUa TUkOcAdJcANIexZF O1F8UScOLwdSbGoL NQ4vNDcwO3BTJTpY RgYVKF8UXXNDLDMm QFUpGjMhVUMCXW0d MhgiYngbEEtZHkQp Olw/VEgJWwA8 X-Authentic-SMTP: 61633532353630.1024:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 75.119.251.161/587 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. X-Spam-Score: -1.5 (-) 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 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1Yx7Da-0006Ad-Dt Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Zero-Conf for Full Node Discovery 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: Tue, 26 May 2015 05:15:59 -0000 --/NkBOFFp2J2Af1nK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 26, 2015 at 12:52:07AM -0400, Matt Whitlock wrote: > On Monday, 25 May 2015, at 11:48 pm, Jim Phillips wrote: > > Do any wallets actually do this yet? >=20 > Not that I know of, but they do seed their address database via DNS, whic= h you can poison if you control the LAN's DNS resolver. I did this for a Bi= tcoin-only Wi-Fi network I operated at a remote festival. We had well over = a hundred lightweight wallets, all trying to connect to the Bitcoin P2P net= work over a very bandwidth-constrained Internet link, so I poisoned the DNS= and rejected all outbound connection attempts on port 8333, to force all t= he wallets to connect to a single local full node, which had connectivity t= o a single remote node over the Internet. Thus, all the lightweight wallets= at the festival had Bitcoin network connectivity, but we only needed to ba= ckhaul the Bitcoin network's transaction traffic once. Interesting! What festival was this? --=20 'peter'[:-1]@petertodd.org 000000000000000003ce9f2f90736ab7bd24d29f40346057f9e217b3753896bb --/NkBOFFp2J2Af1nK Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- iQGrBAEBCACVBQJVZAF+XhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw MDAwMDAwMDAwMDAwMDAwM2NlOWYyZjkwNzM2YWI3YmQyNGQyOWY0MDM0NjA1N2Y5 ZTIxN2IzNzUzODk2YmIvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0 ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkfvcAwgAvz0cP3T0CT1yBs6nXPoGVHg0 +bjsk6/gsgInzjWekoM213n2Q5ocsPHHX4rt/P7WGTYKRpT5QFN883DzIcEcHY45 UyEQfxITtGZWSDo/g6bvN6XZGyhv+t2ZaxPU4u6RayXtXOG9qQfKZJsOJZaesc1q 3IiG0Vv3BICWNa12ZAjyb9zP0jRCCyPrso6qVyfju/IBxsBtcmXOpwMBK61DN4A0 zmTWSFlbUUNFEOdaqI8J2eJhiaB7DrS7FAdnpADiz3LutU/7OMRECzLJd6ioYQAK oLmZMiArrQ3zWkYVaO52NJ8w8zBSSQgdND6drgYGNEi2Aswd93dYjXgHJ668iA== =Ltg5 -----END PGP SIGNATURE----- --/NkBOFFp2J2Af1nK--