Solana Stake-Weighted Access
Transactions reach slot leaders over stake-weighted QoS (SWQoS) on the Sender / TPU path, not the public mempool — how Supanode lands txns under congestion.
- SWQoS routing direct to the slot leader
- Dual-path: SWQoS + Jito, first to land wins
- Leader schedule tracked in real time
- Pay-per-tx via tip, no subscription
- Open at 5 TPS per client
- Routing
- stake-weighted QoS to slot leader
- Delivery paths
- SWQoS + Jito Bundle Engine (parallel)
- Landed rate
- 98.7% (24h rolling)
- Submit-to-leader p50
- 1.2 ms
- Rate limit
- 5 TPS per client
- Minimum tip
- 1,000,000 lamports (0.001 SOL)
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 Sender / TPU path. There is no separate "staked RPC" subscription. Standard reads run on JSON-RPC; transaction landing runs over the stake-weighted 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. Supanode also fans out to the Jito Bundle Engine in parallel and keeps whichever path lands first.
How is it priced?
Pay-per-transaction via the tip itself — no subscription. The minimum tip is 1,000,000 lamports (0.001 SOL) per transaction. Access is open at 5 TPS per client.
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?
No. Stake-weighted access is delivered through the Sender, a drop-in endpoint: swap your RPC URL, keep your sendTransaction calls, and web3.js, Rust, Python, and Go work unchanged. Reads stay on your regular JSON-RPC endpoint; the stake-weighted path handles submission.
Which regions does the stake-weighted path run in?
Sender endpoints run in Frankfurt, Amsterdam, and Tokyo — submit to the one closest to your servers. From there Supanode tracks the leader schedule in real time and forwards over SWQoS and Jito in parallel, so you never need to chase the slot leader across regions yourself.
Get Solana Stake-Weighted Access.
Set up over Telegram with an engineer — endpoint, allowlist, tuning.