Sender
Direct TPU transaction delivery via SWQoS plus Jito Bundle Engine in parallel. Pay-per-transaction via tip - no subscription.
// updated 2026-06-04
Direct TPU transaction delivery for traders. Routes transactions to slot leaders through stake-weighted TPU channels and Jito Bundle Engine in parallel - whichever lands first wins.
Tips are required. Every transaction must include a System Program transfer to one of Supanode's tip accounts, minimum 1,000,000 lamports (0.001 SOL). Without a valid tip, the transaction is rejected at the gateway.
What is Sender for?
Public RPC drops transactions under heavy load. Sender bypasses the crowded RPC layer and pushes your transaction directly to the current slot leader.
| Use case | Why Sender |
|---|---|
| HFT and arbitrage | You can't afford a missed leader window |
| MEV extraction | Direct TPU + Jito tips in one call |
| Sniper bots | Token launches need sub-second landing |
| Liquidation keepers | Race conditions decided at TPU layer |
| Trading in volatile markets | Reliability when public RPC is congested |
How it works
Your app → Sender → [SWQoS TPU + Jito Bundle Engine] → Slot leader
Each transaction is forwarded along two paths in parallel:
- SWQoS (stake-weighted Quality of Service) - directly to the current slot leader.
- Jito Bundle Engine - via the validator block-building auction.
Whichever path lands the transaction first wins. The other is dropped silently. Supanode tracks the leader schedule in real time so the SWQoS path always points at the correct validator.
Preflight is never run. Sender doesn't simulate before forwarding. Validate locally first via RPC simulateTransaction.
What is the Sender rate limit?
5 TPS per client. This is the throughput Sender provides — the same for every client. Sender is open access; no Bundle subscription is required.
Pricing
Pay-per-transaction via the tip itself - no subscription, no fixed monthly fee. The minimum tip is 1,000,000 lamports (0.001 SOL) per transaction.
See Tips for tip addresses and code samples.
External references
Where to next
First request in 5 minutes.
JSON-RPC, HTTP Plaintext, HTTP Binary.
Minimum tip and tip addresses.
Regional endpoints and routing.