Crypto glossary
EVM equivalence vs compatibility
EVM equivalence means a chain runs Ethereum code exactly like Ethereum; EVM compatibility means it supports Solidity and tools, but with differences.
Many blockchains advertise support for the Ethereum Virtual Machine, but the degree varies. An EVM-compatible chain accepts Solidity contracts and works with wallets like MetaMask, yet may differ in opcodes, precompiled contracts, gas costs or how it handles certain edge cases. An EVM-equivalent chain follows the Ethereum specification closely enough that contracts, developer tools and even client software behave identically. For zero-knowledge rollups, Vitalik Buterin proposed a scale from Type 1, fully Ethereum-equivalent, to Type 4, which only compiles high-level languages to a different VM.
The distinction matters to developers who want to deploy existing, audited code without changes, and to protocols that depend on exact behaviour, such as gas-sensitive logic or precompiles. Optimistic rollups made equivalence a selling point, and zkEVMs have moved closer to it as proving technology improved.
Labels are often used loosely in marketing. Compatible chains can break contracts in subtle ways, and even equivalent ones may lag behind new Ethereum upgrades. Developers should test on the target chain rather than trust the label.
Example
A protocol redeploys its audited lending contracts on an EVM-equivalent rollup unchanged, but has to rewrite parts of its code for a chain that is only EVM-compatible.