Skip to the article
Token Trail

News from across crypto

How to Handle a Bitcoin Transaction That Drops from the Mempool

When a Bitcoin transaction drops from the mempool, its inputs remain unspent; rebroadcast it, replace it with RBF, or wait for confirmation on another node.

By The Token Trail Desk3 min read

How to Handle a Bitcoin Transaction That Drops from the Mempool

A Bitcoin transaction that drops out of a mempool is no longer being held by that node, but its inputs remain unspent. The signed transaction can still be rebroadcast or replaced, and a copy held by another node may still confirm.

Why a transaction disappears and what to do

The mempool is a node’s temporary cache of unconfirmed transactions. Each node manages its own cache, so a transaction missing from your node or an explorer may still be in miners’ mempools. That difference matters: local disappearance does not prove the transaction has vanished across the network.

The most common cause is a full mempool. Bitcoin Core’s default memory limit is 300 MB. When the pool reaches its limit, a node evicts transactions with the lowest fee rates and raises its minimum fee for accepting new transactions. A low-fee transaction disappearing while busier periods continue is a clue. Rebroadcast it, or use your wallet’s fee-bump option to replace it with a higher-fee transaction.

For a TeleSwap deposit, the distinction matters because the bridge needs the Bitcoin transaction to confirm before it can credit the deposit. The teleswap liquidity context may help explain the bridge route, but a transaction still sitting unconfirmed has not completed that step.

Age can also explain a disappearance. Bitcoin Core’s default mempool expiry is 336 hours, or 14 days; nodes can use different settings. If a transaction has stayed unconfirmed for about that long, check whether your wallet still has it and rebroadcast it if the inputs remain available.

Before acting, identify the transaction and check its inputs and wallet status:

  • The transaction ID shows whether a node or explorer still sees it.
  • The wallet shows whether it can rebroadcast or raise the fee.
  • The inputs show whether another transaction has already spent the coins.

If the inputs remain unspent, rebroadcasting the same signed transaction may get it back into nodes’ mempools. To replace it, use RBF—Replace-by-Fee—and pay a higher fee. BIP 125 describes opt-in replacement rules; Bitcoin Core 28.0 enabled full-RBF by default, allowing replacement without the original transaction signalling opt-in. Node policies can differ, so a replacement may not spread everywhere at once.

Until a TeleSwap deposit confirms, do not treat it as credited. Check the transaction status and inputs first; if the deposit is still unconfirmed, rebroadcast or replace it through the wallet or service flow that created it.

Related

Can a dropped Bitcoin transaction still confirm later?

Yes. A copy may remain in another node’s or miner’s mempool after your node drops it. If that copy is included in a block, the transaction confirms; otherwise, rebroadcasting may restore it to more mempools.

What is the mempool minimum fee and why does it change?

The mempool minimum fee is the lowest fee rate a node currently accepts into its pool. It rises when a full pool evicts its lowest-feerate transactions, then can fall as space becomes available. If none of these checks explains the status, compare the transaction ID across sources and ask the wallet or service that created it to confirm whether it remains valid and can be rebroadcast.