How Gulf Stream forwards Solana transactions without a mempool
Solana does not have a mempool - at least not in the default protocol. That statement surprises many people who come from Ethereum or Bitcoin, where every transaction sits in a public waiting room before a miner picks it up. On Solana, the design is fundamentally different. The mechanism that makes this possible is called Gulf Stream.
Gulf Stream is the transaction forwarding protocol that bypasses the need for a shared mempool entirely. Instead of broadcasting every transaction to every validator, Gulf Stream sends each transaction directly to the validator who will be the next leader - the one producing the next block. That leader knows which slot they are assigned to produce. Gulf Stream forwards transactions to them ahead of that slot, often several slots in advance. This cuts the time a transaction spends in limbo to near zero.
The benefit is straightforward. Without a mempool, there is no global backlog where everyone can see pending transactions. That eliminates a class of attacks, like front-running bots that scan the mempool and jump ahead of you. It also reduces memory load on validators, because they do not need to store and rebroadcast every pending transaction to every peer.
But there is a catch. The default Solana protocol has no mempool. Jito-Solana, a popular third-party validator client, introduces one. Jito-Solana runs an out-of-protocol block space auction. Validators using Jito can accept bids from users who want their transactions placed first. This creates an effective mempool for those validators. It is not part of the core Solana code. It exists alongside it. So when someone says "Solana has no mempool," they are correct about the base protocol. But in practice, a significant portion of validators run Jito-Solana, which means the mempool is present in the network, just not in the protocol.
Gulf Stream also interacts with how transactions travel across the network. That is where Turbine comes in.
Turbine is the block propagation protocol. When a leader produces a block, Turbine breaks that block into small data packets. It sends those packets to a small set of validators, who then forward them to others in a tree-like structure. Each validator only receives the packets they need. The goal is efficiency: a validator should not have to download the entire block from one source, because that would create a bottleneck. Turbine spreads the load. It is why Solana can handle high throughput without every node drowning in data.
Turbine handles blocks. For transaction ingress - the process of getting transactions from users to leaders - Solana replaced UDP with QUIC. Previously, validators accepted incoming transactions over UDP. That was fast, but unreliable. UDP does not handle congestion control. A flood of transactions could overwhelm a validator. QUIC adds reliability. It is built on top of UDP but includes stream multiplexing, congestion control, and error correction. When a leader is under heavy load, QUIC lets the validator tell clients to slow down. That prevents dropped packets and wasted compute.
The shift to QUIC was not trivial. It required changes to how validators handle incoming connections. But it gave the network a more predictable ingress path. Combined with Gulf Stream, it means transactions can arrive early, reliably, and without sitting in a global queue.
One common misconception is that because Solana has no mempool, transactions never wait. That is not quite true. They do wait, but not in a shared pool. They wait in the leader's local queue, which is private to that leader. You cannot see someone else's pending transaction. You cannot front-run it. But you also cannot guarantee your transaction will land in the next slot if the leader is overloaded. Gulf Stream forwards transactions early, but it does not guarantee inclusion. The leader still decides which transactions to include, and priority fees influence that decision.
The separation is clean. Gulf Stream handles forwarding. Jito-Solana adds a market layer on top for those who want to pay for priority. Turbine handles propagation of blocks after they are produced. QUIC handles the reliability of the ingress path. Each piece solves a specific problem. Together, they let Solana process transactions without the mempool model that other blockchains rely on.
As of August 2026, Solana continues to operate with this architecture. The protocol itself has no mempool. The Jito-Solana client provides one as an optional add-on. For most users, transactions travel from wallet to leader via Gulf Stream, get included in a block, and propagate through Turbine - all without ever entering a public waiting room.
Not financial advice. orymsolana.xyz publishes market data and general information about digital assets. Crypto assets are volatile and you can lose everything you put in. Nothing here is a recommendation to buy, sell or hold, and we make no price predictions.
Prices are sourced from third parties and may be delayed or wrong. Verify anything you intend to act on against a primary source.