# Shredstream

Pre-execution Solana transaction streaming via Jito ShredStream, Shyft RabbitStream...

- Repository: https://github.com/agiprolabs/claude-trading-skills (507 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-09-03
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add agiprolabs/claude-trading-skills --skill shredstream -g -a claude-code -y`
Codex: `npx skills add agiprolabs/claude-trading-skills --skill shredstream -g -a codex -y`
Cursor: `npx skills add agiprolabs/claude-trading-skills --skill shredstream -g -a cursor -y`
Gemini CLI: `npx skills add agiprolabs/claude-trading-skills --skill shredstream -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add agiprolabs/claude-trading-skills`

## Description

Pre-execution Solana transaction streaming via Jito ShredStream, Shyft RabbitStream, and Triton Deshred

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# ShredStream, Pre-Execution Solana Data

ShredStream gives you transaction data **before the validator executes the block**, typically 100-500ms earlier than standard Yellowstone gRPC. You see transaction *intent*, not confirmed results.

This is the fastest path to Solana data for time-critical trading strategies.

## How It Works

Solana validators produce blocks by serializing transactions into **shreds** (~1,228 bytes each, sized for UDP MTU). Shreds propagate through Turbine (Solana's fanout protocol, 2-3 hops). ShredStream bypasses Turbine by receiving shreds **directly from leader validators** via Jito's Block Engine.

```
Leader Validator
     │
     ├── Turbine (standard, 2-3 hops, 200-500ms)
     │       └── Your RPC Node → Yellowstone gRPC (post-execution)
     │
     └── Jito Block Engine (direct)
              └── ShredStream Proxy (your server)
                   ├── UDP shreds → Your RPC/Validator (faster block building)
                   └── gRPC entries → Your Trading Bot (decoded transactions)
```

### What You Get vs. What You Don't

| Available (Pre-Execution) | NOT Available (Needs Execution) |
|---------------------------|--------------------------------|
| Transaction signatures | Success/failure status |
| Account keys (pubkeys) | Balance changes (pre/post) |
| Instructions (program, accounts, data) | Log messages |
| Address lookup table references | Inner instructions (CPI) |
| Slot number | Token balance changes |
| | Compute units consumed |

**Key tradeoff**: Speed for completeness. You see what's *about to happen* but can't confirm it actually succeeded. Some transactions you see will ultimately fail.

## Three Ways to Get Pre-Execution Data

The rest: https://github.com/agiprolabs/claude-trading-skills/blob/HEAD/skills/shredstream/SKILL.md