public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Wladimir <laanwj@gmail.com>
To: Peter Todd <pete@petertodd.org>
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 12:23:57 +0200	[thread overview]
Message-ID: <CA+s+GJBw84dxc7pvJef-c=m7Dj0Cjy=O4PjNKB=5Bt2spM83OA@mail.gmail.com> (raw)
In-Reply-To: <20140617072351.GA7205@savin>

On Tue, Jun 17, 2014 at 9:23 AM, Peter Todd <pete@petertodd.org> wrote:
> 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.

Anyhow -- back to the original proposal. I'm fine with setting aside
part of the service bit space for experiments.

Wladimir



  parent reply	other threads:[~2014-06-18 10:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17  7:23 [Bitcoin-development] Proposal: allocate 8 service bits for experimental use 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
2014-06-18 10:23 ` Wladimir [this message]
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+GJBw84dxc7pvJef-c=m7Dj0Cjy=O4PjNKB=5Bt2spM83OA@mail.gmail.com' \
    --to=laanwj@gmail.com \
    --cc=Bitcoin-development@lists.sourceforge.net \
    --cc=pete@petertodd.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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