Preprocessed transaction streams.
Preprocessed gRPC gives you transaction intent before normal processed metadata, delivered over gRPC so you do not have to rebuild raw shreds yourself.
50% OFFLaunch offer on Desk, from $499/mo. Paid onboarding support on request.
◆ OVERVIEW
Preprocessed gRPC is a transaction-intent stream produced from decoded shreds before the validator exposes normal processed transaction metadata. It is earlier than processed metadata, but it does not include execution result, logs, account writes, balances, or final status.
Shreds are the fragments validators propagate before a block is assembled. rpc edge reconstructs transaction intent from that layer and streams it over gRPC so latency-sensitive consumers can react before normal processed transaction metadata is available.
The decoding happens server-side, co-located with the cluster, so you receive ready-to-use transaction intent rather than raw bytes. Use Yellowstone gRPC when you need executed account state, logs, balances, or status metadata.
Available on Desk from $499/mo.
◆ CAPABILITIES
What Preprocessed gRPC does.
Earlier transaction intent
Read transaction intent before normal processed metadata is emitted.
Built for trading filters
Designed for transaction filters that matter to trading systems, not broad archive indexing.
Decoded server-side
Reassembled and deserialized before they hit your stream, so you can act without handling raw shred reconstruction.
Delivered over gRPC
Delivered over gRPC as a bounded premium stream alongside Yellowstone gRPC.
// conceptual route selection for a preprocessed transaction stream
const stream = await rpcedge.subscribe({
source: "preprocessed",
filter: { programs: [RAYDIUM, PUMP_FUN] },
});
for await (const tx of stream) {
signal.evaluate(tx); // react early, reconcile on processed/finalized state
}◆ WHY rpc edge
Latency is a location problem.
Subscribe instead of polling
Yellowstone gRPC pushes filtered account, slot, and transaction updates over one persistent stream, so your bot does not need to rebuild the same polling loop.
Choose the data your workload needs
Use standard RPC for state and history, Yellowstone gRPC for live validator updates, or preprocessed transactions when earlier intent matters to the strategy.
Start shared, move dedicated
Launch on a self-serve plan with included bandwidth. Move to private bare metal, regional placement, and an SLA when traffic or latency requirements justify it.
◆ USE CASES
- Arbitrage and sniping where landing first is everything
- MEV searchers needing the earliest signal
- Liquidation bots reacting before confirmation
Frequently asked questions
What is preprocessed gRPC?
Is preprocessed data safe to act on?
How is this different from Yellowstone gRPC?
◆ GET ACCESS
See transactions before the block lands.
Pick a plan and point your client at a scoped endpoint, or talk to the infra team to scope a dedicated, co-located node tuned to your latency and volume.
50% OFFLaunch offer on Desk, from $499/mo. Paid onboarding support on request.
DESHRED · gRPC
- Earlier transaction intent
- Built for trading filters
- Decoded server-side
- Delivered over gRPC