Ethereum

The Ethereum Gateway provides standard EVM JSON-RPC for reading state, calling contracts, and submitting signed transactions. Its gas token is ETH.

Supported networks

Copy the complete Access Point from the dashboard instead of constructing a domain from the Host.

Endpoint-free calls

On an Accelerator hit, you can call eth_blockNumber, eth_getBlockByNumber([hexHeight, false]), and debug_traceBlockByNumber([hexHeight, {"tracer":"callTracer"}]) without an Endpoint. See Accelerator for exact parameters and miss behavior.

Configure complete method access

1. Create a Gateway for the target network.
2. Use Provider sync or manually add an EVM Endpoint on the same network.
3. Add the Endpoint to the default JSON-RPC route and confirm its health check passes.
4. Call eth_chainId to 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 should return 0x1; Sepolia should return 0xaa36a7.

eth_chainId is not an Accelerator method, so this verification requires a usable Endpoint.

Current limits

• Single EVM JSON-RPC calls over HTTP are supported; batch, WebSocket, and public gRPC are not.
• Ethereum Beacon API and generic REST endpoints are not exposed.
• Archive, trace, and debug methods depend on the upstream node and plan. The Gateway does not fill upstream capability gaps.
• Sign transactions in the client. See Routing and reliability before retrying writes.

See JSON-RPC and Errors and troubleshooting for shared behavior.