It's not about the receiving address, your client either supports setting the RBF flag or not. With the RBF flag set you reserve the option to speed up the tx as a SENDER. Have you done that before with the client you're using?

In contrast, a receiver can speed up a transaction by crafting a CPFP tx, spending the unconfirmed tx with a higher fee rate and thereby giving the miner an incentiv to include the initial, low fee parent tx.

👉 If you have a pending tx right now, use the receiving address to spend the unconfirmed tx to a new address you own and you're good.

Mempool accelerator offers this service for 50k sats, if you're lucky, but you can easily create a cpfp tx in sparrow. It recognizes what you want to do.

Reply to this note

Please Login to reply.

Discussion

So it was a very small transaction, sending from a BlueWallet on-chain address to a Phoenix on-chain address for splice-in.

Completely forgot to include the screenshot in my original note, but got the error pictured below. When I tried to cancel the transaction instead speeding it up via RBF, that worked for whatever reason.

So I’m just out a few hundred sats, but ended up getting the funds where they needed to go.

Thanks for the explanation on CPFP, I guess I’ve never used that before - just RBF.