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.