SWQoS Endpoint

SWQoS (Stake Weighted Quality of Service)

SWQoS is a mechanism where leaders prioritize connections through staked validators. While RPCs themselves do not hold stake, they can access priority bandwidth by peering with staked validators. At ERPC, SWQoS is now available not only for dedicated RPCs but also for shared plans. On shared SWQoS endpoints, 1 TPS is allocated for every 4.2 elSOL held, and the capacity scales with the amount of elSOL you own. The growth of elSOL holders directly contributes to expanding ERPC’s overall SWQoS bandwidth.

Dedicated RPC Nodes

For HTTP and WebSocket, transaction-focused

Because you exclusively use the RPC bandwidth, you remove one layer of randomized admission and congestion compared with shared endpoints. With no impact from other users, latency is dramatically reduced. Slot lag is less likely even at peak times. CPU and memory can be scaled to your requirements. If you run your app on our zero-distance bare metal, it stays entirely within the same network and minimizes public internet traversal, enabling further acceleration. We also support globally distributed architectures.

€ 1,280-/mo

Dedicated SWQoS

Dedicated SWQoS

You can apply SWQoS to your dedicated RPC node. In dedicated setups the bottleneck is typically sending, not data retrieval. A dedicated RPC without stake-backed peering can only use the non-priority bandwidth (20%), so transaction inclusion is limited to about one fifth. As a result, inclusion tends to be deferred to later slots. Applying SWQoS lets you use the priority lane and significantly increases inclusion probability and success rate.