From: Peter Todd <pete@petertodd•org>
To: Bitcoin-development@lists•sourceforge.net
Subject: [Bitcoin-development] Proposal: allocate 8 service bits for experimental use
Date: Tue, 17 Jun 2014 03:23:51 -0400 [thread overview]
Message-ID: <20140617072351.GA7205@savin> (raw)
[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]
For my replace-by-fee implementation(1) I used service bit 26 to let
preferential peering work so that replace-by-fee nodes could easily find
each other. Of course, that's a temporary/experimental usage that can be
dropped after wider adoption, so I included the following comment:
// Reserve 24-31 for temporary experiments
NODE_REPLACE_BY_FEE = (1 << 26)
Service bits are never a guaranteed thing anyway, so occasional
collisions can and should be tolerated by applications using these
experimental service bits.
Alternately Wladimir J. van der Laan brought up elsewhere(2) the
possibility for a wider notion of an extension namespace. I'm personally
not convinced of the short-term need - we've got 64 service bits yet
NODE_BLOOM is the first fully fleshed out proposal to use one - but it's
worth thinking about for the long term.
1) https://github.com/petertodd/bitcoin/tree/replace-by-fee-v0.9.1
2) https://github.com/bitcoin/bitcoin/pull/4351#issuecomment-46272958
--
'peter'[:-1]@petertodd.org
000000000000000058ca7ee3a40438ea5a96e499910638352468c6d69abdb226
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 685 bytes --]
next reply other threads:[~2014-06-17 7:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 7:23 Peter Todd [this message]
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
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=20140617072351.GA7205@savin \
--to=pete@petertodd$(echo .)org \
--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