From: Wladimir <laanwj@gmail•com>
To: Jeff Garzik <jgarzik@bitpay•com>
Cc: Bitcoin Dev <Bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal: allocate 8 service bits for experimental use
Date: Wed, 18 Jun 2014 08:20:26 +0200 [thread overview]
Message-ID: <CA+s+GJB-PziMMYDJMFYX6vAu-FCfugeJrNe+n3aLokFcFvzvEA@mail.gmail.com> (raw)
In-Reply-To: <CAJHLa0Mk5E4ubQ2MZcdrG3fAm5KAATKsSgxnN8VKN1W=uBU0Og@mail.gmail.com>
On Tue, Jun 17, 2014 at 11:29 PM, Jeff Garzik <jgarzik@bitpay•com> wrote:
> I wrote a patch for string-based name extensions, circa 2011-2012. I
> agree that is preferable to unreadable bits, for reasons you cite.
>
> However, it was noted that extensions (or UUIDs etc.) would not be
> propagated around the network in "addr" messages, as service bits are.
Thanks for letting me know, I didn't remember your patch.
Ugh, yes, propagating all extensions in `addr` messages is not how I
imagined this to work.
But then there would need to be an alternative way to discover nodes
that offer a certain extension. Alas, this moves it from a
straightforward and common sense change to a significant change to the
protocol.
Wladimir
next prev parent reply other threads:[~2014-06-18 6:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 7:23 Peter Todd
2014-06-17 7:57 ` Wladimir
2014-06-17 8:02 ` Matt Whitlock
2014-06-17 8:08 ` Wladimir
2014-06-17 8:16 ` Wladimir
2014-06-17 21:29 ` Jeff Garzik
2014-06-18 6:20 ` Wladimir [this message]
2014-06-18 10:23 ` Wladimir
2014-06-18 11:48 ` Jeff Garzik
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+s+GJB-PziMMYDJMFYX6vAu-FCfugeJrNe+n3aLokFcFvzvEA@mail.gmail.com \
--to=laanwj@gmail$(echo .)com \
--cc=Bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@bitpay$(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