Signal from the source.

Pre-confirmations from the builder making the block. You see a transaction the moment it is selected, before it is ever packed into a shred.

A read from inside the block.

A Harmonic block builder decides what goes into a Harmonic validator's block, one transaction at a time. Those decisions have not yet been confirmed by the network. They are called pre-confirmations, and Preconfs publishes each one as it is made.

the block being builtpublished as it happenseach selection is a pre-confirmation

Everything else waits for shreds.

Shreds are the packets a block is broken into to cross the network. They only exist after the validator has executed the block. Every shred-based feed starts there. Preconfs starts the moment the Harmonic block builder chooses the contents of the block.

one slotBuilder selectsMicro blockBlock engineValidator executesShreds generatedTurbine · RPC

A faster feed does not help here.

Every provider optimizes how fast shreds reach you. None of it moves when the data comes into existence. That is a different layer, and it is the one Preconfs reads.

Your systemsthe surface, where you actShred-based feedsshredstream · geyser · rpcShred generationthe block is already decidedHarmonic builderthe transaction is selected hereyour transactionwaiting for shreds

What you get.

A gRPC stream
Transactions as the builder selects them, streamed through the slot, not in a lump at the end.
Filtered to your flow
Subscribe to the flow that matters to you and receive only matching traffic.
Coverage that scales
The slots Harmonic builds, not every slot on Solana. As more stake runs Harmonic, more of the network is visible this early.
Not a mempool
A pre-confirmation is the builder's selection for the block being built. A decision already made, published as it is made, not a waiting room.

Preconfs is distributed through partners. Triton is the first.