HashKey Chain public RPC endpoints, tested
Every keyless HashKey Chain (chain ID 177) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-10-04: 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 3 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://hashkey.drpc.org | 24 ms | 0 blocks | under 1,000 | archive (1M+) |
| https://mainnet.hsk.xyz | 177 ms | 0 blocks | 10,000+ | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/hashkey (SwiftNodes, keyless: 2 req/s) | 2186 ms | 4 blocks | 10,000+ | archive (1M+) |
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
- streams
hashkey.drpc.org: first head after 2025 ms - does not stream
rpc.swiftnodes.io/ws/hashkey(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Test any endpoint yourself with the RPC tester. Our HashKey Chain endpoint, limits and status: HashKey Chain RPC, uptime history.