From: Tier Nolan <tier.nolan@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Services bit for xthin blocks
Date: Mon, 7 Mar 2016 21:09:12 +0000 [thread overview]
Message-ID: <CAE-z3OWyzxSxyEma9MXnOzOcirea=HcR_gps20fDwGxVnxuZ+Q@mail.gmail.com> (raw)
In-Reply-To: <CAHUwRvuR9qtYc+rVh1yPbQoESxm4m0r6a+Fd6VF=FuT0vom_HQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]
These are the relevant info BIPs.
NODE_GETUTXO
https://github.com/bitcoin/bips/blob/master/bip-0064.mediawiki
NODE_BLOOM:
https://github.com/bitcoin/bips/blob/master/bip-0111.mediawiki
The relevant code is here:
https://github.com/bitcoin/bitcoin/blob/master/src/protocol.h#L228
The NODE_GETUTXO bit was included even though it is not supported by core.
(It is one of XT's features).
I think you need to be able to reasonably claim that the bit is useful and
will have actual users, before you can claim a bit.
You can also claim one of the free for all bits 24 - 31, but that is
supposed to be only temporary.
Giving a link to "thin blocks" would help promote discussion about its
merits.
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.
>
> Andrew
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
[-- Attachment #2: Type: text/html, Size: 2318 bytes --]
prev parent reply other threads:[~2016-03-07 21:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 20:06 G. Andrew Stone
2016-03-07 20:51 ` Gregory Maxwell
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 ` Tier Nolan [this message]
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='CAE-z3OWyzxSxyEma9MXnOzOcirea=HcR_gps20fDwGxVnxuZ+Q@mail.gmail.com' \
--to=tier.nolan@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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