From: "Jeremy Spilman" <jeremy@taplink•co>
To: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Peer Discovery and Overlay
Date: Tue, 24 Dec 2013 00:52:46 -0800 [thread overview]
Message-ID: <op.w8k9l8qayldrnw@laptop-air.hsd1.ca.comcast.net> (raw)
Some really nice efforts out there to map and analyze the bitcoin P2P
network.
The current protocol apparently recommends returning up to 2500 addresses
from 'getaddr'. I'm not sure how much clients are expected to probe the
address space in order to select 'far-apart' peers, or how much such an
process would even attempt to achieve.
How much does it matter if the ability to discover the entire network of
peers is fast or slow? There are probably pros and cons to both.
Is there any thought to how existing bitcoin node relations, and the ease
at which peers can be discovered, becomes a service in itself, or even
possibly a vulnerability?
Are there any past instances of applications hijacking or interfacing with
the exiting p2p messages, or abusing 'getaddr' functionality? Are there
any guidelines on this, or should there be?
next reply other threads:[~2013-12-24 8:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-24 8:52 Jeremy Spilman [this message]
2013-12-24 10:47 ` Tier Nolan
2013-12-24 14:02 ` Peter Todd
2013-12-24 17:11 ` Warren Togami Jr.
2013-12-24 17:15 ` Mike Hearn
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=op.w8k9l8qayldrnw@laptop-air.hsd1.ca.comcast.net \
--to=jeremy@taplink$(echo .)co \
--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