From: Peter Todd <pete@petertodd•org>
To: Matt Whitlock <bip@mattwhitlock•name>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Zero-Conf for Full Node Discovery
Date: Tue, 26 May 2015 01:15:46 -0400 [thread overview]
Message-ID: <20150526051546.GB23502@savin.petertodd.org> (raw)
In-Reply-To: <23111107.dfGN69SrR9@crushinator>
[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]
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?
>
> Not that I know of, but they do seed their address database via DNS, which you can poison if you control the LAN's DNS resolver. I did this for a Bitcoin-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 network over a very bandwidth-constrained Internet link, so I poisoned the DNS and rejected all outbound connection attempts on port 8333, to force all the wallets to connect to a single local full node, which had connectivity to a single remote node over the Internet. Thus, all the lightweight wallets at the festival had Bitcoin network connectivity, but we only needed to backhaul the Bitcoin network's transaction traffic once.
Interesting!
What festival was this?
--
'peter'[:-1]@petertodd.org
000000000000000003ce9f2f90736ab7bd24d29f40346057f9e217b3753896bb
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
next prev parent reply other threads:[~2015-05-26 5:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 4:06 Jim Phillips
2015-05-26 4:37 ` Matt Whitlock
2015-05-26 4:46 ` Kevin Greene
2015-05-26 4:56 ` Matt Whitlock
2015-05-26 5:12 ` Kevin Greene
2015-05-26 5:23 ` Luke Dashjr
2015-05-26 4:48 ` Jim Phillips
2015-05-26 4:52 ` Matt Whitlock
2015-05-26 5:15 ` Peter Todd [this message]
2015-05-26 5:47 ` Matt Whitlock
2015-05-26 10:48 ` Mike Hearn
2015-05-27 10:16 ` Louis Rossouw
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150526051546.GB23502@savin.petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=bip@mattwhitlock$(echo .)name \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox