The EAVM surface exists so that anyone with an EVM wallet can use EAV7 without learning anything new — and so you do not have to write a wallet from scratch.
No code. What differs from an ordinary EVM network is the decimals and the method set.
The button follows the canonical EIP-3326/3085 path: it tries to switch networks and, if the network is not in the wallet yet, adds it.
EAV7 speaks the JSON-RPC dialect that universal wallets understand — add the network in one click.
MetaMask displays the 0x…; on-chain the balance lives in the E7… corresponding address. They're the same account.
The same parameters, typed into the custom network form.
Eighteen decimals is what the wallet expects, and what the EAVM surface delivers.
Nome da rede EAV7 RPC https://rpc.eavscan.com Chain ID 72020 (0x11954) Símbolo EAV7 Decimais 18 (a superfície EAVM assume 18) Explorador https://eavscan.com Ícone https://eavscan.com/icon-512.png
If the chainId comes back right, the rest of the wallet works. 0x11954 is 72020 in hex.
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"}The same amount has two representations depending on the surface. Converting once, at the boundary, is safer than converting on every screen.
# 1 EAV7 = 1 000 000 e7 (API HTTP · CHAIN.UNIT) # 1 e7 = 1 000 000 000 000 wei (EAVM · CHAIN.EAVM_WEI_PER_E7) 5 EAV7 = 5 000 000 e7 = 5 000 000 000 000 000 000 wei
Your wallet shows a 0x address. The chain keeps the balance in an E7 account — and it is the same amount.
0x… → E7…Deterministic and stateless: the same 0x always lands on the same E7.0xe7000000…An E7 address fits inside 20 EVM bytes under the reserved prefix, checksum included — the wallet sends without knowing.The surface is honest about what it does not do; a missing method answers -32601 instead of lying.