{"type":"rich","version":"1.0","author_name":"npub17qxssk9sj2r7jswvh3y32e7vwz7mcckhz33gk9nurdmw0lhsfkgswupwet","author_url":"https://nostr.ae/npub17qxssk9sj2r7jswvh3y32e7vwz7mcckhz33gk9nurdmw0lhsfkgswupwet","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-05-26\n📝 Original message: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.\n\n\nOn Monday, 25 May 2015, at 11:06 pm, Jim Phillips wrote:\n\u003e Is there any work being done on using some kind of zero-conf service\n\u003e discovery protocol so that lightweight clients can find a full node on the\n\u003e same LAN to peer with rather than having to tie up WAN bandwidth?\n\u003e \n\u003e I envision a future where lightweight devices within a home use SPV over\n\u003e WiFi to connect with a home server which in turn relays the transactions\n\u003e they create out to the larger and faster relays on the Internet.\n\u003e \n\u003e In a situation where there are hundreds or thousands of small SPV devices\n\u003e in a single home (if 21, Inc. is successful) monitoring the blockchain,\n\u003e this could result in lower traffic across the slow WAN connection.  And\n\u003e yes, I realize it could potentially take a LOT of these devices before the\n\u003e total bandwidth is greater than downloading a full copy of the blockchain,\n\u003e but there's other reasons to host your own full node -- trust being one.\n\u003e \n\u003e --\n\u003e *James G. Phillips IV*\n\u003e \u003chttps://plus.google.com/u/0/113107039501292625391/posts\u003e\n\u003e \u003chttp://www.linkedin.com/in/ergophobe\u003e\n\u003e \n\u003e *\"Don't bunt. Aim out of the ball park. Aim for the company of immortals.\"\n\u003e -- David Ogilvy*\n\u003e \n\u003e  *This message was created with 100% recycled electrons. Please think twice\n\u003e before printing.*"}