EVM
The Ethereum-compatible lane — endpoints, what it accepts on each network, gas in VORD, and the JSON-RPC methods it serves.
Vordium runs an Ethereum-compatible lane beside its native operations. Its state is part of the chain's state root, and gas is paid in VORD.
Whether the EVM runs contracts right now: —.
On the main network the EVM lane answers reads. It does not accept transactions: eth_sendRawTransaction answers
-32003 "transaction rejected: EVM transactions are not accepted on Vordium; use the app or the SDK". Trading is done
with the native operations (Orders).
Endpoints
| Fact | Mainnet | Testnet |
|---|---|---|
| Chain id | 101101 | 101102 |
| Chain id (hex) | 0x18aed | 0x18aee |
| Native lane (JSON-RPC at the root) | https://rpc.vordium.com | https://rpc-testnet.vordium.com |
| EVM lane | https://rpc.vordium.com/evmrpc | https://rpc-testnet.vordium.com/evmrpc |
| Native token | VORD | VORD |
| Decimals | 18 | 18 |
The root address answers JSON-RPC as the native chain's view; the EVM lane answers as the EVM. Both also take
WebSocket connections (wss:// at the same address).
Gas
Gas is paid in VORD, which has 18 decimals. eth_maxPriorityFeePerGas answers 0x0: no tip is needed.
JSON-RPC
The full list of methods, what each answers and the error codes are in the JSON-RPC reference.
In short: the usual read methods work (eth_chainId, eth_blockNumber, eth_getBlockByNumber, eth_getBalance,
eth_call, eth_getLogs, receipts), block filters work, and eth_subscribe("newHeads") works over WebSocket.
Two things differ from Ethereum:
- A height with no block answers
nullfrometh_getBlockByNumber— empty heights are normal. - Consecutive blocks are not parent-linked the way Ethereum blocks are.
Network facts last checked against the network 2026-10-22 13:00:37 UTC · mainnet spec v28 · testnet spec v8