// solana · tpu-sender

Solana TPU Sender

Routes your txns straight to upcoming slot leaders over stake-weighted TPU. Lands 98.7% at 1.2 ms submit p50 — just swap your RPC URL.

Solana · tpu-sender● live
landed rate
98.7 %
submit p50
1.2 ms
min tip
0.001 SOL
01.WHAT'S INCLUDED// Solana · tpu-sender
  • Dual-path: SWQoS direct + Jito in parallel
  • Drop-in — keep your sendTransaction calls
  • Real-time leader-schedule tracking
  • Pay-per-use via tips, no monthly fee
  • web3.js · Rust · Python · Go
// factsSPEC
Landed rate
98.7% (24h rolling)
Submit-to-leader p50
1.2 ms
Delivery paths
SWQoS + Jito Bundle Engine
Regions
FRA · AMS · TYO
Minimum tip
1,000,000 lamports (0.001 SOL)
Rate limit
5 TPS per client
02.HOW IT WORKS// dual-path tpu routing

Your tx, two paths, first one wins.

Every tx is fanned out over two paths at once — SWQoS direct to the slot leader, and the Jito Bundle Engine. First to land wins; no more lost to mempool congestion.

SWQoS direct path — bypasses the public mempool, stake-weighted
Jito bundle path — block-engine inclusion, optional tips
Leader schedule tracked in real time so SWQoS targets the correct validator
// DUAL-PATH ROUTING
your bot
sendTransaction
supanode tpu
fan-out
SWQoSpath 1
leader
peer
Jitopath 2
bundle
stage
landed← first wins
03.FAQ// 5 questions
How does the TPU Sender land transactions?

Every transaction is fanned out over two paths in parallel: stake-weighted QoS direct to the current slot leader, and the Jito Bundle Engine. Whichever lands first wins; the other is dropped. Supanode tracks the leader schedule in real time so the SWQoS path always points at the correct validator.

Do I need to change my code?

No — it is a drop-in endpoint. Swap your RPC URL for the Sender URL and keep your sendTransaction calls as they are. It works with web3.js, Rust, Python, and Go.

How is the TPU Sender priced?

Pay-per-transaction via the tip itself, with no monthly fee. The minimum tip is 1,000,000 lamports (0.001 SOL) per transaction; a higher tip buys higher priority under congestion. Access is open at 5 TPS per client.

What submission methods are supported?

Three: JSON-RPC (standard sendTransaction, the easiest drop-in), HTTP Plaintext (base64 transaction without the JSON-RPC wrapper), and HTTP Binary (raw bincode bytes up to 1,232 bytes, the lowest overhead). Pick by how much you care about latency versus simplicity.

Which region should I send to?

The one closest to your servers — Frankfurt, Amsterdam, or Tokyo. The Sender already fans out to the leader over SWQoS and Jito in parallel, so duplicating sends across regions does not improve landing; it just multiplies network load and tip risk.

Get Solana TPU Sender.

Set up over Telegram with an engineer — endpoint, allowlist, tuning.