public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jim Phillips <jim@ergophobia.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: Mon, 25 May 2015 23:48:16 -0500	[thread overview]
Message-ID: <CANe1mWzeLsOWv+2qwx1b3s61HqCwy5GLd2Rv3LgWLrOa_jkFjw@mail.gmail.com> (raw)
In-Reply-To: <2916218.tfdjj1Sv9m@crushinator>

[-- Attachment #1: Type: text/plain, Size: 1690 bytes --]

Do any wallets actually do this yet?
On May 25, 2015 11:37 PM, "Matt Whitlock" <bip@mattwhitlock.name> wrote:

> This is very simple to do. Just ping the "all nodes" address (ff02::1) and
> try connecting to TCP port 8333 of each node that responds. Shouldn't take
> but more than a few milliseconds on any but the most densely populated LANs.
>
>
> On Monday, 25 May 2015, at 11:06 pm, Jim Phillips wrote:
> > Is there any work being done on using some kind of zero-conf service
> > discovery protocol so that lightweight clients can find a full node on
> the
> > same LAN to peer with rather than having to tie up WAN bandwidth?
> >
> > I envision a future where lightweight devices within a home use SPV over
> > WiFi to connect with a home server which in turn relays the transactions
> > they create out to the larger and faster relays on the Internet.
> >
> > In a situation where there are hundreds or thousands of small SPV devices
> > in a single home (if 21, Inc. is successful) monitoring the blockchain,
> > this could result in lower traffic across the slow WAN connection.  And
> > yes, I realize it could potentially take a LOT of these devices before
> the
> > total bandwidth is greater than downloading a full copy of the
> blockchain,
> > but there's other reasons to host your own full node -- trust being one.
> >
> > --
> > *James G. Phillips IV*
> > <https://plus.google.com/u/0/113107039501292625391/posts>
> > <http://www.linkedin.com/in/ergophobe>
> >
> > *"Don't bunt. Aim out of the ball park. Aim for the company of
> immortals."
> > -- David Ogilvy*
> >
> >  *This message was created with 100% recycled electrons. Please think
> twice
> > before printing.*
>

[-- Attachment #2: Type: text/html, Size: 2283 bytes --]

  parent reply	other threads:[~2015-05-26  4:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26  4:06 [Bitcoin-development] Zero-Conf for Full Node Discovery 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 [this message]
2015-05-26  4:52     ` Matt Whitlock
2015-05-26  5:15       ` Peter Todd
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=CANe1mWzeLsOWv+2qwx1b3s61HqCwy5GLd2Rv3LgWLrOa_jkFjw@mail.gmail.com \
    --to=jim@ergophobia.org \
    --cc=bip@mattwhitlock.name \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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