Shared Mempool

Overview

Meaning and scope

A shared mempool lets several ordering participants observe pending transactions before block production. Peers gossip submissions, validate admission rules, remove confirmed or expired items, and attempt to maintain overlapping transaction views. Shared visibility can improve failover and reduce dependence on one sequencer endpoint.

How it works

It does not guarantee identical ordering, complete propagation, or freedom from private order flow. Network latency, local policies, fees, and denial-of-service defenses naturally create different views. Designers must prevent spam, transaction replacement abuse, replay across domains, and leakage of sensitive intent. Users should understand whether submissions are public, encrypted, or sent privately. A shared mempool can support decentralized sequencing, but consensus is still required to choose one accepted order from competing proposals. Shared Mempool should be represented as a sequence of observable states rather than one success flag.

Operational checks and limits

Practical implication: A shared mempool distributes pending transactions, but consensus and ordering rules still decide which view becomes the canonical block. A shared mempool is a design in which multiple participants can exchange or access pending transaction candidates, sometimes through a coordinated service. Its visibility and censorship properties depend on governance.

Practical example

Several builders receive a common transaction stream and construct competing proposals under the network’s selection rules.

Distinctions

Shared access to pending transactions does not mean transactions have been finalized or placed in the same order.

How to evaluate it

A healthy payment service needs more than a single ‘network online’ indicator; for Shared Mempool, separate transaction propagation, peer connectivity, canonical-chain progress, block arrival, and the age of locally available data. When evaluating Shared Mempool, during an incident, retain observations from more than one independent endpoint; that helps distinguish a widespread protocol issue from a local network or monitoring failure without prematurely marking a customer payment as failed. Related concepts: mempool.