The short version: an unconfirmed transaction isn't lost, and you have two ways to rescue it — raise the fee on the one you sent, or, if you're the receiver, pay your way out from the other side. Both are built in. Neither requires anyone's help.

When Tuga wants to come in and the back door is shut, she sits down in front of it and waits. No scratching, no noise — just sitting, with the specific stillness of a creature certain that reality will eventually correct itself.

And it does, but never because of anything she did. Either someone inside notices and opens the door, or she waits. Those are the two mechanisms. She has no third option and, to her credit, she doesn't invent one.

A stuck Bitcoin transaction has exactly the same two exits, and unlike Tuga you get to choose which.

1. First: it isn't lost

The single most useful fact, and the one that stops the panic: an unconfirmed transaction has not left your control and the coins have not gone anywhere.

What's happened is that you broadcast a transaction with a fee that, at this moment, isn't competitive. Miners pick transactions by what they pay per unit of space. Yours is sitting in the queue — the mempool — waiting for either a quiet period or a better offer.

Three things follow:

Nobody can spend those coins but you. The transaction is signed and sitting in public, but until it's mined, nothing has moved.

It may confirm on its own. Fee pressure is cyclical. Weekends and quiet nights clear backlogs that looked hopeless on a busy afternoon.

It may also be dropped. Nodes eventually evict old transactions from their mempools — typically after a couple of weeks. If that happens, the coins are simply still yours, as if you never sent it. That's a non-event, not a loss.

So the first move is genuinely to do nothing for a few hours. Many "stuck" transactions resolve while the owner is busy reading panicked forum posts about them.

2. Exit one: RBF — ask again, louder

Replace-by-Fee lets you rebroadcast the same transaction with a higher fee. Same recipient, same amount, new fee. Miners take the better-paying version and the original is discarded.

In most modern wallets this is a right-click: Increase fee, or Bump fee. You pick a new rate, confirm, done.

Two things to know:

It only works if your wallet flagged it. Most wallets now enable RBF by default, but not all, and some exchanges disable it. If the option is greyed out, the transaction wasn't signalled as replaceable and this route is closed to you.

The extra fee comes from your coins. You're not paying a penalty to anyone — you're paying miners more for the same space. If the transaction spent nearly your entire balance, there may not be room to raise it.

RBF is the clean option and it's the one to reach for whenever you're the sender.

3. Exit two: CPFP — someone inside opens the door

If you can't replace the transaction — you didn't signal RBF, or you're the recipient and have no control over it at all — there's a second route with a name that sounds like jargon and is actually a plain description: Child Pays For Parent.

Here's the mechanism. A miner evaluates transactions in packages. If an unconfirmed transaction has a child spending its output, the miner can consider them together: if the child pays a large enough fee to lift the combined rate of both, mining both becomes worthwhile.

So you spend the incoming coins — to yourself, to another wallet you control, anywhere — with a deliberately high fee. That child drags the parent through with it.

In practice: in a wallet with coin control, select the unconfirmed incoming output, send it to an address of your own, and set an aggressive fee. Sparrow, Electrum and most competent desktop wallets allow this directly.

This is the exit Tuga doesn't have. The person on the other side of the door can open it.

4. How to avoid being here

Check the mempool before you send, not after. Public mempool viewers show current fee rates by confirmation target. Thirty seconds of looking beats a week of waiting.

Treat the wallet's suggestion as a suggestion. Some wallets quote a rate that was accurate when the fee estimator last ran. If you're sending something that matters, check independently.

Don't send during the rush if you don't have to. Fees spike and subside. If your transfer can wait until the weekend, it costs less and confirms faster.

Keep RBF enabled. It's free optionality. There's no downside to signalling it.

And practise it once, on purpose, with nothing at stake. Send something with a deliberately absurd low fee on signet, watch it sit there, and rescue it both ways. Ten minutes now buys you complete calm later. I wrote a whole piece about setting up that practice garden; this is the exercise that pays for itself fastest.

5. The uncomfortable half

Most "stuck transaction" emergencies are self-inflicted by impatience. The honest advice for the majority of cases is wait, and almost nobody wants to hear it. People bump fees after twenty minutes during a period when the next block would have taken them anyway, and pay several times what they needed to for an outcome they'd have had for free.

Fee bumping has a privacy cost. Replacing a transaction publishes both versions. Doing a CPFP links the incoming output to the wallet you swept it into, in public, immediately and permanently. If you've been careful about not connecting your addresses, a panicked rescue can undo that work in one click.

And this whole category of problem exists because of a real trade-off. Block space is limited on purpose — that's what makes running a node cheap enough for ordinary people, which is what makes the network's rules enforceable by its users rather than by whoever can afford the hardware. The fee market is the price of that property. People who promise a chain with no congestion and no fees are usually not describing a cleverer design; they're describing a different set of compromises, with the costs moved somewhere less visible.

One thing that is never the answer: nobody can "unstick" your transaction for a fee. Any service, DM, or helpful stranger offering to accelerate it for payment is either selling you something you can do yourself for free, or stealing from you. There is no customer support desk for the mempool, and the absence of one is the point.

She sits at the door and waits, and it works, eventually. You have the better version: you can raise the offer, or you can open it from the inside. 🐾⚡