Network ProtocolVerified Reference • August 2026
Mempool Telemetry & 0-Confirmation Queuing
The memory pool (mempool) is the temporary staging buffer on full blockchain nodes where valid transactions await miner/validator selection and block inclusion.
Core Architectural Highlights:
Nodes enforce individual max transaction pool sizes (typically 4,096 to 10,240 pending txs in Geth).
Transactions below the dynamic minimum gas price floor are evicted without warning.
0-confirmation transactions can be superseded using Replace-By-Fee (RBF) with matching account nonces.
1. Mempool Propagation Lifecycle
When an end-user signs an ECDSA transfer payload and broadcasts it via JSON-RPC eth_sendRawTransaction, the target node validates signature mathematics, nonce sequentiality, and account balance before propagating the raw bytes to peer nodes over devp2p wire protocols.
// Geth txpool validation pseudocode
func (pool *TxPool) add(tx *types.Transaction) error {
if tx.GasPrice().Cmp(pool.gasPrice) < 0 {
return ErrUnderpriced
}
if pool.all.Count() >= pool.config.GlobalSlots {
pool.evictLowestPriced()
}
return pool.broadcast(tx)
}2. Eviction & Timeout Dynamics
Unmined transactions do not remain in memory indefinitely. If network gas surges, block builders prioritize transactions paying higher priority fees (EIP-1559 tips). Stale transactions lingering past 72 hours are dropped from node memory pools (txpool discard).