UpgradesSeptember 14, 2026by
EmpoorioChain Core
EmpoorioChain Core

Runtime 211: The EVM Accepts Real Transactions

Before

From the 31 August relaunch through runtime 208, EmpoorioChain's EVM was readable and not writable. eth_chainId, eth_blockNumber, eth_getBalance all answered; eth_sendRawTransaction was rejected at validation, every time. Measured on 6 September 2026. MetaMask, Hardhat, viem, ethers and the Eoonia browser extension were all blocked. The public-sale contract could not have been deployed on this chain.

The cause

Frontier submits an Ethereum transaction as an unsigned Substrate extrinsic whose validity comes from the Ethereum signature inside. That requires the runtime's RuntimeCall to implement SelfContainedCall, so the transaction pool can ask the call to validate itself. EmpoorioChain's runtime used a generic extrinsic type without it.

The change

Runtime 211 implemented SelfContainedCall for RuntimeCall, delegating Ethereum::transact to pallet-ethereum's validation and dispatch. A normal-class upgrade under the policy (no economic change), though arguably security-adjacent since it touches the transaction path.

Verification

  • 10 September, runtime 213 live: signed transactions from MetaMask and Hardhat on chain id 2026 included and finalized.
  • Eoonia's EVM integration matrix: 43 of 43 operations verified against the live chain by 14 September.
  • web3_clientVersionempoorio-chain/v208.1/fc-rpc-2.0.0-dev on both public nodes.

What it unblocked

  • Solidity deployment to EmpoorioChain (the sale contract remains on Sepolia by design — it takes USDC on Ethereum — but any dApp contract can now target 2026).
  • The Eoonia extension as an Ethereum provider.
  • The 0xAA AI-oracle precompile becoming reachable from a contract.
  • Runtime 220's gas-price fix (1 gwei), which only matters once transactions execute.

What it exposed

On runtime 213, eth_getCode(addr, 'latest') returns 0x for contracts that have code; only 'pending' returns it. Deployment scripts that confirm by reading code at latest report false failures. Clients verify by nonce and receipt; filed as a Frontier-integration issue.

The old page

Described validators adopting a client version on another network. EmpoorioChain has one client, upgraded in place; this page records the upgrade that made its EVM real.

Based on the Frontier finding (2026-09-06), RED.json (rpc_evm_expuesto) and the Eoonia integration matrix.

Share this article