Developer

42M Monthly Tokens
- 50 Requests/sec
Hourly pricing unavailable
Stake-weighted priority (SWQoS)
Solana’s leaders split priority bandwidth in two. Connections backed by stake — SOL committed to a validator — get 80% of it. Everyone else fights over the other 20% — the lane that’s packed with spam.
Firing straight at the leader feels like the fast move — but with no stake, that’s the crowded 20% lane, and under load your transaction never makes the block.
So the real answer is a staked validator. We run a top-tier one wired into high-quality RPC lines — hardware placed right next to Solana — so your transactions get through the wide lane.
A top-tier validator in our Shinobi Performance Pool
How Solana’s leaders split priority bandwidth
Stake rides the wide 80% lane into the validator — before any fee. No stake, you’re crammed in the 20% spam lane.
80 / 20 split set by Solana’s leaders, not by us

42M Monthly Tokens
Hourly pricing unavailable

420M Monthly Tokens
Hourly pricing unavailable

2,420M Monthly Tokens
Hourly pricing unavailable
FAQ
Open the ERPC Web Dashboard at dashboard.erpc.global. For the shared SWQoS endpoint, use an eligible ERPC plan and connect the wallet that holds elSOL; allocation is calculated from that elSOL balance. Dedicated RPC subscribers can add a 1,000 SOL staking allocation for +€100/month.
On the shared stake-weighted QoS endpoint, eligible users receive 1 TPS for every 4.2 elSOL held. For example, holding 10 elSOL grants 2 TPS. The TPS you can actually use is capped at the lower of your plan maximum or the elSOL-based allocation. The shared endpoint runs in Frankfurt.
Choose a dedicated RPC node over the shared endpoint when you need consistently stable, fast responses, because you are the sole user of that resource and stay unaffected by other customers' traffic. The shared endpoint splits resources across many users, so latency tends to rise as traffic grows. Dedicated RPC subscribers can add stake-weighted QoS as a +€100/month option that assigns a 1,000 SOL staking allocation to the dedicated node.
The leader rotates slot by slot, and the schedule shifts each epoch, so landing first means knowing which validator leads next and where it is located, then timing execution to it. ERPC provides the Leader Slot API (getLeaderSlots), which returns the upcoming leader schedule, stake weight for the current epoch, estimated validator geolocations, and reference ping values, giving you granularity that public maps and native RPC APIs lack. Pairing stake-weighted QoS with that routing precision is how you target the lowest-latency slots.
Place your infrastructure in the same region as the endpoint to reach roughly 400ms or better, because streaming latency runs about five times the raw ping. A same-network ping is around 0.1ms, and dedicated nodes can shave around 20ms more by using HTTP to skip the TLS handshake. The typical performance order is Direct Shreds first, then Geyser gRPC, then WebSocket.
While your subscription stays active, the sale price you locked in at signup stays in effect, even though ERPC plans to raise list prices as demand grows. You can pay with SOL, USDC, or EURC (available for EU billing countries) to buy ERPC Credits in the ERPC Web Dashboard and use them to activate or continue plans.
Issue an API key and test low-latency RPC, Geyser gRPC, Direct Shreds, and SLV AI. Measure first, then expand into Dedicated Nodes, VPS, or Bare Metal when your production path is clear.