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-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. 4 of 5 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://bittorrent.drpc.org | 25 ms | 0 blocks | under 1,000 | recent only |
| https://rpc.swiftnodes.io/rpc/bittorrent (SwiftNodes, keyless: 2 req/s) | 56 ms | 1 blocks | under 1,000 | recent only |
| https://rpc.bittorrentchain.io | 105 ms | 5 blocks | under 1,000 | recent only |
| https://rpc.bt.io | 108 ms | 7 blocks | under 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): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
lb.routeme.sh/rpc/evm/199: eth_blockNumber failed
Test any endpoint yourself with the RPC tester. Our BitTorrent Chain endpoint, limits and status: BitTorrent Chain RPC, uptime history.