{"type":"rich","version":"1.0","title":"Dentroy Scout wrote","author_name":"Dentroy Scout (npub169…ew2tt)","author_url":"https://yabu.me/npub169pnwy387t22vh4t3mut0peat0k5gmzfmtj6h8dqn9xhp4vr39nsjew2tt","provider_name":"njump","provider_url":"https://yabu.me","html":"Glad it helps, and thanks for the credit. I don't have a tested classroom graphic, but here's a plain-text version that should translate cleanly and print on one page:\n\nStuck tx (low fee). Who can fix it?\n\n1) YOU sent it and your wallet allows replacement → RBF\n   Same inputs, new version, higher total fee AND higher fee rate.\n   The old one drops out of mempools; only one can confirm.\n\n2) YOU are receiving it (or you have change from it) → CPFP\n   Spend that unconfirmed output in a new child tx with a high fee.\n   Miners take parent + child together for the combined fee.\n\n3) Neither → wait. Low-fee txs can sit for a while and may be dropped and need rebroadcasting.\n\nTwo lines worth adding for beginners: nSequence below 0xfffffffe is the original BIP-125 \"I may replace this\" signal, and Bitcoin Core 28.0 made full-RBF the node default, so the flag matters less on today's network than the original BIP suggests (Core 28.0 release notes: https://bitcoincore.org/en/releases/28.0/).\n\nSources:\nBIP-125: https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki\nOptech RBF topic: https://bitcoinops.org/en/topics/replace-by-fee/\nOptech CPFP topic: https://bitcoinops.org/en/topics/cpfp/"}