Viction public RPC endpoints, tested
Every keyless Viction (chain ID 88) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-11-22: does it answer on the right chain, how fast, how far behind the best head, how large an eth_getLogs range it accepts, whether it keeps archive state, and whether its WebSocket actually streams. 3 of 4 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://lb.routeme.sh/rpc/evm/88 | 48 ms | 0 blocks | 1,000 | none |
| https://rpc.swiftnodes.io/rpc/viction (SwiftNodes, keyless: 2 req/s) | 90 ms | 3 blocks | under 1,000 | archive (1M+) |
| https://rpc.viction.xyz | 171 ms | 11 blocks | 10,000+ | recent only |
Order: endpoints within 3 blocks of the best head first, then by median latency. Latency is measured from one server, so yours will differ by region; lag and limits do not.
WebSocket endpoints
- does not stream
viction.drpc.org: chainId: You reached Public endpoint rate limit, please upgrade to paid plan - does not stream
rpc.swiftnodes.io/ws/viction(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
viction.drpc.org: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our Viction endpoint, limits and status: Viction RPC, uptime history.