Mempool Eviction
Pronunciation: MEM-pool ih-VIHK-shun
Definition
Mempool eviction removes previously accepted unconfirmed transactions when capacity, fee, conflict, expiry, dependency, or chain-state conditions no longer permit retention. Eviction removes an unconfirmed transaction from one node's pending pool under local capacity, fee, conflict, expiry, or policy rules. It does not erase a signed transaction from the universe: another node may retain it and a miner or validator may still include it later.
Overview
Meaning and boundaries
Nodes evict transactions to control memory use and maintain a useful pool of likely block candidates. Eviction removes an unconfirmed transaction from one node’s pending pool under local capacity, fee, conflict, expiry, or policy rules. It does not erase a signed transaction from the universe: another node may retain it and a miner or validator may still include it later.
How it works in practice
Low-fee transactions may be removed when capacity fills, while confirmed conflicts, invalidated dependencies, expiration rules, or reorganizations can trigger other removals. Eviction is local and does not cancel the transaction everywhere. Another node or miner may still retain and confirm it. A wallet that creates a replacement must follow network rules and avoid assuming the original can never reappear. Applications should track transaction status across several states, including seen, dropped, replaced, conflicted, and confirmed. Re-broadcast or fee-bumping logic must verify inputs and nonces first. Operators should expose eviction metrics and current minimum fee so users understand why an accepted transaction disappeared. Mempool Eviction should be represented as a sequence of observable states rather than one success flag. Systems need idempotent processing keyed to stable transaction and business identifiers. Repeated callbacks, node disagreements, reorganization, and delayed receipts must not create duplicate credits or irreversible state transitions before the required network evidence is available.
Checks and failure points
Keep pending invoices recoverable when a transaction disappears from one mempool view. Investigate replacements and conflicts, rescan the chain, and avoid concluding that funds are safely available for a second payment.
How it differs from related terms
Eviction is removal from a node’s pending pool, whereas a confirmed transaction reversal involves a blockchain reorganization or chain-specific finality event. Related entries: Mempool.
Example
A low-fee transaction vanishes from one node after congestion. The customer rebroadcasts it; the merchant checks whether the original is still active elsewhere before updating its invoice.
Comparison
Eviction is removal from a node's pending pool, whereas a confirmed transaction reversal involves a blockchain reorganization or chain-specific finality event.
Key Takeaway
Local mempool disappearance does not guarantee cancellation.
Sources
- Bitcoin.org Documentation: P2P Network — Bitcoin.org (2026-07-30)
- Bitcoin Developer Guide: Transactions — Bitcoin.org (2026-07-30)