ShredPrism

Serialized Solana entries over the Jito ShredStream interface, delivered over gRPC with TLS from dedicated regions.

ShredPrism delivers serialized Solana entries over gRPC, from the block the leader is producing. It is the earliest view of Solana data that constant-k offers.

Compatibility and identity

ShredPrism serves the Jito ShredStream interface, shredstream.ShredstreamProxy/SubscribeEntries. A client written for Jito ShredStream connects unchanged, with the endpoint and the x-token metadata changed.

The interface is Jito's; the payload inside it is standard Solana entries. The protocol file is shredstream.proto in jito-labs/mev-protos.

ShredPrism combines shreds sourced from the fastest known shred providers with shreds from constant-k's own validator. Combining sources means a fragment missed by one can still arrive.

Endpoints

RegionHost and port
New Yorkprism-newyork.constant-k.com:55577
Frankfurtprism-frankfurt.constant-k.com:55577

Connections must use TLS, with the API key in the x-token header. Your connection details appear on the My Account page once Nexus is active.

Delivery

PropertyBehaviour
StageReassembly done; deserialization and everything after it belongs to the reader. See Data Stages.
PayloadSerialized entries, with the slot they belong to
TransportgRPC over HTTP/2 with TLS, so data arrives in order and lost packets are retransmitted. A dropped UDP shred stream packet is gone without notice.
ContentEvery transaction and every slot, unfiltered

Each response carries a slot number and a byte string of serialized proof-of-history entries, each entry with its own transactions. Entries covers the layout, the decoders and the delivery properties of the feed, and the Quickstart has the service, method and metadata.

Access and limits

ShredPrism is included on Nexus. Limits apply per region.

LimitNexus
Concurrent streamsOne stream per key, in each region
Bandwidth limitNone
Per-request meteringNone
Stream typeThe full Solana feed over gRPC
Shred visibilityPre-block, sub-slot

A second stream on the same key in the same region is refused, and the stream you already hold keeps running. The status and its message are in the Quickstart troubleshooting table.

ShredPrism carries serialized entries, deserialized and filtered by your own code. Turbo Kaldera carries decoded pre-execution transactions, already filtered, and Kaldera carries execution results. The service comparison sets the four streaming services side by side, and Data Stages places each one on the pipeline.

On this page