BitTorrent Chain public RPC endpoints, tested
Every keyless BitTorrent Chain (chain ID 199) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-10-11: 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. 5 of 5 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://rpc.bittorrentchain.io | 100 ms | 2 blocks | 1,000 | recent only |
| https://lb.routeme.sh/rpc/evm/199 | 361 ms | 0 blocks | under 1,000 | none |
| https://bittorrent.drpc.org | 21 ms | 14 blocks | under 1,000 | recent only |
| https://rpc.swiftnodes.io/rpc/bittorrent (SwiftNodes, keyless: 2 req/s) | 55 ms | 12 blocks | 1,000 | recent only |
| https://rpc.bt.io | 95 ms | 4 blocks | 1,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
bittorrent.drpc.org: subscribe rejected: method is not available on free plan, please upgrade to paid plan - does not stream
rpc.swiftnodes.io/ws/bittorrent(SwiftNodes): gateway: WebSocket not available for chain: bittorrent
Test any endpoint yourself with the RPC tester. Our BitTorrent Chain endpoint, limits and status: BitTorrent Chain RPC, uptime history.