Reference

EAVM

The surface compatible with the EVM ecosystem. Same chain, same ledger — seen through a wallet that expects 18 decimals and 0x addresses.

Wallet

Add the network

The button uses the canonical wallet_switchEthereumChain → wallet_addEthereumChain flow. For wallets that inject no provider, the parameters alongside cover manual setup.

custom network

Use EAV7 in your wallet

EAV7 speaks the JSON-RPC dialect that universal wallets understand — add the network in one click.

🦊 MetaMask🛡️ Trust Walletany EVM wallet

Network nameEAV7

RPC URLhttps://rpc.eavscan.com

Chain ID72020

SymbolEAV7

Explorerhttps://eavscan.com

Decimals18

Using another wallet (Trust, etc.)? Add it manually with the details above (custom network).

same account

Two identities, one account

EAVM0x71C7…9f21

nativeE7A4B2…9F21

MetaMask displays the 0x…; on-chain the balance lives in the E7… corresponding address. They're the same account.

1Click to add the EAV7 network
2Your account appears as 0x… in the wallet
3On-chain the balance lives in the corresponding E7

Parameters

What the numbers mean

The card above already has the values to copy. These are the traps behind them.

chainId: 72020 · 0x11954Decimal when adding the network by hand, hexadecimal over JSON-RPC.
Local port: 7070The public endpoint is rpc.eavscan.com; with the node on your machine it is port 7070.
Decimals: 18 · 6The wallet shows 18 decimals; the native API uses 6. Same amount, different scale.

JSON-RPC

Supported methods

Enough for wallets, contract reads and submitting a signed transaction.

bash

curl -s https://rpc.eavscan.com \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'

{"jsonrpc":"2.0","id":1,"result":"0x11954"}

Method	Description
Node and identity
`web3_clientVersion`	Node client identification.
`net_version`	Network id in decimal, as a string.
`net_listening`	Whether the node is accepting connections.
`eth_chainId`	72020 in hexadecimal: 0x11954.
`eth_syncing`	Node sync state.
`eth_accounts`	Empty list — the node holds no user keys.
State
`eth_blockNumber`	Height of the chain head.
`eth_getBalance`	0x account balance, in wei.
`eth_getCode`	Bytecode deployed at the address.
`eth_getTransactionCount`	Account nonce.
Fees and gas
`eth_gasPrice`	Current gas price.
`eth_maxPriorityFeePerGas`	Suggested tip per gas unit.
`eth_feeHistory`	Per-block fee history.
`eth_estimateGas`	Gas estimate for a call.
Blocks, transactions and events
`eth_getBlockByNumber`	Block by height.
`eth_getBlockByHash`	Block by hash.
`eth_getTransactionByHash`	Transaction by hash.
`eth_getTransactionReceipt`	Receipt with status, gas and logs.
`eth_getLogs`	Events filtered by address and topic.
Execution
`eth_call`	Runs the call without writing state.
`eth_sendRawTransaction`	Submits an already signed transaction.

Limits

What does not exist yet

Compatibility is deliberately partial. These methods are not served:

eth_sendTransactioneth_getStorageAteth_subscribeeth_newFilter

Signing stays on the client

There is no eth_sendTransaction because the node custodies no keys: sign in the wallet and submit with eth_sendRawTransaction. There is no WebSocket and no subscriptions either — poll /logs or eth_getLogs to follow events.

Unknown method

Anything outside the list returns JSON-RPC error -32601, not an empty response. Silently swallowing the unknown is how a second, divergent implementation is born.

Value

Payable contracts

From CHAIN.EAVM_VALUE_HEIGHT onward, EAVM contracts are payable over a unified ledger.

Unified ledger: The 0x world balance IS the matching native account. Value flows in, circulates and flows out without getting stuck in a bridge.
Internal transfers: Value moved by execution is not a signed transaction and has no hash of its own: it shows up in GET /internal, outside consensus.
Conversion: The RPC answers in wei; consensus works in e7. The factor is 10¹² and it holds both ways.