Get StartedSender-Agnostic Transaction Relay
Leader-proximity-aware routing across Nozomi, Helius, 0slot, and custom senders. Slipstream selects the optimal sender based on real-time leader proximity.
Global Worker Network
Real-time worker status and leader latency across all regions. RTT values update every second.
What Slipstream Does
Leader Proximity Routing
Routes each transaction to the worker closest to the current slot leader. Each region measures real-time RTT to the active leader validator and transactions are forwarded through the lowest-latency path.
4-Protocol Fallback
QUIC (port 4433, primary) → gRPC (10000) → WebSocket (9000) → HTTP (9091). Automatic failover with configurable timeout per protocol.
Atomic Bundles
Submit 2–5 transactions as an atomic bundle (5 tokens / 0.00025 SOL). All-or-nothing execution with tip wallet support via get_senders().
TPU Direct Submission
Fire-and-forget UDP submission straight to the leader's TPU (2 tokens / 0.0001 SOL). No confirmation, no retry — absolute minimum latency.
5 Real-Time Streams
Leader hints, tip instructions, priority fees, latest blockhash, and slot updates — all streamed in real-time over your active connection.
Sender Agnostic
Automatically selects between Nozomi, Helius, 0slot, and custom senders per transaction based on leader proximity and network conditions.
How It Works
Connect via SDK
Your application connects to the nearest Slipstream worker using QUIC (preferred), gRPC, WebSocket, or HTTP. The SDK auto-discovers available regions and selects the optimal one.
Submit Transaction
Send a single transaction (1 token), atomic bundle (5 tokens), or TPU direct (2 tokens). Options include broadcast mode, deduplication, preferred sender, and retry configuration.
Proximity-Aware Routing
Slipstream identifies the current slot leader and routes your transaction to the worker with the lowest RTT to that leader. If the leader is in a US data center, the US East worker (~17ms RTT) handles it.
Sender Selection & Delivery
The worker selects the optimal sender (Nozomi, Helius, 0slot, or custom) based on the leader's identity and network conditions, then delivers your transaction. Confirmation is tracked and returned via your connection.
How Slipstream Compares
Slipstream combines intelligent sender selection with leader-proximity routing.
| Feature | Slipstream | Direct RPC | Jito |
|---|---|---|---|
| Leader RTT (US East) | <1ms | Varies (100ms+) | ~50–100ms |
| Sender Selection | Auto (proximity-aware) | Single endpoint | Jito only |
| Protocols | QUIC, gRPC, WS, HTTP | HTTP | gRPC, HTTP |
| Atomic Bundles | 2–5 tx (5 tokens) | ||
| TPU Direct (UDP) | 2 tokens | DIY only | |
| Real-Time Streams | 5 stream types | Limited | |
| Regions | 4 (dynamic discovery) | Single | Limited |
| Cost per TX | 0.00005 SOL (1 token) | RPC cost only | Tip-based |
One SDK, Three Languages
Install, connect, submit. Same API surface across Rust, TypeScript, and Python.
use allenhark_slipstream::*;
let config = Config::builder()
.api_key("sk_live_...")
.build()?;
let client = SlipstreamClient
::connect(config).await?;
let result = client
.submit_transaction(&tx)
.await?;
import { SlipstreamClient,
configBuilder }
from "@allenhark/slipstream";
const config = configBuilder()
.apiKey("sk_live_...").build();
const client = await
SlipstreamClient.connect(config);
const result = await
client.submitTransaction(tx);
from allenhark_slipstream import
SlipstreamClient, config_builder
config = config_builder()
.api_key("sk_live_...")
.build()
client = await
SlipstreamClient.connect(config)
result = await
client.submit_transaction(tx)
Pricing
Token-based billing. 1 token = 50,000 lamports = 0.00005 SOL. Deposit SOL and start sending.
Pro
- All 4 protocols
- Atomic bundles + TPU
- All 4 regions
- Priority routing
- Webhooks
Enterprise
- Volume discounts
- Dedicated workers
- Custom senders
- SLA guarantee
- Dedicated support
Ready to Route Smarter?
Start with the free tier — 100 tokens/day, no deposit required. Scale to millions of transactions across 4 regions with pay-as-you-go billing.