EVM JSON-RPC

Supported EVM JSON-RPC usage on Onyx Mainnet.

Mainnet endpoint: https://rpc.onyx.org

Common methods

The public relay supports the EVM methods commonly needed by wallets, exchanges, and applications, including:

• Network and blocks: eth_chainId, net_version, eth_blockNumber, eth_getBlockByNumber, eth_getBlockByHash

• Accounts and state: eth_getBalance, eth_getTransactionCount, eth_getCode, eth_getStorageAt

• Transactions: eth_sendRawTransaction, eth_getTransactionByHash, eth_getTransactionReceipt

• Contracts and fees: eth_call, eth_estimateGas, eth_gasPrice, eth_maxPriorityFeePerGas

• Events: eth_getLogs and supported filter/subscription methods

Onyx does not promise support for every Ethereum client extension, debug method, pending-pool behavior, or future RPC method. Probe the exact method set your application requires and handle method not found or method not supported responses.

Example

curl -sS https://rpc.onyx.org \
  -H 'content-type: application/json' \
  --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

Onyx-specific considerations

• Native XCN is returned in 18-decimal RPC units but settles at 8-decimal ledger precision.

• eth_estimateGas must be used for transfers because the recipient account may need to be created.

• Read the current gas price; do not use fixed price tiers copied from another network.

• Public capacity and throttling can change. Back off on transient errors and arrange dedicated service before depending on a specific SLA.