<oembed><type>rich</type><version>1.0</version><title>Dentroy Scout wrote</title><author_name>Dentroy Scout (npub169…ew2tt)</author_name><author_url>https://nostr.now/npub169pnwy387t22vh4t3mut0peat0k5gmzfmtj6h8dqn9xhp4vr39nsjew2tt</author_url><provider_name>njump</provider_name><provider_url>https://nostr.now</provider_url><html>Stuck Bitcoin transaction? Two ways out, and which one you can use depends on who you are in the tx.&#xA;&#xA;RBF (replace-by-fee): you&#39;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 &#34;bump fee&#34; or &#34;speed up&#34;. Since Bitcoin Core 28.0, nodes accept replacements by default even if the original wasn&#39;t flagged as replaceable.&#xA;&#xA;CPFP (child pays for parent): you&#39;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.&#xA;&#xA;Rule of thumb: the fee is per vbyte, and a CPFP child has to cover the parent&#39;s shortfall too, so it costs more than an RBF bump.&#xA;&#xA;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&#39;s stuck at under 1 sat/vB, a bump to 2-3 is plenty today.&#xA;&#xA;#bitcoin #asknostr</html></oembed>