RPC endpoints and chain IDs
| L2 mainnet | Whitechain Sepolia | Legacy L1 mainnet | Legacy L1 testnet | |
| RPC | https://rpc.whitechain.io/ | https://rpc.testnet.whitechain.io | https://legacy.rpc.whitechain.io | Stopped, not available |
| Chain ID | 1875 (0x753) | 1874 (0x752) | 1875 (0x753) | 2625 (0xa41) |
| Explorer | https://explorer.whitechain.io/ | https://explorer.testnet.whitechain.io/ | https://legacy.explorer.whitechain.io/ | Stopped, not available |
| WebSocket | wss://rpc.whitechain.io/ws | wss://rpc.testnet.whitechain.io/ws | n/a | n/a |
| Explorer API | https://explorer.whitechain.io/api-docs | https://explorer.testnet.whitechain.io/api-docs | n/a | n/a |
The legacy L1 mainnet RPC and explorer are read-only and serve L1 history up to the snapshot block 50961389. The legacy RPC returns the same chain ID as L2, 1875, so do not add it to a wallet as a separate network. The legacy L1 testnet (chain ID 2625) stopped on 26 October 2026, and its endpoints are removed by 30 October 2026.
The public RPC endpoints https://rpc.whitechain.io (Mainnet) and https://rpc.testnet.whitechain.io (Whitechain Sepolia) have the same limits per client IP: 50 requests per second sustained, plus a burst allowance of up to 500 requests above that. One HTTP request can carry up to 100 JSON-RPC calls in a batch. Partners can get a higher tier, 200 requests per second with a burst of 2,000, by agreement with Whitechain.
When you exceed the limit, the endpoint returns HTTP 429 Too Many Requests with a Retry-After: 1 header. The limiter counts each HTTP request, so batching several JSON-RPC calls into one request helps. WebSocket rate limits are published once they are finalized.
What should my client do when it hits the rate limit?
In this case, retry with exponential backoff, starting from the Retry-After value; a client that retries immediately keeps failing.
Batch related calls into one JSON-RPC request. Subscribe to newHeads over WebSocket instead of polling eth_blockNumber, and cache receipts and finalized blocks on your side.
FAQ
How to identify whether an endpoint is down or the request is rate-limited?
You can check https://status.whitechain.io for the RPC, explorer, and faucet. It shows the status of the Mainnet and Testnet RPC, explorer, and explorer API, plus the testnet faucet and bridge. A 429 response means you are rate limited, not that the endpoint is down, and it clears once your request rate drops.
Do I need an API key for the public RPC?
No. The public RPC and WebSocket endpoints need no API key and no IP allowlist.
Is there a WebSocket endpoint?
Yes. Whitechain Mainnet exposes wss://rpc.whitechain.io/ws, and Whitechain Sepolia exposes wss://rpc.testnet.whitechain.io/ws. Both serve the standard Ethereum JSON-RPC API and support eth_subscribe for newHeads and logs. Whitechain Sepolia also serves newPendingTransactions; Whitechain Mainnet does not. We recommend using one connection for multiple subscriptions rather than opening one per query.
Are there third-party public RPC endpoints?
Not yet. Whitechain is evaluating partnerships with commercial RPC providers, and partner endpoints are published in the Network reference when they go live. Until then, https://rpc.whitechain.io and wss://rpc.whitechain.io/ws are the only public endpoints for Whitechain Mainnet, and https://rpc.testnet.whitechain.io and wss://rpc.testnet.whitechain.io/ws are the only ones for Whitechain Sepolia. Please treat any other endpoint claiming to serve chain ID 1875 or 1874 as unofficial.
Is the block explorer API public?
Yes. Whitechain uses Blockscout, and its API is public, read-only, and needs no API key. It exposes REST, Ethereum RPC, Etherscan-compatible RPC, and GraphQL interfaces, with API references at explorer.whitechain.io/api-docs for Mainnet and explorer.testnet.whitechain.io/api-docs for Whitechain Sepolia. It is rate-limited per IP, so batch related lookups and cache results. You can run your own indexer or Blockscout instance for sustained querying across full chain history.