Skip to main content
Blockfront

Crypto markets, protocols and policy

Ethereum Swaps: What Happens Before Inclusion

How does the Ethereum public mempool work? Each node keeps and shares its own pool of valid pending transactions; builders choose transactions for blocks.

Blockfront Editorial

3 min read

Ethereum Swaps: What Happens Before Inclusion

Ethereum’s public mempool is a set of separate node-level pools that share valid pending transactions, rather than one network-wide queue. A transaction waits in a node’s pool until a block builder selects it, or it is replaced or evicted.

Nodes validate transactions, then share them with peers

A wallet sends a signed transaction to an Ethereum node through an RPC connection, the interface apps use to submit requests. The node checks its signature, nonce, balance and fee settings before accepting it into its transaction pool, its local store of pending transactions.

The nonce is the account’s sequential transaction number. Under EIP-1559, a transaction’s fee includes the block’s base fee and a priority fee, or tip. Ethereum.org’s transaction documentation explains how these fees work.

After accepting a transaction, the node gossips it to peers using Ethereum’s devp2p peer-to-peer network and its eth protocol. Those peers can pass it on, so within seconds many nodes—and bots monitoring the public mempool—may see it. Each node maintains its own pool, so what one node has received or retained may differ from another’s.

Geth, a widely used Ethereum client, separates executable transactions into a “pending” pool and transactions waiting for an earlier nonce into a “queued” pool. Its transaction pool documentation describes both. When a node’s pool is full, it can evict lower-paying transactions to make room.

A nonce gap can hold up every later transaction from an account

Take a MetaMask swap with nonce 12. If the account’s next expected nonce is 12 and the transaction passes the node’s checks, it can enter the pending pool and spread through the network.

Now say nonce 12 is missing, but the account has already sent transactions with nonces 13 and 14. Those later transactions sit in the queued pool because the account’s transactions must execute in nonce order. Neither can be picked for a block until nonce 12 arrives and is included, or the gap is otherwise resolved. One stuck transaction can therefore hold back every later transaction from that account.

A block builder selects eligible transactions for a block. Under EIP-1559, the priority fee is the tip paid to the block’s proposer, so builders generally favor transactions offering higher tips, while also considering how transactions fit together. A research and development organization focused on how Ethereum handles maximal extractable value, Flashbots is one example of infrastructure involved in this part of the ecosystem.

When your swap is included in a block, it leaves the pending pool and executes; until then, it can wait for a competitive tip, a missing nonce, or space in a node’s pool. The same path applies to ordinary transfers and other contract calls: submit, validate, gossip, then wait for block inclusion.