Every node maintains its own view
A mempool is a node's local collection of valid unconfirmed transactions that may be candidates for future blocks. It is not part of the blockchain.
Nodes receive transactions at different times and can use different policy settings, so honest nodes may have different mempools.
Policy controls admission and relay
Before accepting a transaction, a node checks consensus validity and local relay policy. Policy helps limit resource abuse and controls what the node stores and forwards.
When memory limits are reached, a node can evict lower-fee transactions. Eviction does not necessarily mean the transaction is invalid.
Mining removes confirmed transactions
Miners build candidate blocks from transactions available to them, commonly prioritising packages with attractive fee rates that satisfy all rules.
When a valid block arrives, included transactions leave the mempool and conflicts are removed. A reorganisation can make transactions unconfirmed again.
Mempool and fee competition
Transactions compete for limited block space
Watch transactions enter a node's local mempool and compete by effective fee rate, dependencies and miner policy.
Validate locally
Each node maintains its own mempool. A transaction may be accepted by one node and absent from another.
Key vocabulary
Terms worth knowing
- Relay policy
- Local non-consensus rules a node uses when deciding what unconfirmed data to store and forward.
- Eviction
- Removal of lower-priority transactions when a node's mempool reaches configured limits.
- Ancestor
- An unconfirmed transaction whose output is spent by another unconfirmed transaction.
Worked example
Visible to one explorer, absent from another
A transaction reaches some peers but not others because nodes receive it at different times and apply local policy and resource limits.
- 1Confirm the transaction was actually broadcast
- 2Compare more than one independent source
- 3Check whether inputs conflict or the fee is below local policy
- 4Avoid rebroadcasting a different spend without understanding replacement
There is no authoritative global mempool. Different observations can all be honest local views.
Common misconceptions
What learners often get wrong
Misconception
The mempool is a waiting room stored in the blockchain.
More accurate
It is temporary local node memory; only confirmed transactions become part of a block.
Misconception
A dropped transaction is permanently failed.
More accurate
It may still exist on other nodes or be rebroadcast later if its inputs remain unspent.
Try it yourself
Explain a transaction's status from three viewpoints.
- Describe the sender wallet's view
- Describe a node that accepted it
- Describe a node that never received it
- Explain what changes after confirmation
Use fictional values and public information only. Never enter seed words, private keys or other wallet secrets into a learning exercise.
Key takeaways
- There is no single global Bitcoin mempool.
- Consensus rules and relay policy serve different purposes.
- Mempool contents vary between nodes.
- Confirmation moves a transaction from temporary memory into the blockchain.
Lesson recap
Check what you learned
Reveal each model answer, then honestly mark whether you understood it or need another review.
1 of 3
Recall
Can two honest nodes have different mempools?
References
