SOLANATPU SENDER WITH SWQOS
Solana TPU Sender with SWQoS
Direct transaction forwarding to slot leaders via stake-weighted TPU channels. Dual-path routing through SWQoS and Jito Bundle Engine. JSON-RPC, HTTP, and QUIC support across multiple global regions.
Supanode TPU Sender forwards your Solana transactions through stake-weighted channels directly to the current slot leader. When you submit a transaction, we route it via high-stake validator connections that bypass the public RPC congestion which normally drops transactions during high network activity. Dual-path delivery: your transaction goes through both our SWQoS channels and the Jito Bundle Engine simultaneously — whichever path lands first wins.
USE CASES
- + HFT & arbitrage: land in the same slot as target transactions
- + MEV extraction: dual-path delivery maximizes landing probability
- + Sniper bots: first execution on new token launches
- + Liquidation keepers: beat competition to unhealthy positions
- + Trading bots: reliable fills during volatile market conditions
- + DeFi protocols: guaranteed execution for critical operations
KEY FEATURES
- + Dual-path: SWQoS channels + Jito Bundle Engine
- + Direct TPU forwarding to current slot leader
- + 4 submission methods: JSON-RPC, HTTP Binary, HTTP Plaintext, QUIC
- + Global regions: FRA, AMS, NYC, TYO
- + Real-time leader schedule tracking
- + Standard sendTransaction API — drop-in replacement
Four submission methods, pick the one that fits your stack. JSON-RPC — standard sendTransaction, drop-in replacement for any Solana RPC provider, lowest integration effort. HTTP Binary — send raw transaction bytes (bincode serialized, up to 1232 bytes) for lower overhead, ideal for Rust/C++ systems that serialize transactions directly. HTTP Plaintext — base64-encoded transaction string without the JSON-RPC wrapper, simpler and lighter than full RPC. QUIC with TLS 1.3 — the lowest latency option, removes HTTP overhead entirely, built for HFT bots and arbitrage systems. Certificate-based auth, up to 64 concurrent streams per connection.
Our infrastructure tracks the leader schedule in real-time and forwards to the current and next leaders via their TPU. Global presence across Frankfurt, Amsterdam, New York, and Tokyo ensures your transactions take the shortest path to the leader regardless of where the current leader is located. No preflight simulations on our side — always run simulateTransaction on your own RPC before submitting. We focus on one thing: getting your transaction to the leader as fast as possible.
[SUBMISSION METHODS]FOUR WAYS TO
FOUR WAYS TO
SEND
Pick the method that fits your stack and latency requirements.
JSON-RPC
LowStandard sendTransaction — drop-in replacement for any Solana RPC provider. Works with every SDK out of the box.
Complexity: SimpleBest for: Standard integrations
HTTP Binary
LowerSend raw bincode-serialized transaction bytes directly. No base64 encoding overhead. Max 1232 bytes per transaction.
Complexity: MediumBest for: Rust/C++ systems with pre-serialized transactions
HTTP Plaintext
LowerBase64-encoded transaction string without the JSON-RPC wrapper. Simpler and lighter than full RPC calls.
Complexity: MediumBest for: Scripts, automation, quick prototyping
QUIC
LowestQUIC with TLS 1.3, removes HTTP overhead entirely. Certificate-based auth with API key as CN. Up to 64 concurrent streams per connection.
Complexity: AdvancedBest for: HFT, arbitrage, latency-critical applications
AVAILABLE
LOCATIONS
Select the location closest to your infrastructure for optimal latency, or choose multiple regions for enhanced redundancy and global coverage.
Frankfurt
Frankfurt is a major hub for blockchains infrastructure in Europe, with a high concentration of validators. Its top-tier data centers and strong network backbone provide ultra-low latency and reliable performance.
Amsterdam
Amsterdam is a key location for many blockchains infrastructure with a strong presence of validators. Hosting infrastructure here provides low latency, stable connectivity, and reliable performance for any workload.
Tokyo
Tokyo hosts numerous major data center operators providing core infrastructure. Strategic location for Asia-Pacific with low latency to major exchanges and validators.
New York
New York is a major hub for blockchains infrastructure in the United States, with a high concentration of validators. Its top-tier data centers and strong network backbone provide ultra-low latency and reliable performance.
MORE COMING SOON
MORE COMING SOON
PRICING
We encourage you to review our selection of services and our price list for Solana TPU Sender with SWQoS. Our pricing is both market-aligned and transparent. Please take your time to compare options and make the perfect choice for your needs. Expect quality and clear value.
POPULAR
Tip-Based
0.001 SOL /tx min
- + Minimum tip: 1,000,000 lamports per tx
- + Higher tip = higher priority
- + Dual-path: SWQoS + Jito Bundle Engine
- + 4 submission methods (JSON-RPC, HTTP, QUIC)
- + Pay only per transaction — no monthly fees
High Volume / B2B
Custom
- + Dedicated tip addresses
- + Custom landing rate analytics
- + Priority support & engineering access
- + Volume-based pricing
Solana TPU Sender with SWQoS FAQ
[NEED HELP?]
Standard sendTransaction via public RPC goes through an unstaked node that competes for limited bandwidth to the leader. During congestion, most of these transactions get dropped. Supanode TPU Sender routes your transaction through stake-weighted channels directly to the current slot leader's TPU, bypassing public congestion entirely. We also send through Jito's Bundle Engine simultaneously — whichever path arrives first wins.
When you submit a transaction to our TPU Sender, we forward it through two independent paths at once: (1) our stake-weighted validator connections that have priority TPU access via SWQoS, and (2) Jito's Bundle Engine for block inclusion. The slot leader receives your transaction from whichever path delivers first. This dual-path approach maximizes landing probability compared to using either channel alone.
Four methods: (1) JSON-RPC — standard sendTransaction, drop-in replacement for any Solana RPC, works with all SDKs. (2) HTTP Binary — send raw bincode-serialized transaction bytes (up to 1232 bytes), lowest overhead for Rust/C++ systems. (3) HTTP Plaintext — base64-encoded transaction without JSON-RPC wrapper, simpler than full RPC. (4) QUIC with TLS 1.3 — removes HTTP overhead entirely, supports 64 concurrent streams per connection, certificate-based auth. Starting out? Use JSON-RPC. Need lower latency? Try HTTP Binary. Building HFT or arbitrage? Use QUIC.
TPU Sender operates from Frankfurt, Amsterdam, New York, and Tokyo. Transactions are routed from the region closest to the current slot leader, not necessarily the region closest to you. Our infrastructure tracks the leader schedule in real-time and selects the optimal forwarding path automatically.
Staked RPC provides general-purpose priority RPC access — you can query accounts, subscribe to events, and send transactions with SWQoS priority. TPU Sender is specialized purely for transaction forwarding: it adds dual-path delivery (SWQoS + Jito), multiple transport protocols (including QUIC), and is optimized end-to-end for maximum landing rate. Use Staked RPC for full RPC functionality with priority, use TPU Sender when landing rate is your only metric.
TPU Sender uses the standard sendTransaction JSON-RPC method. Point your existing RPC endpoint to our TPU Sender URL, add your API key header, and submit signed transactions as usual. No SDK changes, no special serialization. Works with Rust, TypeScript, Python — any Solana SDK that supports sendTransaction.
SHORT INTEGRATION GUIDE
01
Get API Key
Sign up and receive your TPU Sender endpoint
02
Sign Transaction
Build and sign your transaction locally
03
Submit
Send via JSON-RPC, HTTP, or QUIC
04
Lands at Leader
Dual-path delivery to current slot leader