Ethereum
Ethereum is the reference EVM network in the Gateway catalog. Its gas token is ETH, and the Gateway exposes standard EVM JSON-RPC for reading state, calling contracts, and submitting signed transactions.
Networks and hosts
| Network | Chain ID | JSON-RPC Host |
|---|---|---|
| Mainnet | 1 | ether-jsonrpc |
| Sepolia | 11155111 | ether-sepolia-jsonrpc |
Host is the prefix of the Access Point shown in the dashboard. Copy the complete Access Point from the dashboard rather than assembling a domain from the prefix.
Mainnet and Sepolia are separate Gateways with separate Routes, so an Endpoint created for one network cannot serve the other.
Provider coverage
Ethereum is the only chain family in the catalog where all five Provider integrations reach both networks.
| Provider | Mainnet | Sepolia | How Endpoints appear |
|---|---|---|---|
| Alchemy | Yes | Yes | Generated from the Gateway catalog, API key applied as a path credential |
| QuickNode | Yes | Yes | Imported from Endpoints that already exist in your QuickNode account |
| Chainstack | Yes | Yes | Imported from nodes in the running state |
| dRPC | Yes | Yes | Generated as lb.drpc.live load-balancer URLs |
| Tenderly | Yes | Yes | Generated as <network-slug>.gateway.tenderly.co Node RPC URLs |
Because five vendors overlap here, Ethereum Routes are a practical place to hold one primary upstream plus ordered backups from a different vendor. See Providers for the shared synchronization workflow.
Reads without an Endpoint
Three EVM request shapes check the shared cache before Endpoint selection: eth_blockNumber, eth_getBlockByNumber with ["latest", false] or an explicit hexadecimal height and false, and debug_traceBlockByNumber with the callTracer configuration. Other parameter variants require a Route. Endpoint-free RPC lists the exact forms and cache behavior; authentication, rate limits, and Usage accounting apply whether or not the cache answers.
Verify the network
curl '<ethereum_access_point>' \
-H 'Authorization: Bearer <app_api_key>' \
-H 'Content-Type: application/json' \
--data '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'Mainnet returns 0x1; Sepolia returns 0xaa36a7. Run the call after the Route has a healthy Endpoint so the answer reflects the upstream you configured.
Coverage boundary
The Gateway accepts one JSON-RPC 2.0 object per HTTP POST. Archive depth, debug and trace namespaces, and historical state follow the upstream node’s software, plan, and enabled namespaces. Validate those against the vendor plan rather than against Gateway network support.
See JSON-RPC for request format and Errors and recovery for Gateway error codes.