---
title: Solidity on the Frontier EVM
description: Deploying and calling Solidity contracts on EmpoorioChain's Frontier EVM (chain id 2026) — what works, what is measured, what is not.
---

# Solidity on EmpoorioChain (Frontier EVM)

Use the EVM when you have Solidity you do not want to rewrite, or need logic no pallet provides.

## Network

- RPC: `https://rpc.testnet.empooriochain.org` (also `rpc2.`); Ethereum JSON-RPC (`eth_*`) on the same endpoint
- Chain id: `2026` (`0x7ea`) — not 1337, 9911 or 27777
- Currency: DMS, 18 decimals
- Gas: `eth_gasPrice` → 1 gwei (EIP-1559 with base fee) since runtime 220; a simple transfer costs 21,000 × 1 gwei = 0.000021 DMS
- Known defect: `eth_getCode(addr, "latest")` returns `0x` for contracts with code; use `"pending"` or verify by nonce

## Accounts

The H160 is derived from the same seed as the sr25519 account. Its native balance lives at `blake2_256("evm:" ++ H160)`; fund it with a native transfer before deploying. Eoonia Wallet does this automatically.

## What has been verified

- Runtime 211 made the EVM accept real transactions; 213+ run on the public testnet.
- 43 of 43 Creator Studio contracts (tokens, vaults, escrow, subscriptions, an ERC-4337 EntryPoint v0.6) deployed in block from Eoonia against runtime 220; the whole matrix paid 0.0664 DMS in gas.
- Signing with the wrong chain id (a common template bug) produces a signature valid on Ethereum mainnet — always sign with 2026.

## Tooling

Hardhat and Foundry work with a custom network entry. Verify deployments through EmpooScan once its indexer decodes the 220 metadata, or by reading the receipt from the RPC.

## Limits

Two validators, no audit, no mainnet. Throughput is not published. Contracts on the EVM do not see native pallets (DUSD balances, staking, compliance rules) except through precompiles.