public inbox for
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd•org>
To: Bitcoin Error Log <bitcoinerrorlog@gmail•com>
Cc: Bitcoin Development Mailing List <>
Subject: Re: [bitcoindev] Draft BIP for User-Defined Transaction Flags Policy & Strategy
Date: Sun, 14 Apr 2024 15:51:34 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 2091 bytes --]

On Sun, Apr 14, 2024 at 08:09:51AM -0700, Bitcoin Error Log wrote:
> Adoption and Transition Strategy & Requirements
> It is implicit, until now, that within this strategy is a requirement for 
> Core and other implementations to abandon strategies within Option 2, by 
> specifically removing and rejecting policy tools like mempoolfullrbf, or 
> other attempts to overrule, filter, or otherwise filter and hamper the 
> propagation of valid, non-destructive transactions.

For the record, I will continue to distribute both my Libre Relay¹ and Full-RBF
Peering² forks of Bitcoin Core, and they will continue to propagate full-rbf
replacements. I'd estimate roughly 30 nodes in total on the P2P network are
running one of those two forks. Bitcoin Knots also enables full-RBF by default,
and has something like 150 nodes.

90%+ of hash rate is running full-RBF because it's common for blocks to earn
thousands of dollars worth of fees from full-RBF replacements.  The idea that
miners would give that up, en-mass, just because you asked nicely for the sake
of your broken, insecure, and unused ways of transacting bitcoin is laughable.
Miners regularly modify the Bitcoin Core codebase for their own needs;
commenting out the one line of code that prevents full-RBF replacements is

You'd do well to stop wasting your time with this nonsense and work on
Lightning or something. As for Bitcoin Core, enabling full-RBF by default is
well overdue:


-- 'peter'[:-1]

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 on the web visit

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-04-14 15:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-14 15:09 Bitcoin Error Log
2024-04-14 15:51 ` Peter Todd [this message]
2024-04-14 20:12 ` Isaac Eiter
2024-04-15 18:58 ` Keagan McClelland
2024-04-16  2:01   ` Antoine Riard

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \
    --to=pete@petertodd$(echo .)org \ \
    --cc=bitcoinerrorlog@gmail$(echo .)com \
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