Subject: Re: [bitcoindev] Re: Relax OP_RETURN standardness restrictions

From: Peter Todd <[email-masked]>
Date: Fri, 2 May 2025 20:10:07 +0000

On Fri, May 02, 2025 at 12:04:13PM -0700, /dev /fd0 wrote:
> Config `mempoolfullrbf` was added in July 2022: 
> https://github.com/bitcoin/bitcoin/pull/25353
> It was made default in August 2024: 
> https://github.com/bitcoin/bitcoin/pull/30493
> Option was removed in November 2024: 
> https://github.com/bitcoin/bitcoin/pull/30592
> 
> `datacarrier` and `datacarriersize` already exist, so why is it a big deal 
> to remove them after a few months of monitoring the usage with stats? 

The `mempoolfullrbf` option was a good example of how keeping an option
to reject otherwise standard transactions is just wasted effort. Having
the option didn't stop full-rbf replacements from getting mined; user's
refusing to relay a transaction type that a significant % of miners are
mining acomplishes nothing.

In that *specific* case there were a tiny number of users, Wasabi's
Coordinator being an example, where for technical reasons full-rbf
replacements caused problems until that code was fixed; giving those
users an option to temporarily disable those replacements was sort of
useful. But there's no reason to think that will be true with OP_Return
outputs, and in any case, you can just delaying upgrading your node
while you fix your broken code.

-- 
https://petertodd.org 'peter'[:-1]@petertodd.org

-- 
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 [email-masked].
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/aBUmn9HIYj06vbsX%40petertodd.org.