From: "Sjors Provoost" <sjors@sprovoost.nl>
To: "Melvin Carvalho" <melvincarvalho@gmail.com>
Cc: "'Bitcoin Development Mailing List'" <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Bip54: add sequence, timestamp (and version) to GBT
Date: Tue, 10 Feb 2026 08:53:15 +0100 [thread overview]
Message-ID: <081ed43e-04e7-40d5-b61a-dc3957dc5d08@app.fastmail.com> (raw)
In-Reply-To: <CAKaEYh+cjFBx42vhag3dd1zF0QFbgXHPL0fBUDFcA4aZY63EvQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]
On Tue, Feb 10, 2026, at 06:12, Melvin Carvalho wrote:
>
>>
>> SegWit had its own BIP for adding fields, but that was a significantly bigger lift. My preference would be to just extend BIP54, as I've done below.
>>
>> Feel free to respond on the list or here: https://github.com/bitcoin/bips/pull/2097
>
> BIP54’s consensus fixes are currently uncontroversial.
>
> Bundling new getblocktemplate additions into it changes that and expands the policy surface. Those additions should be specified separately, where they belong.
Hi Melvin,
What do you mean by "policy surface" and how is it expanded? The fields do not add new rules to the proposal, they merely make implementation easier and safer.
Why do new fields "belong" elsewhere?
- Sjors
--
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/081ed43e-04e7-40d5-b61a-dc3957dc5d08%40app.fastmail.com.
[-- Attachment #2: Type: text/html, Size: 2152 bytes --]
prev parent reply other threads:[~2026-02-10 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 19:37 Sjors Provoost
2026-02-10 5:12 ` Melvin Carvalho
2026-02-10 7:53 ` Sjors Provoost [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=081ed43e-04e7-40d5-b61a-dc3957dc5d08@app.fastmail.com \
--to=sjors@sprovoost.nl \
--cc=bitcoindev@googlegroups.com \
--cc=melvincarvalho@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