Building a trading bot, monitoring DEX activity or researching transaction patterns on Solana starts with a question: how should your application receive transaction data?
For developers looking for Solana public order flow, two useful options are raw shreds and reconstructed transaction streams. They expose different interfaces to early network data—and require different amounts of integration work.
Shredo offers both: Raw Shreds over UDP and Decoded Transactions over authenticated gRPC.
This guide explains what public order flow means on Solana, how the two formats differ and which one fits your application.
What is public order flow on Solana?
In trading, order flow describes the stream of buying, selling and other transaction activity that applications observe and analyse.
On Solana, “public order flow” is best understood as a broad description of observable network activity—not the name of a single protocol or a universal pending-transaction endpoint.
Solana does not use the same globally gossiped public mempool model familiar from Ethereum. Its transaction-forwarding architecture directs transactions toward scheduled leaders instead. Solana’s explanation of Gulf Stream describes this distinction.
For developers, that means choosing a data interface based on what the application actually needs:
- Raw network data for a custom reconstruction pipeline.
- Reconstructed transactions for filtering and transaction analysis.
- Execution and account-state updates for tracking outcomes.
- Confirmed or finalized records for reconciliation and historical research.
These are related views of transaction activity, but they are not interchangeable.
How do Solana shreds fit into transaction data?
Shreds are small fragments of Solana block data. Applications can reconstruct entries and transactions from those fragments rather than waiting for a complete block response.
This makes shred-based ingestion useful for systems that need to observe transaction activity while block data is still propagating. The underlying format is designed for network propagation, however—not for direct consumption as a list of swaps. Solana shred format overview
Receiving shreds is therefore the beginning of a processing pipeline. Your application still needs to reconstruct the relevant data and interpret the transactions it recovers.
That is the main distinction between Shredo’s Raw Shreds and Decoded Transactions.
Raw Shreds: control your own processing pipeline
Shredo Raw Shreds delivers deduplicated Solana shreds over UDP to one public IPv4 address and port.
Choose this product when you already have a deshredder, are building your own transaction-processing infrastructure or want control over how reconstruction works.
Your application handles:
- Receiving UDP packets.
- Reconstructing entries and transactions.
- Parsing transaction messages.
- Applying program, account and strategy-specific logic.
Raw Shreds gives you flexibility, but also responsibility for the receiving pipeline. UDP does not guarantee delivery or ordering, so a production receiver should account for packet loss and incomplete reconstruction.
Price: 99 USDC per calendar month.
Decoded Transactions: work directly with transaction events
Shredo Decoded Transactions delivers reconstructed, signed Solana transactions over a TLS-protected gRPC stream.
Instead of operating a UDP receiver and implementing shred reconstruction, your application consumes transaction events through a versioned Protobuf interface.
The stream includes transaction signatures, serialized signed transaction data, instructions, account information and observation metadata. Program and account filters help narrow the stream to the activity relevant to your application.
Choose Decoded Transactions when your work starts at the transaction layer:
- Monitoring transactions involving selected programs.
- Following activity associated with specific accounts.
- Building transaction classification pipelines.
- Feeding research, alerting or trading systems.
Here, decoded means transaction-level reconstruction and parsing. It does not automatically mean a fully interpreted DEX trade with execution logs, balance changes and confirmed results.
Price: 399 USDC per calendar month. A separate Raw Shreds subscription is not required.
Raw Shreds vs Decoded Transactions
| Feature | Raw Shreds | Decoded Transactions |
|---|---|---|
| Data format | Raw shred packets | Reconstructed signed transactions |
| Transport | UDP | gRPC over TLS |
| Connection setup | One public IPv4 address and UDP port | Outbound client connection with an API key |
| Shred reconstruction | Handled by your application | Handled before delivery |
| Program and account filtering | Implemented in your pipeline | Supported by the service |
| Best fit | Custom ingestion infrastructure | Applications working with transaction events |
| Monthly price | 99 USDC | 399 USDC |
The choice is primarily about where you want your application’s work to begin.
If you already operate a reconstruction pipeline, Raw Shreds may fit naturally. If you want to spend more time on transaction logic and less on packet processing, Decoded Transactions removes that reconstruction step.
Early observation is not execution confirmation
A transaction appearing in a stream does not, by itself, prove that it succeeded or became final.
Applications should distinguish between:
- Observing transaction data.
- Verifying execution and its result.
- Establishing confirmation or finality.
Solana’s commitment levels—processed, confirmed and finalized—describe different levels of confidence in chain state. They should not be inferred from a feed’s delivery timestamp. Solana transaction confirmation guide
For production systems, pair early transaction observations with the execution or state interface appropriate to your task. For example, detecting a transaction that references a pool is different from confirming the pool’s resulting balances.
Neither Shredo product should be treated as a guarantee of profitable execution, complete network visibility or uninterrupted historical coverage.
Is this the same as private order flow?
No.
Private order flow involves an explicit arrangement to access transactions or trading intentions before their normal broadcast—for example, through a wallet or trading application.
A shred-based transaction feed is a different data product. Receiving a transaction through Raw Shreds or Decoded Transactions does not give your application exclusive access, control over its original submission or a guaranteed position immediately after it.
For transaction analysis, the important question is not simply whether a feed is labelled “public” or “private.” It is what data it exposes, when your application observes it and what that observation actually proves.
Frequently asked questions
Does Solana have a public mempool?
Not a globally gossiped public mempool equivalent to Ethereum’s. Developers instead use interfaces such as shred feeds, transaction streams and execution or account-state subscriptions.
Do I need to run a validator to use Shredo?
No. Raw Shreds requires a suitable receiving server and your own processing pipeline. Decoded Transactions can be consumed by a TLS-capable gRPC client.
Does Decoded Transactions include confirmed swap results?
No. It provides reconstructed transaction data. Canonical execution results, logs and finality require separate verification.
Can I buy Decoded Transactions without Raw Shreds?
Yes. They are separate products with separate subscriptions.
Which product should I start with?
Choose Raw Shreds if you need to operate your own reconstruction pipeline. Choose Decoded Transactions if your application needs transaction events without implementing shred reconstruction.
Start building with Shredo
Choose the interface that matches your infrastructure:
Raw Shreds for your own UDP ingestion and reconstruction pipeline.
Decoded Transactions for signed transaction events, program and account filtering, and gRPC integration.