Your Bitcoin transaction is still waiting. A wallet offers a fee increase; another mentions a child transaction. Those tools change different things, so the useful first question is which transaction or output your wallet can control.
This explainer concerns onchain Bitcoin, not Lightning or BTC represented on another network. The implementation examples use Bitcoin Core's 31.0 exported RPC documentation and version 31.1 source policy, checked 14 October 2026. They are not a claim about every wallet. No node, wallet, keys or real transaction is used here.
RBF replaces a conflicting transaction
Replace-by-fee proposes another transaction that spends an input already spent by an unconfirmed transaction. They conflict: both cannot spend that same output in the same valid chain. An accepted replacement changes the transaction the node keeps, not a confirmed block.
Bitcoin Core's bumpfee documentation describes replacing a wallet transaction while retaining all its original inputs. Additional fees can come from reducing change or adding inputs; a change output can be created if needed. Change is the portion of an input's value returned to the sender, not a separate cashback reward.
Keeping the intended recipient and payment amount unchanged still needs checking in the replacement. The documented RPC also permits custom outputs, so a button labelled "increase fee" is not evidence that every payment detail stayed the same. The replacement has a new transaction ID.
If the replacement is confirmed instead, its transaction fee applies. You do not add the abandoned original candidate's fee to it as though both conflicting spends confirmed on the same chain. A new unrelated payment, however, may not conflict with the first and can become a second payment.
CPFP adds a dependent child
Child-pays-for-parent creates a new transaction spending an output of an unconfirmed parent. A block containing that child needs the parent first if the parent has not already confirmed. The child can therefore make including the combination more attractive through its additional fee.
For a sender, the usable output may be change. A recipient who controls the payment output may also have a possible child, if their wallet supports spending that unconfirmed output. An output that your wallet cannot spend is not available simply because you can see it on an explorer.
This preserves the parent rather than replacing it. If both transactions confirm, both fees are paid. Bitcoin Core's package policy explains child-with-parents relationships and fee accounting. Relay and wallet support still matter; creating a child does not reserve block space.
| Question | RBF | CPFP |
|---|---|---|
| What changes? | A conflicting replacement is proposed | A new child spends an unconfirmed output |
| What needs control? | Inputs and the ability to construct/sign the replacement | A spendable parent output and support for an unconfirmed spend |
| Does the original stay? | It competes with the replacement | The child depends on it |
| What fees matter? | The replacement's fee and applicable replacement rules | Fees and virtual sizes of the required unconfirmed set |
| What is not promised? | Acceptance, inclusion or cancellation | Package propagation, inclusion or account credit |
Wallet eligibility and node policy are separate
The version 31.1 wallet implementation rejects fee bumps when the original has wallet or mempool descendants, is mined or conflicts with a mined transaction, or has already been marked replaced. Its normal bumpability check also requires the original inputs to belong to that wallet. A wallet record, signing capability and adequate funding are separate prerequisites.
Bitcoin Core's version 31.1 replacement policy no longer requires opt-in RBF signalling. Do not turn an older "RBF flag required" rule into a universal statement about today's network. A wallet or another node can still have different support and policy.
A higher sat/vB number alone is not the entire admission test. The replacement must satisfy applicable rules, including absolute fees, the incremental relay fee and improvement of the mempool's fee-rate diagram. Bitcoin Core's 31.0 release notes describe the cluster-mempool change. Older ancestor/descendant limits and the removed CPFP carveout should not be presented as this version's current policy.
For CPFP, check whether an unconfirmed output you control exists and whether the wallet can use it. Sending all input value to a recipient may leave no sender-controlled change to spend. That is different from RBF funding: Core's replacement flow may add inputs, subject to its checks.
Worked example: count both CPFP sizes
Here, sat means satoshis and vB means virtual bytes. A fee rate in sat/vB divides the transaction's fee by its virtual size; the total fee is the amount the transaction pays overall. A high child fee rate does not automatically give the whole parent-and-child pair that rate.
These are invented teaching numbers, not a live fee quote or a suggested rate. Assume one unconfirmed parent, one child, no other unconfirmed dependencies, no fee adjustments, sufficient spendable value and the exact virtual sizes below. Real signing and input selection can change the size and fee.
| Transaction | Virtual size | Fee | Fee rate |
|---|---|---|---|
| Original parent | 200 vB | 400 sat | 2 sat/vB |
| Proposed CPFP child | 150 vB | 3,100 sat | About 20.67 sat/vB |
| Parent plus child | 350 vB | 3,500 sat | 10 sat/vB |
For the illustrative combined rate of 10 sat/vB:
Required combined fee = 10 sat/vB × (200 vB + 150 vB)
= 3,500 sat
Child fee = 3,500 sat − 400 sat
= 3,100 sat
Giving the child alone 10 sat/vB would pay 1,500 sat. With the parent's 400 sat, the pair would pay 1,900 sat across 350 vB, or about 5.43 sat/vB, not 10. The parent consumes block space too.
This simplified combined-rate calculation is not a simulation of Core's package admission. Its documented acceptance accounting excludes transactions already accepted individually when avoiding double-counting. Larger dependency sets and cluster policy need their own analysis; the table does not certify an arbitrary package.
For a separate RBF illustration, suppose the replacement is 220 vB, rather than 200, and pays 2,200 sat. Its rate is 10 sat/vB; its absolute fee is 1,800 sat above the original's 400 sat. That arithmetic does not establish acceptance, the required live fee or a confirmation time. Review the wallet's actual replacement, not the old transaction's size.
The two Core RPCs are not interchangeable
The 31.0 psbtbumpfee reference returns an unsigned partially signed Bitcoin transaction, or PSBT, for a replacement. It does not itself complete signing and broadcast. Core's bumpfee flow signs and commits/broadcasts the replacement, as shown by its documentation and wallet implementation.
Producing a PSBT is a preparation step, not evidence that a miner or node accepted a transaction. The final inputs, outputs and fee still need review before any real signing. This article provides no executable RPC commands, wallet access or signing procedure.
Dropped, confirmed and exchange-held mean different things
An explorer or node not showing a transaction does not prove it disappeared from every peer. A local mempool is not a global cancellation register. Core's abandontransaction reference describes local wallet bookkeeping for eligible transactions absent from a block and that node's mempool. It is not a message ordering every node to forget the payment.
Once the payment is confirmed on the active chain, the unconfirmed fee-bumping workflow is not a refund tool. RBF attempts before confirmation are not guaranteed cancellation either: the original can confirm first. CPFP deliberately depends on the parent's spend rather than undoing it. Confirmation counts and reorganisations need their own interpretation.
With an exchange or custodial service, an account balance is not control over the withdrawal transaction's inputs or change. The sending service controls that construction. For an exchange deposit, inclusion is separate from internal credit. Follow the service's official transaction/deposit investigation route, not a stranger's "accelerator" requiring recovery words.
Before choosing a fee-bumping tool
Identify the transaction's actual network and current status. For an unconfirmed onchain Bitcoin payment, ask:
- Does my wallet control the original inputs and support an eligible replacement?
- Is there an unconfirmed output I can spend, and does the wallet support that child?
- Have descendants, a prior replacement or a confirmation changed the situation?
- What are the actual new size, total fee and remaining payment outputs?
- Is the delay in chain inclusion or in the recipient service's own account processing?
RBF and CPFP offer different ways to change fee incentives. Wallet capability, valid spends and node policy determine whether a proposal can proceed; miners determine inclusion. The network-fee explanation and Bitcoin spend model supply useful background before any transaction decision.
Sources
Primary documentation checked 14 October 2026. This is a version-scoped explainer, not an October release announcement. Arithmetic is hypothetical. No Bitcoin node, wallet, transaction, exchange account, cancellation, recovery or inclusion-time claim was tested.
- Bitcoin Core 31.0: bumpfee: replacement inputs, change/funding, options and fee units.
- Bitcoin Core 31.0: psbtbumpfee: unsigned replacement PSBT and prerequisites.
- Bitcoin Core 31.1: wallet fee bumper: wallet eligibility, fee checks and signing/commit path.
- Bitcoin Core 31.1: replacement policy: absolute fees, relay increment, full-RBF and fee-rate diagram.
- Bitcoin Core 31.1: package policy: child-parent relationships and package fee accounting.
- Bitcoin Core 31.0 release notes: cluster mempool and removed carveout.
- Bitcoin Core 31.0: abandontransaction: local wallet bookkeeping, not global cancellation.
See something wrong? Brokzi logs material changes. Prepare a correction note.




