Use cases

ShredStream delivers transactions before they appear in a confirmed block. Combined with Jito bundles, you can detect and react to on-chain events within the same slot:

for await (const shred of client.subscribe({})) {  if (!shred.isLastInSlot) continue;   // Full slot assembled — inspect transactions before RPC propagation  const entries = assembleEntries(shred);  for (const entry of entries) {    for (const tx of entry.transactions) {      if (isMevOpportunity(tx)) {        // Submit bundle to Jito block engine        await submitBundle(buildBackrun(tx));      }    }  }}

• Detect large swaps, liquidations, or oracle updates before block confirmation.
• Place limit orders or trigger hedges on CEXes based on on-chain events.
• React to price moves before they propagate to public RPC endpoints.

Build block explorers or indexers that show transactions as they happen — not after confirmation. Users see trades appear in your UI 200–400 ms faster than competitors using public RPC.

• Detect missed blocks before they are rooted — alert before the epoch report.
• Track your own validator's shred production rate in real-time.
• Identify network partitions by watching for shred gaps.

• High-level transaction parsing — use getTransaction with jsonParsed encoding for that.
• Fetching account state — shreds contain transactions, not account data snapshots.
• Applications that don't need sub-confirmation latency — Yellowstone gRPC is simpler and sufficient.