public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gregory Maxwell <greg@xiph.org>
To: "G. Andrew Stone" <g.andrew.stone@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Services bit for xthin blocks
Date: Mon, 7 Mar 2016 20:51:00 +0000	[thread overview]
Message-ID: <CAAS2fgQi1X4v9WxT1pnd_XSyE2b8hUZUv0z5A8cOEvw5RztOKw@mail.gmail.com> (raw)
In-Reply-To: <CAHUwRvuR9qtYc+rVh1yPbQoESxm4m0r6a+Fd6VF=FuT0vom_HQ@mail.gmail.com>

On Mon, Mar 7, 2016 at 8:06 PM, G. Andrew Stone via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> The Bitcoin Unlimited client needs a services bit to indicate that the node
> is capable of communicating thin blocks.  We propose to use bit 4 as AFAIK
> bit 3 is already earmarked for Segregated Witness.

Does this functionality change peer selection?  If not, the preferred
signaling mechanism is probably the one in BIP 130.

Otherwise, I think the standard method for getting numbers has been to
write a BIP documenting the usage. I don't know if that is intentional
or just how things have previously happened; and I don't have much of
an opinion on it.


  reply	other threads:[~2016-03-07 20:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-07 20:06 [bitcoin-dev] Services bit for xthin blocks G. Andrew Stone
2016-03-07 20:51 ` Gregory Maxwell [this message]
2016-03-07 21:10   ` dagurval
2016-03-08  2:35     ` G. Andrew Stone
2016-03-08 17:19       ` Luke Dashjr
2016-03-09 18:11         ` G. Andrew Stone
2016-03-09 21:11           ` Tier Nolan
2016-03-08  5:14   ` Dave Scotese
     [not found]     ` <CAAS2fgSf_qYaT7ahQTbmRoQpG57qgF26NKVuGGaEzpMZmCOFoA@mail.gmail.com>
2016-03-08  6:09       ` [bitcoin-dev] Fwd: " Gregory Maxwell
2016-03-07 21:09 ` [bitcoin-dev] " Tier Nolan

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=CAAS2fgQi1X4v9WxT1pnd_XSyE2b8hUZUv0z5A8cOEvw5RztOKw@mail.gmail.com \
    --to=greg@xiph.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=g.andrew.stone@gmail.com \
    /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