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-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Yx697-0005KY-Q6 for bitcoin-development@lists.sourceforge.net; Tue, 26 May 2015 04:07:17 +0000 X-ACL-Warn: Received: from mail-wi0-f181.google.com ([209.85.212.181]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Yx695-0004Pu-Mr for bitcoin-development@lists.sourceforge.net; Tue, 26 May 2015 04:07:17 +0000 Received: by wizk4 with SMTP id k4so63315017wiz.1 for ; Mon, 25 May 2015 21:07:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=03JY60JKks/e8ipI32XLlNXG21AJw5sQ2a4J/ePNfi0=; b=ATYNpO+XXXbAuy8jTrCoHSYh5SiBQB0XFag+HvsToi8HvDHxU7CMkrL8zclg6Gr78m +Yj5gDsAfnDZd5SkRX1ogi3euo4hVgAu9tVR046Tj3LIjZvJpRXhwUMgCLFeuXoADHlD 29Tueq+5Dkwsi+wokMTKNWRb9Lv+J+yA5m7hj95UQKH2xLVFgObZ1W3EYQEk9TvAeyeS VxThENEr/xYJ84BiwwGdCwudWUeOKwRCOo6Zg9cwAjlQsglwAWJARGyg2Od2mQe+/27j DN6sxxkXx79Aqin1vyw8owS7EecQCs5rC+5aTGLC6gociNKGiDv/8aUHZ70kgs6O7KEu 9c0g== X-Gm-Message-State: ALoCoQn0uLhLMRrDQdBY26CLdyUwYB8LUN+OHltazT7eri8X0NfYG2GNcF8Q51gRijlKgAFlDe4Z X-Received: by 10.180.90.209 with SMTP id by17mr36630709wib.2.1432613229412; Mon, 25 May 2015 21:07:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.246.69 with HTTP; Mon, 25 May 2015 21:06:38 -0700 (PDT) From: Jim Phillips Date: Mon, 25 May 2015 23:06:38 -0500 Message-ID: To: Bitcoin Dev Content-Type: multipart/alternative; boundary=f46d043c80d2a3d7300516f442e5 X-Spam-Score: 1.5 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.7 HTML_IMAGE_ONLY_20 BODY: HTML: images with 1600-2000 bytes of words 1.0 HTML_MESSAGE BODY: HTML included in message 0.3 HTML_SHORT_LINK_IMG_3 HTML is very short with a linked image 0.0 T_REMOTE_IMAGE Message contains an external image -0.5 AWL AWL: Adjusted score from AWL reputation of From: address X-Headers-End: 1Yx695-0004Pu-Mr Subject: [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 04:07:17 -0000 --f46d043c80d2a3d7300516f442e5 Content-Type: text/plain; charset=UTF-8 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* *"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.* --f46d043c80d2a3d7300516f442e5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Is there any work being done on using some kind of zero-co= nf service discovery protocol so that lightweight clients can find a full n= ode 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 Int= ernet.=C2=A0

In a situation where there are hundre= ds or thousands of small SPV devices in a single home (if 21, Inc. is succe= ssful) monitoring the blockchain, this could result in lower traffic across= the slow WAN connection.=C2=A0 And yes, I realize it could potentially tak= e a LOT of these devices before the total bandwidth is greater than downloa= ding a full copy of the blockchain, but there's other reasons to host y= our own full node -- trust being one.

--
James G. Phillips IV=C2=A0=C2=A0
<= i>"Don't bunt. Aim out of the ball park. Aim for the company of im= mortals." -- David Ogilvy

=C2=A0