Base stream
Fastest shred-level transaction bytes—the foundation Preconfs extend.
// Preconfs · Binary add-on
Capture already-included transaction data inside the validator before raw shreds are emitted. Preconfs is a Binary add-on that merges pre-shred delivery with your existing Binary stream—same payload, earlier arrival for connected leaders.
Preconfs require an active Shreder Binary subscription. They extend Binary—they do not replace it.
Preconfs are streamed only from connected current leaders. Coverage grows as more stake is connected. Read the launch article →
// What it is
On Solana, there is a gap between the moment transactions are executed and marked for inclusion and the moment the corresponding shreds are sent to the network. Raw shreds, Decoded Shreds, and Binary all depend on that emission step—so they cannot arrive earlier than the validator emits shreds, no matter how direct the network path is.
Preconfs shift the source earlier. Shreder captures transaction data inside connected leaders before shreds are emitted, then merges it into your Binary stream. Whichever source delivers a transaction first—earliest shreds or preconfs—gets sent straight to you.
Preconfs are a Binary add-on, not a standalone product. Start with Binary, then add Preconfs for qualified low-latency workloads.
Fastest shred-level transaction bytes—the foundation Preconfs extend.
Pre-shred data from connected leaders, merged into the same stream.
Every transaction, no gaps—fastest source wins per signature.
// Why Preconfs
For Binary users who have already optimized everything downstream and still need more.
Capture data inside the validator before shredding and network transmission—cutting 5–50 ms off leader shred delivery for connected validators.
No separate integration path. Preconfs merge into your existing Binary stream; same filters, same deserialization, same client code.
Transactions are already included in the block before they are streamed. Preconfs do not expose pre-inclusion data or create block-influence opportunities.
Preconfs are local to your region and streamed only from current connected leaders—targeted acceleration where it matters.
// Performance
Shreder measured Preconfs against leader shreds from the same validators—not third-party providers.
Preconfs vs leader shreds
Measured across a number of validators; comparison is Preconfs vs shreds from the same leaders.
| Percentile | Preconfs lead | Leader shreds |
|---|---|---|
| P10 | 1–3 ms faster | Baseline |
| P50 | 5–10 ms faster | Baseline |
| P90 | 20–50 ms faster | Baseline |
// How it works
Preconfs ship as a continuous stream on top of Binary: a mix of the fastest shreds and pre-shred data. Your client sees one uninterrupted feed—some transactions arrive from earliest shreds, some from preconfs.
Preconfs are a Binary add-on that streams Solana transaction data captured inside the validator before the corresponding raw shreds are emitted. The payload matches Binary; delivery is faster for transactions from connected leaders.
Yes. Preconfs are provided as a continuous stream add-on on top of Shreder Binary. You subscribe to Binary first, then enable Preconfs for qualified use cases.
In Shreder testing against leader shreds from the same validators, expected leads are P10 1–3 ms, P50 5–10 ms, and P90 20–50 ms.
No. Preconfs deliver the same transaction data as Binary. Some transactions arrive from the earliest shreds, some from preconfs—whichever source is first is sent to you.
No. Transactions streamed via Preconfs are already included in the block by the time they are sent out. Preconfs do not expose transactions before inclusion decisions are made.
Only transactions from current leaders connected to Preconfs. Coverage grows as more stake and leaders are connected.
Preconfs launch in Frankfurt first. Streams are local to the region.
Preconfs are available to qualified Shreder Binary customers. Contact the team to discuss your use case.
Preconfs are a Binary add-on for qualified customers who need pre-shred data—typically 5–50 ms ahead of leader shreds.