The transaction
A standard Ethereum-format signed transaction — the kind MetaMask produces — sent to https://rpc.testnet.empooriochain.org with chain id 2026 in its signature, accepted by the pool, included, finalized. Verified on runtime 213 on 10 September 2026, then across 43 of 43 EVM operations in Eoonia's matrix by the 14th.
Why every earlier one was rejected
Frontier submits an Ethereum transaction as an unsigned Substrate extrinsic whose validity is the Ethereum signature inside it. The runtime must implement SelfContainedCall so the pool can ask the call to validate itself. EmpoorioChain's runtime used a generic extrinsic type without it — measured on 6 September, when eth_* reads had just started working and writes were tried for the first time. Fixed in runtime 211.
What it unlocked
- MetaMask, Hardhat, Foundry, viem, ethers against EmpoorioChain.
- The Eoonia browser extension as an Ethereum provider (EIP-712, chain switching).
- Solidity deployment to the chain itself; the
0xAAAI-oracle precompile reachable from a contract. - Runtime 220's gas price (1 gwei) having anything to price.
What it exposed
eth_getCode(addr, 'latest') returning 0x for deployed contracts on 213 — clients verify by nonce and receipt.
One ledger
The EVM account that sent that transaction holds the same DMS as its native counterpart. There is no wrapped token on EmpoorioChain's EVM; a former bridge precompile was retired to keep it that way. The first EVM transaction moved native DMS, seen through an Ethereum address.
The tour
The page this replaces launched a world tour of hacker houses. EmpoorioChain's EVM made one trip — from reads only to accepts transactions — in five days, and stayed home.
Based on the Frontier finding (2026-09-06), RED.json (rpc_evm_expuesto) and the Eoonia EVM matrix.