From: Anthony Towns <aj@erisian.com.au>
To: Matt Corallo <lf-lists@mattcorallo.com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] [BIP Draft] 24 bits for nVersion nonce space instead of 16
Date: Sat, 28 Mar 2026 21:58:07 +1000 [thread overview]
Message-ID: <acfCTzCqIalFuOdi@erisian.com.au> (raw)
In-Reply-To: <6fa0cb45-37d6-4b41-9ff8-03730fd96d6e@mattcorallo.com>
On Thu, Feb 26, 2026 at 05:12:03PM -0500, Matt Corallo wrote:
> ==Specification==
> 24 bits from the block header nVersion field, starting from 5 and ending at
> 28 inclusive (0x1fffffe0), are reserved for nonce use and removed from BIP8
> and BIP9 specifications. A mask of 0xe000001f should be applied to nVersion
> bits so bits 5-28 inclusive will be ignored for soft-fork signalling and
> unknown soft-fork warnings.
This conflicts with the proposed use of bit 5 for signalling CTV activation
over the next twelve months mentioned at:
* https://groups.google.com/g/bitcoindev/c/HC2bn4QOR-M/m/TF8qJidzAAAJ
* https://delvingbitcoin.org/t/bip-119-ctv-activation-client/2242
* https://github.com/ctv-activation/activation-client/blob/06ddbdf01bc8ce181b01c7497010bff74c2b79c6/src/kernel/chainparams.cpp#L121-L127
I don't think there's any meaningful support for that activation proposal,
but thought it was worth pointing out for completeness.
BIP110 is currently signalling via bit 4 until block 963648; LNHANCE
is possibly signalling on bit 3 between May last year and Jan 2028.
Previously, CSV signalled on bit 0, segwit on bit 1, segwit reduced
threshold (bip 91) on bit 4, and taproot on bit 2.
Cheers,
aj
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/acfCTzCqIalFuOdi%40erisian.com.au.
prev parent reply other threads:[~2026-03-28 13:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 22:12 Matt Corallo
2026-02-27 15:34 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2026-03-09 19:45 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2026-03-28 11:58 ` Anthony Towns [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=acfCTzCqIalFuOdi@erisian.com.au \
--to=aj@erisian.com.au \
--cc=bitcoindev@googlegroups.com \
--cc=lf-lists@mattcorallo.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