From: Jeff Garzik <jgarzik@exmulti•com>
To: Amir Taaki <zgenjix@yahoo•com>
Cc: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] P2P feature discovery (was Re: BIP 33 - Stratized Nodes)
Date: Wed, 16 May 2012 14:18:27 -0400 [thread overview]
Message-ID: <CA+8xBpd-0nXdda4fwyFonEY6rOSSyt=5goD-rbMTpvkcuHNTog@mail.gmail.com> (raw)
On Wed, May 16, 2012 at 12:34 PM, Amir Taaki <zgenjix@yahoo•com> wrote:
> Please check out my proposal,
>
> https://en.bitcoin.it/wiki/BIP_0033
>
> I want to use the existing Bitcoin protocol to provide this functionality in order to maintain compatibility. This proposal does not affect current Bitcoin clients, but allows the parallel system to operate alongside and sometimes intersect with the main Bitcoin network in a positive way.
I do not object to the concept, but the discovery process should be
improved. Even venerable SMTP has a better, more flexible
capabilities discovery process.
Instead of further overloading service bits in the version message, or
altering the version message, let us instead make feature discovery an
easy, flexible, extensible process.
We can add new commands without impacting older nodes, so let's create
a new command "get-features" (or pick your name) that returns a list
of key/value pairs. The key is a string, the value type is determined
by the key.
Standard behavior of clients would be to send "get-features" after
seeing remote version info, as part of the initial connection
handshake.
In any case, the basic point is to move FAR away from fighting over a
limited, inflexible resource (service bits in "version" msg) to
something string-based and easily extensible.
I can create this as BIP 34, if people wish.
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti•com
next reply other threads:[~2012-05-16 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 18:18 Jeff Garzik [this message]
2012-05-16 18:29 ` Luke-Jr
2012-05-16 18:38 ` Jeff Garzik
2012-05-16 18:46 ` Luke-Jr
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='CA+8xBpd-0nXdda4fwyFonEY6rOSSyt=5goD-rbMTpvkcuHNTog@mail.gmail.com' \
--to=jgarzik@exmulti$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=zgenjix@yahoo$(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