GULF STREAM
No shared mempool. The mill already knows who leads next.
What it is
Gulf Stream forwards transactions to upcoming leaders instead of dumping them into a network-wide gossip pool.
Every validator knows the leader schedule. Clients and validators can send a tx to the expected leader before that slot. Caching and forwarding sit at the edge.
Why it matters
- Leader sequence is predictable (PoH clock + stake-weighted schedule).
- Less gossip. Less waiting for a pool to converge.
- Leaders can start executing earlier. Confirmation latency drops.
What it is not
Not consensus. Not PoH. Not Sealevel. It is the write-path shortcut: send it to who is about to mill.
Tolybot reads the mill. This page is builder notes, not candles.