Decoded Shreds

Pre-execution transaction intent reconstructed from shreds, streamed over gRPC as SubscribeDeshred. Desk and above.

This is the rpc edge product name for the deshred transaction stream: transaction intent reconstructed from Solana shreds and pushed over gRPC before the validator exposes normal processed metadata. Older copy called the same stream preprocessed gRPC.

Who gets it

Desk and Custom. Trader includes Yellowstone gRPC (processed / confirmed / finalized), not this stream. The dashboard page is Decoded Shreds.

Endpoint and auth

Same host as Yellowstone gRPC. Different RPC.

grpc.rpcedge.com:443
frankfurt.grpc.rpcedge.com:443

Pass your UUID API key in gRPC metadata:

x-api-key: YOUR_UUID_KEY
authorization: Bearer YOUR_UUID_KEY

Open SubscribeDeshred on that connection. Do not put deshred filters on the ordinary Subscribe request. Processed accounts, logs, and status still come from Yellowstone Subscribe on the same host.

How to open the stream: Subscribe.

Why use it

Use this stream when the first reaction can run on transaction intent and you will reconcile later. For account changes, logs, balances, and executed metadata, use Yellowstone gRPC at processed, confirmed, or finalized.

Included data

• signature;
• transaction bytes / message;
• slot and shred-span context where available;
• vote flag;
• loaded writable and readonly addresses from address lookup tables, when the gateway resolves them;
• transaction-level filter fields supported by SubscribeDeshred.

Not included

• account writes;
• logs and inner instructions;
• transaction status metadata;
• balances and compute usage;
• finality guarantees.

A deshred update can fail, land on a dead fork, or never confirm.

Raw shreds roadmap

Raw shred redistribution is on the roadmap if customer demand and upstream rights line up. If you want raw shreds rather than decoded transaction intent, tell us in Telegram and include your preferred region and expected bandwidth.