Wiki / Concepts / Replace-by-fee (RBF)

Replace-by-fee (RBF)

From the Bitcoin Takeover Wiki · ✓ 12 sources · 0 podcast anchors · updated 2026-11-20
20082010201220142016Mike HearnPeter Todd▼ Replace-by-fee · 2015-12-04
Timeline generated from the dates of this article and the articles it links to. Click a label to open it.

Node policy that lets an unconfirmed transaction be replaced by one paying a higher fee: opt-in since 2015 (BIP-125), and full-RBF by default in Bitcoin Core 28.0.

◆ Takeover vieweditorial · opinion, labelled

The wiki's angle: RBF is the clearest case of a policy fight with no soft fork at all. Node defaults and miner incentives settled it, not a BIP activation.[11][10]

Opt-in RBF

BIP-125 lets a spender signal that a transaction may be replaced: a transaction opts in if any input has an nSequence number below 0xffffffff - 1[1]. Bitcoin Core merged opt-in RBF in PR #6871[2]. The project's FAQ says the change does not make a transaction without the signal easier to double-spend, and answers “Not in the slightest” to whether the pull request was controversial[3].

The 2015 and 2022 arguments

In March 2015 Mike HearnMike HearnPersonFormer Google engineer, bitcoinj author and co-creator of Bitcoin XT, who declared Bitcoin a failed experiment in January 2016. argued on the bitcoin-dev list that replace-by-fee “scorched earth” was harmful, and Peter ToddPeter ToddPersonBitcoin developer behind CHECKLOCKTIMEVERIFY and replace-by-fee, a Hong Kong Roundtable signer and a SegWit2x opponent. replied by asking for a list of companies that actually relied on first-seen mempool behaviour[4]. In 2022 PR #25353 added a node option, -mempoolfullrbf, to replace transactions without the signal, and Bitcoin Core 24.0 shipped it off by default[5][6]. Muun's Dario Sneidermanis warned that zero-conf apps like Muun “must immediately turn off their zero-conf features” (emphasis in the original)[7]. A pull request to temporarily disable the option on mainnet was closed, after Murch argued that relying on zero-conf had long been described as bad practice[8].

Full-RBF becomes the default

In October 2022 Peter Todd wrote “Let's see if miners can be bribed to run full-RBF, starting small.”[9] In March 2024 he wrote that ViaBTC had turned it on, putting “something like 95%+ hash power” on full-RBF[10]. Bitcoin Core 28.0 changed the default to mempoolfullrbf=1[11]. The BIP Atlas dossier collects the quotes from both sides[12].

References

  1. primaryBIP-125 (Opt-in Full Replace-by-Fee Signaling), authors David A. Harding and Peter Todd [archived]
  2. primaryBitcoin Core PR #6871, opt-in full-RBF (BIP 125) — merged Nov 2015
  3. primarybitcoincore.org, Opt-in RBF FAQ
  4. primarybitcoin-dev, Peter Todd replying to Mike Hearn on replace-by-fee (28 Mar 2015), b10c mirror
  5. primaryBitcoin Core PR #25353, add a -mempoolfullrbf node setting — merged
  6. primaryBitcoin Core 24.0 release notes
  7. primarybitcoin-dev, Dario Sneidermanis (Muun), “Full-RBF peer discovery” / zero-conf warning (7 Oct 2022), b10c mirror
  8. primaryBitcoin Core PR #26287, “Temporarily disable -mempoolfullrbf for the main chain” — closed
  9. primary@peterktodd on X, 31 Oct 2022: full-RBF bribes
  10. primary@peterktodd on X, 28 Mar 2024: ViaBTC turns on full-RBF
  11. primaryBitcoin Core 28.0 release notes
  12. primarybitcoin/bips repository [archived]

Related articles

Categories: Concepts
Ask about this article: >_ terminal · Onion mirror: http://btctkvroa6xsq25wmpvvlpkcgss7724zk6fm765fvtuunfgxw74j2pyd.onion/wiki/replace-by-fee/
>_ ask the wiki