Solana Stake-Weighted Access
Transactions reach slot leaders over stake-weighted QoS (SWQoS) on the TPU Sender path, not the public mempool — how Supanode lands txns under congestion.
- SWQoS routing direct to the slot leader
- One UDP packet per transaction
- #1 of 18 senders in a live benchmark
- Flat monthly, Standard or High-volume
- Frankfurt and Amsterdam
- Routing
- stake-weighted QoS to slot leader
- Transport
- UDP, API key + transaction per packet
- Benchmark
- #1 of 18 submission services
- Tips paid in benchmark
- 0 SOL
- Pricing
- flat monthly per sending server
- Regions
- FRA · AMS
Stake-weighted access, straight to the leader.
Txns reach slot leaders over stake-weighted QoS (SWQoS) — staked-connection nodes hold a priority lane into the current leader, not the public mempool. How Supanode lands txns under congestion.
Is stake-weighted access a separate product?
No — stake-weighted access is how Supanode lands transactions: SWQoS routing direct to the slot leader, delivered through the TPU Sender path. There is no separate "staked RPC" subscription. Standard reads run on JSON-RPC; transaction landing runs over the stake-weighted TPU Sender path.
How does stake-weighted routing improve landing?
Public RPC drops transactions under load. SWQoS sends your transaction directly to the current slot leader over a stake-weighted channel, bypassing the crowded mempool.
How is it priced?
Through the TPU Sender plans: flat monthly per sending server, Standard or High-volume. There is no per-transaction charge; exact prices are on the pricing page.
What is stake-weighted QoS (SWQoS)?
A Solana mechanism that allocates inbound transaction bandwidth at the slot leader in proportion to validator stake. Connections backed by high stake keep landing under congestion while unstaked traffic is shed first. Supanode submits over stake-weighted channels, so your transactions take the prioritized lane.
Do I need to change my code to use stake-weighted access?
A little. The TPU Sender takes each signed transaction as one UDP packet with your API key in front, instead of an RPC call. That is a few lines in any language, and a ready Rust client comes with onboarding. Reads stay on your regular JSON-RPC endpoint.
Which regions does the stake-weighted path run in?
Frankfurt and Amsterdam. Send from the region closest to your servers; the endpoint is private and comes with your API key.
Get Solana Stake-Weighted Access.
Set up over Telegram with an engineer — endpoint, token, tuning.