Solana doesn't have a mempool

Why there is no mempool

Ethereum nodes gossip pending transactions into a shared public pool, where they wait to be picked up by a block producer. That pool is a queue, and it is observable by anyone.

Solana has no such queue. Clients forward transactions directly to the leader for the current slot, and the leader for the next few slots, using a protocol called Gulf Stream. There is no shared waiting room to watch, because transactions go straight to whoever is about to build the block.

So the classic mempool play — see a pending transaction, insert yourself in front of it — has no equivalent surface on Solana. Anyone selling you 'Solana mempool access' is selling something else under a familiar name.

What replaces it

The earliest genuinely observable moment is the shred broadcast. Once the leader packs transactions into entries and starts shredding them onto the wire, the contents are visible to anyone receiving those shreds — during the slot, before the block is complete, and long before any RPC reports a confirmation.

This is not pending-transaction visibility. By the time you see a shred, the leader has already committed to including that transaction; you cannot get in front of it in that block. What you get is the earliest possible knowledge of what just happened — which is what nearly every real Solana strategy is competing on.

What this means for MEV

Solana MEV is overwhelmingly a reaction game rather than an insertion game. You are racing to be the first to respond to something that has landed: a launch, a large swap, a liquidation trigger, a pool imbalance. Whoever observes it first gets to act first.

That reframes the whole problem. There is no pending queue to snipe, so the advantage goes to whoever taps the pipeline earliest — and the earliest tap available without operating a staked validator is a shred feed.

How early is early?

Our proxies deliver shreds roughly a millisecond after they hit the wire. A commodity RPC websocket reports the same transaction around 200 milliseconds later. On a 400 millisecond slot that gap is most of a slot — the difference between reacting inside the event and reading about it afterwards.