From: "Luke-Jr" <luke@dashjr•org>
To: Jeff Garzik <jgarzik@exmulti•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] P2P feature discovery (was Re: BIP 33 - Stratized Nodes)
Date: Wed, 16 May 2012 18:46:49 +0000 [thread overview]
Message-ID: <201205161846.50784.luke@dashjr.org> (raw)
In-Reply-To: <CA+8xBpcFPdj9akeU9kN9CxERWp5VxKt7g0-mN4tf8NxsAe2+_w@mail.gmail.com>
On Wednesday, May 16, 2012 6:38:28 PM Jeff Garzik wrote:
> On Wed, May 16, 2012 at 2:29 PM, Luke-Jr <luke@dashjr•org> wrote:
> > That assumes you already have a connection to the peer in question.
> > As I understand it, the service bits are propagated as part of the
> > address, so you can see at a glance which nodes you want to connect to
> > for some special service. Passing a huge list along might be unwieldy
> > (though it makes sense for protocol changes that don't add new
> > services).
>
> If the peer list becomes too, um, stratified maybe that's a Big Hint
> that said clients should be using another network entirely, and not
> overloading bitcoin's P2P network for wholly unrelated tasks. The
> bitcoin P2P network is not a general message transit network.
>
> Another argument against the proposal, IOW, if you ask me....
No, I meant the inverse. If only a small minority of nodes are stratified,
the clients need some way to figure out which ones, without connecting to
every node.
prev parent reply other threads:[~2012-05-16 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 18:18 Jeff Garzik
2012-05-16 18:29 ` Luke-Jr
2012-05-16 18:38 ` Jeff Garzik
2012-05-16 18:46 ` Luke-Jr [this message]
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=201205161846.50784.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@exmulti$(echo .)com \
/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