TECHNOLOGIES

What is EVM (Ethereum Virtual Machine)?

Ethereum Virtual Machine

The runtime that executes smart contracts on Ethereum and the dozens of chains that copied its bytecode format.

Last reviewed: byKevin Riedl wiki ↗

The EVM is the execution layer Ethereum invented and that became the de-facto standard for smart-contract chains. A contract compiled to EVM bytecode runs on Ethereum mainnet, Polygon, Arbitrum, Optimism, Base, BNB Chain, Avalanche C-chain, and a long tail of L2s and sidechains.

The practical implication: write your contracts in Solidity (or Vyper), test on Ethereum testnets, and deploy to whichever EVM chain matches your cost and latency target. The portability is real. The trade-offs between chains are speed, finality, decentralisation, and which L2 framework they are built on.

Choose an EVM deployment by workload, liquidity, user access and operational safeguards. A rollup can reduce fees while relying on Ethereum settlement, but its sequencer, proof system, upgrade powers, data availability and withdrawal path add deployment-specific assumptions. Measure the actual transactions rather than promising the same mainnet security or a fixed tenfold or hundredfold discount.

The honest trade-off and the mistake that catches teams repeatedly: EVM-compatible is not the same as Ethereum-equivalent. Subtle differences in gas pricing, precompiles, opcode support, and consensus behaviour mean a contract that passes on mainnet can break on a sidechain. The portability is a starting point, not a guarantee; always re-test per chain before deploying. Account-level UX features like account abstraction also vary in maturity across chains, so confirm support before you promise it.

Lifecycle matters as much as bytecode compatibility. Polygon confirms that its zkEVM Mainnet Beta sequencer was sunset on 3 July 2026. It is not a current target for a new application. This does not mean Polygon PoS or every chain built with Polygon tooling was shut down. Check the exact network and supported exit process before committing funds or planning a migration.

Related terms

// FAQ

FAQs

Test the target chain’s opcode and precompile support, gas rules, finality, infrastructure and deployment tooling. EVM compatibility is a starting point, not a guarantee that a contract behaves identically everywhere.
Choose by the exact deployment’s security controls, liquidity, user access, complete transaction costs and exit path. Do not recommend the retired Polygon zkEVM Mainnet Beta for a new build.
Solidity and Vyper have different language designs and ecosystems. Choose for the team’s expertise, maintained tooling and auditor support, then test the exact compiler and contract behavior. Neither language guarantees secure code.