Berachain RPC endpoint
Berachain (chain ID 80094) is served over HTTPS POST JSON-RPC 2.0. Full and archive nodes back the endpoint, supporting standard EVM methods, historical state, trace_* methods, debug_* methods. Every plan includes Berachain, including Free.
Network information
| Network | Berachain |
| Chain ID | 80094 |
| Endpoint | https://rpc.solidrpc.io/YOUR_API_KEY/evm/80094 |
| Type | Mainnet · L1 |
| Native currency | BERA |
| Node types | Full + Archive |
| Methods | standard, trace, debug |
| Protocol | HTTPS JSON-RPC 2.0 (no WebSocket) |
Testing first? Berachain has a testnet on SolidRPC: Berachain Bepolia.
Quickstart
Fetch the latest Berachain block number. Replace YOUR_API_KEY with a key from the dashboard, new accounts start on the Free plan, no card required (see getting started):
curl https://rpc.solidrpc.io/YOUR_API_KEY/evm/80094 \
-X POST \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'Archive access and tracing
There is no separate archive endpoint for Berachain; historical queries route to archive nodes automatically by block age, at no surcharge.
The debug_* tracing namespace is available:
curl https://rpc.solidrpc.io/YOUR_API_KEY/evm/80094 \
-X POST \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"debug_traceTransaction","params":["0xTRANSACTION_HASH",{"tracer":"callTracer"}],"id":1}'Parity-style trace_* methods are also available.
Details on archive nodes and tracing.
Limits and errors
Quotas and rate limits are account-wide, not per-chain. Method calls to Berachain draw from the same response-unit quota and rate limit as every other network. Error bodies are identical everywhere; see the error reference.