RBF and CPFP are the two real, self-service ways to speed up a stuck Bitcoin transaction. Both work without paying a third party. Both fix the same underlying problem, a fee too low for current conditions, but through completely different mechanisms.
This guide breaks down exactly how each method works and when to use one over the other. It also covers the specific limitations that determine which fix actually applies to your situation. Once your Bitcoin confirms, Coinstick’s sell page converts it to naira in seconds.
- RBF replaces the original transaction. It rebroadcasts the same spend with a higher fee attached.
- CPFP adds a new transaction instead. It spends an output of the stuck one to pull both into the same block.
- RBF requires the sender’s cooperation. Only the original sender’s wallet can trigger it.
- CPFP works for either party. Both the sender and the recipient can potentially use it, depending on who holds spendable outputs.
What RBF Actually Does
“Diagram of RBF vs CPFP showing how each method speeds up a stuck bitcoin transaction”
Replace-By-Fee lets you rebroadcast your original transaction with a higher fee attached, spending the exact same inputs. The network treats this new version as a replacement, not a duplicate. It drops the old one from the mempool once the new one propagates.
This mechanism only works if your wallet actually broadcasts the original transaction as replaceable. Most modern wallets do this by default, following Bitcoin Core’s full-RBF policy shift in its 28.0 release.
What CPFP Actually Does
Child-Pays-For-Parent works from the opposite direction. Instead of replacing the stuck transaction, you create a brand new one that spends an output from it. You attach a high fee to this new transaction.
Miners evaluate the combined package, the stuck “parent” and the new “child,” together. A high enough child fee makes the whole package profitable enough to include in the next block, pulling the parent along with it.
The Core RBF vs CPFP Difference In One Sentence
RBF replaces a transaction. CPFP adds a new one that depends on it. This single distinction explains almost every practical difference between the two methods covered in this guide.
Understanding this difference tells you immediately which one applies to your situation. Each mechanism requires a specific condition to be true first.
When RBF Is Your Only Practical Choice
RBF is the simpler, cheaper option whenever it’s available. It requires no additional transaction and no extra block space beyond the original. It typically costs just the fee difference between your old and new rate.
Most wallets built after 2023 support one-tap RBF bumping directly in the transaction history. If your wallet offers this button, RBF should almost always be your first attempt before considering anything else.
When CPFP Becomes Necessary Instead
CPFP becomes necessary specifically when RBF isn’t available. Most commonly, that’s because the original transaction wasn’t flagged as replaceable when it was broadcast. Older wallets, or wallets configured with RBF disabled, produce this exact situation.
CPFP is also the only option available to a transaction’s recipient. The sender’s wallet controls RBF eligibility, not the recipient’s.
Step By Step: How To Apply RBF
Most modern wallets surface a “bump fee” or “speed up” option directly next to a pending transaction in your history. Tapping this typically calculates a new suggested fee automatically, based on current network conditions.
Confirming the bump broadcasts the replacement transaction immediately. From there, the process works exactly like any normal Bitcoin send, just with a higher fee attached to the same underlying spend.
Step By Step: How To Apply CPFP
Applying CPFP manually requires identifying an unspent output from the stuck transaction. You then construct a new transaction that spends it at a high fee. Some modern wallets automate this entirely with a single “accelerate” button.
Without built-in support, this process requires more technical comfort. You’re manually selecting inputs and calculating an appropriate fee, rather than relying on a guided interface.
Cost Comparison: RBF vs CPFP
“Bar chart comparing the fee cost of RBF vs CPFP in a worked bitcoin example”
RBF typically costs less overall, since you’re only paying the fee difference on a single transaction rather than funding two separate ones. A modest bump, from an underpriced rate to a competitive one, often costs just a small fraction of the original transaction’s value.
CPFP costs more by design, since the child transaction needs its own fee, high enough to subsidize the entire combined package. This makes CPFP the pricier option even when both methods are equally available.
Speed Comparison: RBF vs CPFP
Both methods typically achieve inclusion within one to three blocks once applied correctly, assuming the new fee rate genuinely clears current market conditions. Neither method is inherently faster than the other in a well-functioning scenario.
The real speed difference comes from setup time. RBF’s one-tap process in a modern wallet moves faster than CPFP’s more manual construction process. This gap widens for someone without built-in accelerate support.
Wallet Support: RBF vs CPFP
RBF support has become nearly universal across modern wallet software, mobile and hardware alike. This follows the shift to full-RBF as network-wide default policy. Checking your specific wallet’s settings confirms whether the feature ships enabled. Coinstick’s crypto wallet page also covers general network basics for the assets it supports.
CPFP support varies considerably more. Some wallets build in a guided “accelerate” feature. Others require manually constructing the child transaction through advanced settings or a separate tool.
Can You Use Both RBF And CPFP Together
In rare, especially stubborn cases, applying CPFP to a transaction you’ve already bumped with RBF is technically possible. This is rarely necessary in practice, though. Most situations resolve with one method or the other alone.
Attempting both simultaneously without understanding the interaction risks confusion, since you’re now tracking multiple related transactions rather than one straightforward fix. Reserve this combined approach for a genuinely unusual, persistent case.
RBF Limitations You Should Know
RBF only works if the original transaction actually broadcasts as replaceable, a flag set at creation time by the sending wallet. A transaction sent from an exchange or older wallet software might not carry this flag at all.
Full-RBF relay policy adoption also varies slightly across the network’s nodes and mining pools. This has become far less of a practical concern, though, since full-RBF became the dominant standard.
CPFP Limitations You Should Know
CPFP only works if you actually control a spendable output from the stuck transaction. A sender with no remaining balance tied to that specific transaction has nothing left to attach a child transaction to.
CPFP also requires paying for two transactions’ worth of block space, not one. This makes it inherently costlier than a straightforward RBF bump whenever both methods are actually available.
A Worked Example: Applying RBF
Say your transaction sat unconfirmed for two hours with a fee rate of 4 satoshis per virtual byte. The current recommended rate sits at 18. Your wallet’s bump-fee feature recalculates and rebroadcasts at roughly 20 satoshis per virtual byte.
This single action typically confirms within one to two blocks. The entire cost is just the fee difference, roughly 16 satoshis per virtual byte multiplied by the transaction’s size in virtual bytes.
A Worked Example: Applying CPFP
Say the same transaction wasn’t flagged as replaceable, ruling out RBF entirely. You identify a 0.01 BTC change output from that stuck transaction still under your control.
You construct a new transaction spending that output. The fee needs to be high enough to make the combined parent-and-child package attractive at current market rates. Miners then include both transactions together in the next available block.
Choosing Between RBF And CPFP: A Simple Decision Tree
“Decision tree for choosing RBF vs CPFP to fix a stuck bitcoin transaction”
Check first whether your wallet flagged the original transaction as replaceable. RBF is almost always your best option here, being cheaper and simpler. When it’s not flagged, check whether you control a spendable output from that transaction instead.
Controlling an output means CPFP becomes your path forward. Neither condition applying, especially as a recipient with no controllable output, points you toward contacting the sender or considering a legitimate accelerator service instead.
Why RBF Became The Default Recommendation
RBF’s rise to default status reflects a broader shift in Bitcoin development toward giving senders more direct control over their own transactions. Before full-RBF, a poorly estimated fee could leave a sender with genuinely limited recourse.
This shift also reduced reliance on third-party accelerator services considerably. Most stuck-transaction cases today resolve through a sender’s own wallet, not external help.
Common Mistakes When Choosing Between RBF And CPFP
Attempting CPFP when RBF was actually available wastes money unnecessarily. CPFP’s extra transaction cost provides no benefit over the simpler, cheaper alternative in that situation. Checking RBF eligibility first avoids this mistake entirely.
Assuming CPFP is impossible without checking for an actual spendable output is the opposite mistake. Many recipients don’t realize they can use CPFP on funds they’ve received but not yet spent.
RBF vs CPFP Risk Matrix
“Comparison matrix of RBF vs CPFP across cost, difficulty, wallet support, and who can use it”
| Factor | RBF | CPFP |
| Who can use it | Original sender only | Sender or recipient with a spendable output |
| Typical cost | Fee difference only | Fee difference plus a second transaction |
| Wallet support | Nearly universal in 2026 | Varies, growing but inconsistent |
| Technical difficulty | Low, often one tap | Moderate without built-in support |
How Miners Evaluate A Parent And Child Together
Miners don’t judge a stuck parent and its child separately. They calculate an ancestor fee rate for the whole package. That number divides the combined fees by the combined size of both transactions.
This is why a well-funded child can rescue a weak parent. The high fee on the child lifts the average, and the package suddenly looks attractive. Miners can then include both transactions in the next block they build.
The Rules Bitcoin Enforces On Replacements
Nodes don’t accept just any replacement. A replacement transaction generally has to pay a higher total fee than the transaction it replaces. It also has to pay for its own relay bandwidth, which keeps spammers from flooding the network with tiny bumps.
Other limits exist too. A replacement usually can’t evict an enormous number of dependent transactions, and it shouldn’t add brand new unconfirmed inputs. Wallets that offer a bump button handle these rules for you automatically.
Why A Tiny Fee Bump Sometimes Fails
Some people try to bump a fee by a single satoshi and wonder why nothing happens. Nodes require the new fee to exceed the old one by a minimum margin. A token increase gets rejected before it ever reaches a miner.
Wallets avoid this problem by calculating a sensible increase for you. If you’re bumping manually, add a comfortable margin above the current recommended rate instead of nudging the number up slightly.
A Numeric Walkthrough Of An RBF Bump
Picture a transaction of 200 virtual bytes sent at 4 satoshis per virtual byte. The original fee equals 800 satoshis. The recommended rate has climbed to 20, so a competitive fee would total 4,000 satoshis.
Bumping to 20 satoshis per virtual byte means the replacement pays 4,000 satoshis. Your extra cost is the 3,200 satoshi difference. That’s the entire price of the fix, with nothing paid to any outside service.
A Numeric Walkthrough Of A CPFP Package
Now imagine the same 200-byte parent stuck at 4 satoshis per virtual byte. You spend its change output in a child of 150 virtual bytes. The parent and child together total 350 virtual bytes.
To hit an average of 20 satoshis per virtual byte, the package needs 7,000 satoshis in total fees. The parent already paid 800. The child must therefore pay 6,200 satoshis, which is far more than the 3,200 the RBF route would have cost.
What This Math Reveals
CPFP costs more because the child has to make up the parent’s shortfall on top of paying for its own space. The parent’s low fee doesn’t disappear. Someone still has to cover the gap for the package to compete.
This is the clearest numeric reason to prefer RBF whenever it’s available. The same stuck transaction costs almost double to fix through CPFP in this example.
Transaction Pinning And Why It Matters
Pinning describes a situation where a transaction becomes hard to replace or accelerate. Someone attaches a large, low-fee child to your stuck transaction. Replacing the parent then requires beating the total fees of everything attached to it.
Most ordinary users never encounter pinning. It matters mainly in multi-party setups like shared wallets and payment channels. Recent Bitcoin Core work on package relay and new transaction policies aims to reduce this problem.
Package Relay And Why Developers Built It
Traditionally, nodes evaluated each transaction on its own before accepting it. A parent with a fee below the minimum relay threshold could get rejected, even if its child offered a generous fee. That made CPFP unreliable in exactly the situations people needed it most.
Package relay lets nodes evaluate a parent and child together. Bitcoin Core has been rolling out limited forms of this feature in recent releases. Wider adoption makes CPFP more dependable over time.
How Lightning Channels Rely On Fee Bumping
Lightning channel closures often need a fee bump at exactly the wrong moment. Channel software uses special anchor outputs that allow a CPFP-style bump after the fact. This design lets a channel close without guessing future fees in advance.
Regular users don’t manage this directly. Their Lightning wallet handles it in the background. It’s still a good example of how CPFP became a core building block rather than just a rescue tool.
Cancelling A Payment With RBF
RBF can double as a cancellation tool. You rebroadcast the same inputs, but send the funds back to an address you control instead of the original recipient. If the replacement confirms first, the original payment never happens.
This only works while the original sits unconfirmed. Once a miner includes the original in a block, nothing can reverse it. Speed matters if cancellation is your actual goal.
What Happens If Your Replacement Also Stalls
Fee markets keep moving, so a bump that looked generous can become stale within hours. You can bump again, provided your wallet allows repeated replacements. Each new version must pay more than the last.
Checking current recommended rates before each attempt prevents wasted effort. A larger jump on the second try often works better than several small increments spread over a day.
RBF And Zero-Confirmation Payments For Merchants
Merchants sometimes accept a payment the moment it appears in the mempool, before any confirmation. Full-RBF makes this riskier. A buyer could replace the payment with one that sends the funds elsewhere.
Careful merchants wait for at least one confirmation on meaningful amounts. Small, low-risk purchases may still justify instant acceptance, but the risk should be a conscious decision, not an assumption.
Fee Estimation Habits That Reduce The Need For Either Method
Both RBF and CPFP are repair tools. The better strategy is choosing a sensible fee upfront. A quick look at a live fee estimator before sending prevents most problems.
Choosing a target confirmation time also helps. A payment needed within an hour deserves a higher rate than a transfer that can wait until tomorrow. Matching the fee to your real deadline saves money and stress. Live reference pages, like Coinstick’s Bitcoin rate page for price, follow the same check-before-you-act habit.
Testing Your Wallet’s Bump Feature Safely
Practice on a small amount before you face a real emergency. Send a tiny payment at a deliberately low fee, then try the bump button. Watching the process work once removes most of the fear.
Keep the amount small enough that a mistake wouldn’t matter. Learning your wallet’s interface in a calm moment beats figuring it out while a large payment sits stuck.
Security Rules When Bumping A Fee
A legitimate bump happens inside your own wallet or through your exchange’s support team. No website should ask for your seed phrase or private key to bump a fee. Any request like that signals theft, not help.
Stay inside tools you already trust. If someone contacts you unprompted offering to speed up your transaction, treat it as a scam attempt and ignore it.
Sequence Numbers And The Replaceable Flag
Every Bitcoin transaction input carries a sequence number. Under the older opt-in system, a low sequence value told nodes the transaction could be replaced. Wallets that set this flag by default made RBF possible without extra effort.
Full-RBF changed the picture by ignoring that flag in relay policy. Even so, sensible wallets still set it, and older transactions without it remain the main reason people need CPFP today.
What Full-RBF Changed In Practice
Before full-RBF, a sender who forgot the flag had no direct way to bump a stuck payment. Recipients had CPFP, and everyone else waited. That gap created most of the demand for paid accelerator services.
Today, senders hold far more control. A stuck payment from a modern wallet usually needs nothing more than a fee bump. The change shifted the whole conversation from paying outsiders toward fixing the problem yourself.
A Short History Of Fee Bumping
Early Bitcoin offered no clean way to fix an underpriced payment. Users either waited or asked a miner for a favor. Mining pools eventually built accelerator tools to fill the gap and charge for the service.
Opt-in replacement arrived later and gave wallets a standard tool. Full-RBF then made that tool nearly universal. Each step reduced how often anyone needed outside help.
Wallet Labels To Look For
Wallet makers use different words for the same feature. Look for buttons labeled bump fee, speed up, accelerate, or boost. These usually trigger RBF, CPFP, or a smart choice between the two.
If your wallet shows none of these labels, check its settings menu or help pages. Some wallets hide the option behind an advanced toggle. Knowing where it lives saves time during a real emergency.
How Mempool Limits Affect Cheap Transactions
Nodes cap how much memory they devote to waiting transactions. When the pool fills, the lowest-paying transactions get pushed out first. The minimum fee needed to stay in the pool rises during busy periods.
This explains why a very cheap transaction can vanish entirely during a surge. Bumping the fee early, before that happens, keeps your payment in play. Waiting too long can turn a bump into a full rebroadcast.
Batching Payments To Lower Future Fees
Sending several payments in one transaction costs less than sending them separately. Businesses use batching to save on fees and reduce block space use. Each recipient shares the fixed overhead of a single transaction.
Batching also reduces the number of transactions that can get stuck. One well-priced batch beats a dozen small payments that each need their own fee decision.
Advice For Beginners In Three Lines
“Beginner checklist for using RBF vs CPFP to unstick a bitcoin transaction”
Check the fee before you send. Use RBF if your wallet offers it. Use CPFP when it doesn’t, and contact support when you don’t control the keys.
These three habits cover almost every situation a normal user will ever face. Everything else in this guide adds detail, not new rules.
When Software Bugs Interfere
Occasionally a wallet’s bump feature misbehaves because of a software bug or an outdated version. The button may fail silently or calculate a poor fee. Updating the wallet often fixes the problem.
If an update doesn’t help, try the same action in a different trusted wallet that supports importing your keys safely. Only do this with reputable software, and never paste keys into a website.
Terminology You Should Know
Replaceable flag refers to a setting on a transaction indicating whether it can be replaced by a higher-fee version. Child transaction refers to the new transaction created under CPFP that spends an output from the stuck “parent.” Package relay refers to how modern nodes evaluate the parent and child together as one combined fee unit.
Full-RBF refers to the network-wide policy allowing any transaction to be replaced by a higher-fee version. This holds regardless of whether the original explicitly opted in. Knowing these terms makes wallet documentation considerably easier to follow.
RBF vs CPFP On Exchange-Originated Transactions
Neither method is available to you directly on a transaction sent from a centralized exchange. The exchange’s own systems control both the original broadcast and any potential fee bump. Contacting exchange support remains the correct path here regardless of which method you’d otherwise prefer. For a Coinstick-related transfer, the Coinstick contact page is the right channel.
This limitation applies equally to both methods. It’s worth remembering before you spend time trying to construct a workaround for a custodial transaction you don’t actually control.
RBF vs CPFP For Businesses Processing Volume
A business handling regular Bitcoin volume benefits from automating RBF specifically. Its lower cost and broader wallet support make it the better primary strategy over building CPFP logic. Reserving CPFP for genuine edge cases, like an older non-replaceable transaction, keeps operational costs lower.
Working with a wallet provider that supports automated RBF triggers reduces manual intervention considerably. It also cuts average resolution time for any business processing meaningful volume.
Frequently Asked Questions About RBF vs CPFP
Which method should I try first?
RBF, whenever your wallet supports it. It’s cheaper, simpler, and resolves the same underlying problem as CPFP in most cases.
Can I use CPFP if I’m not the original sender?
Yes, provided you control a spendable output from the stuck transaction. This is common for a recipient who hasn’t yet spent received funds.
Does either method guarantee my transaction confirms immediately?
No. Both methods improve your transaction’s priority, but final inclusion still depends on overall network conditions and which pool mines the next block.
Where can I get help with a Coinstick transfer?
Coinstick’s FAQ page covers common questions about its own platform. It doesn’t cover wallet-level fee bumping, which your own wallet handles.
Is CPFP ever cheaper than RBF?
Rarely. CPFP requires paying for an entire second transaction’s block space, which usually makes it the costlier option when both are available.
More Questions About Fixing A Stuck Transaction
What if my wallet doesn’t support either method natively?
Some wallets require manually constructing a CPFP transaction through advanced settings. Otherwise, you may need to switch to software that supports RBF for future transactions.
Can I cancel a transaction instead of bumping it?
Not directly. RBF technically replaces a transaction. That replacement can send funds back to yourself, which functions similarly to a cancellation in most practical cases.
Do hardware wallets support these features?
Increasingly, yes. Most major hardware wallet software now supports RBF, while CPFP support varies more by specific manufacturer and firmware version.
The Bottom Line On RBF vs CPFP
RBF and CPFP solve the same core problem through different mechanisms. Knowing which one actually applies to your situation saves both time and money. RBF wins on cost and simplicity whenever it’s available. CPFP remains the essential fallback when it isn’t.
Checking your wallet’s specific support for each feature before you actually need it is the single most useful preparation covered in this entire guide. When your Bitcoin does confirm, Coinstick’s sell page is there whenever you’re ready to convert it. Do this before an active stuck-transaction situation, not during one.
Continue Reading
Clean structure, clean records, and early review are what keep crypto tax reporting manageable.