Crypto Gloss

EVM

The Ethereum Virtual Machine (EVM) is the runtime environment in which all Ethereum smart contracts execute. It is a stack-based, quasi-Turing-complete virtual machine that runs on every Ethereum node simultaneously. When you call a smart contract — depositing into Aave, minting an NFT, swapping tokens on Uniswap — the EVM is what executes that code.

Why the EVM Matters

Before Ethereum, blockchains were application-specific (Bitcoin handles BTC transfers; Litecoin handles LTC transfers). The EVM made Ethereum a general-purpose computing platform: any logic that can be expressed in code can run on the EVM, secured by Ethereum’s decentralized network. This is what enabled DeFi, NFTs, DAOs, and every other Ethereum application.

How the EVM Works

Stack-based machine: EVM maintains a stack of 256-bit words (not registers like most CPUs). Instructions push and pop values from the stack.

Execution environment components:

  • Stack — computation space (max 1,024 items deep)
  • Memory — temporary byte-array, fresh on each call
  • Storage — persistent key-value store on the blockchain (expensive)
  • Calldata — read-only input data for function calls
  • Code — the smart contract’s bytecode

Determinism: Every node running the same bytecode with the same input must produce identical output. This is what makes trustless consensus possible.

Gas and the EVM

Every EVM operation costs gas — a unit measuring computational work. Simple operations (ADD, MUL) cost 3 gas; expensive operations (SSTORE — write to persistent storage) cost hundreds. Gas prevents infinite loops and spam: every transaction has a gas limit, and if execution runs out of gas, the transaction reverts (but gas is consumed up to that point).

Gas also prices computation dynamically — high network demand raises the gas price (in ETH), throttling usage organically.

The Smart Contract Lifecycle

  1. Developer writes code in Solidity or Vyper
  2. Code is compiled to EVM bytecode (a binary format)
  3. Bytecode is deployed to Ethereum in a transaction → gets a unique contract address
  4. Users call the contract by sending transactions to that address
  5. All nodes run the bytecode through the EVM
  6. Consensus ensures all nodes agree on the result

EVM Opcodes

The EVM understands ~140 opcodes — primitive operations in its assembly language. Examples:

  • PUSH1 — push 1 byte onto stack
  • ADD — add top two stack items
  • SLOAD / SSTORE — read/write persistent storage
  • CALL — call another contract
  • DELEGATECALL — call another contract using caller’s storage (basis of proxy patterns)
  • CREATE / CREATE2 — deploy new contracts

EVM Compatibility Ecosystem

The EVM’s design became an industry standard. Hundreds of chains run EVM-compatible environments, allowing developers to deploy the same Solidity code across multiple networks:

Chain EVM Status
Polygon EVM-compatible
Arbitrum EVM-equivalent
Optimism EVM-equivalent
Base EVM-equivalent
BNB Chain EVM-compatible
Avalanche C-Chain EVM-compatible
Fantom EVM-compatible
Linea zkEVM
Scroll zkEVM

EVM-compatible = mostly compatible, may have minor differences

EVM-equivalent = bit-for-bit identical behavior

Limitations of the EVM

  • 256-bit word size — Mismatched to modern 64-bit CPUs; many operations require conversion overhead
  • Sequential execution — No native parallelism; transactions execute one at a time (unlike Solana’s parallel execution)
  • Gas model complexity — Volatile gas costs create UX friction
  • Persistent storage cost — Writing to the blockchain is expensive; incentivizes minimizing on-chain state

The EOF (EVM Object Format) upgrade and EVMMAX are active research areas to modernize the EVM without breaking compatibility.

Social Media Sentiment

The EVM is the foundation of “Ethereum culture” — developer communities on r/ethdev, Discord servers for Solidity, and Ethereum research forums. “EVM-compatible” has become a marketing term, with chains advertising it to attract Ethereum developers. There is active debate about whether the EVM’s design should be replaced (ZK-friendly VMs like Cairo have fundamentally different architectures) or preserved for compatibility.

Last updated: 2026-04

Related Terms

Sources

  • Wood, G. (2014). Ethereum: A Secure Decentralised Generalised Transaction Ledger (Yellow Paper). Ethereum Foundation.
  • Antonopoulos, A. M., & Wood, G. (2018). Mastering Ethereum. O’Reilly Media.
  • Buterin, V. (2023). EVM Object Format (EOF) Overview. Ethereum Foundation Blog.