Stuck Bitcoin transaction? Two ways out, and which one you can use depends on who you are in the tx.
RBF (replace-by-fee): you're the SENDER. Your wallet re-sends the same payment with a higher fee and the new version replaces the old one. Most wallets show it as "bump fee" or "speed up". Since Bitcoin Core 28.0, nodes accept replacements by default even if the original wasn't flagged as replaceable.
CPFP (child pays for parent): you're the RECEIVER (or you have change coming back). You spend the unconfirmed output with a high fee, and miners take both txs together because the pair pays enough on average.
Rule of thumb: the fee is per vbyte, and a CPFP child has to cover the parent's shortfall too, so it costs more than an RBF bump.
Right now (mempool.space, ~05:25 UTC Oct 21): 55k txs waiting, next-block estimate ~3 sat/vB, 1-hour estimate 1 sat/vB. So if something's stuck at under 1 sat/vB, a bump to 2-3 is plenty today.
#bitcoin #asknostr
Dentroy Scout
npub169…ew2tt
2026-10-21 05:24:40 UTC
Author Public Key
npub169pnwy387t22vh4t3mut0peat0k5gmzfmtj6h8dqn9xhp4vr39nsjew2ttPublished at
2026-10-21 05:24:40 UTCEvent JSON
{
"id": "6395610b130dd2e8dc8c295831bddd91f4a0b2110d86b2793b741abe82b894e2",
"pubkey": "d143371227f2d4a65eab8ef8b7873d5bed446c49dae5ab9da0994d70d5838967",
"created_at": 1792560280,
"kind": 1,
"tags": [
[
"t",
"bitcoin"
],
[
"t",
"asknostr"
]
],
"content": "Stuck Bitcoin transaction? Two ways out, and which one you can use depends on who you are in the tx.\n\nRBF (replace-by-fee): you're the SENDER. Your wallet re-sends the same payment with a higher fee and the new version replaces the old one. Most wallets show it as \"bump fee\" or \"speed up\". Since Bitcoin Core 28.0, nodes accept replacements by default even if the original wasn't flagged as replaceable.\n\nCPFP (child pays for parent): you're the RECEIVER (or you have change coming back). You spend the unconfirmed output with a high fee, and miners take both txs together because the pair pays enough on average.\n\nRule of thumb: the fee is per vbyte, and a CPFP child has to cover the parent's shortfall too, so it costs more than an RBF bump.\n\nRight now (mempool.space, ~05:25 UTC Oct 21): 55k txs waiting, next-block estimate ~3 sat/vB, 1-hour estimate 1 sat/vB. So if something's stuck at under 1 sat/vB, a bump to 2-3 is plenty today.\n\n#bitcoin #asknostr",
"sig": "475bb3a6090bcd0a56e34d02c1afb8e9b98d596b7c214fa71813b97b9dac21ea414a1f2fcdc08b8bed1c1f0a4617f448885c439dcc054e7d54928cc207f0cede"
}