# The Ethereum Virtual Machine: how different computers agree The Ethereum Virtual Machine, or EVM, defines how contract instructions execute and change Ethereum state. Given the same starting state, transaction and applicable rules, nodes should obtain the same result. Gas bounds resource consumption. The EVM is a set of execution rules, not a single physical computer or a guarantee of application safety. Evidence: [Ethereum Virtual Machine](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/evm/index.md); [Gas and fees](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/gas/index.md); [Introduction to smart contracts](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/smart-contracts/index.md) Canonical: https://degreesofsatoshi.com/encyclopedia/ethereum-virtual-machine/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T15:10:23.134Z AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Determinism:** The same inputs and rules produce the same execution result ([Ethereum Virtual Machine](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/evm/index.md)) - **Persistent data:** Contract storage survives between transactions ([Ethereum Virtual Machine](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/evm/index.md)) - **Work budget:** Gas meters execution resources ([Gas and fees](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/gas/index.md)) ## Agreement depends on identical rules rather than one central machine Ethereum nodes run execution-client software. Their EVM implementations must agree about what each instruction does, how it affects state and what resources it consumes. Different software implementations can implement the same protocol. This is why an upgrade is more than a website release. Changing execution rules requires the network’s participants to follow compatible rules; otherwise they can disagree about the result of a block. Evidence: [Ethereum Virtual Machine](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/evm/index.md); [Nodes and clients](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/nodes-and-clients/index.md) ## Example: three increments change stored state from five to eight Imagine a contract storing the number five and exposing an increment function. Three successful calls, each adding one, leave the persistent value at eight. Every validating execution reaches that result from the same ordered inputs. Temporary working data used during a call is not the same as the stored counter. The EVM distinguishes execution memory, transaction-scoped transient storage and persistent contract storage, each with different lifetimes. Evidence: [Ethereum Virtual Machine](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/evm/index.md); [Introduction to smart contracts](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/smart-contracts/index.md) ## A finite budget makes arbitrary programs practical to check Programs may loop or perform expensive work. Gas charges for operations and bounds execution by a supplied budget. Without a resource mechanism, a small request could demand unbounded work from other participants. If execution runs out of gas, it fails rather than continuing forever. That failure does not imply zero cost: computation already performed has consumed resources, and the transaction can still have a fee. Evidence: [Gas and fees](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/gas/index.md); [Ethereum Virtual Machine](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/evm/index.md) ## Compatible execution does not mean identical security An EVM-compatible chain aims to support familiar contract execution and tooling. It may nevertheless use different consensus, data availability, upgrade controls or fee rules. Familiar software does not collapse those differences. A program can also execute exactly as written while containing a logic error. Determinism makes results repeatable; it cannot establish that the program implements the promise a user thought they were accepting. Evidence: [Scaling overview](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/index.md); [Ethereum Virtual Machine](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/evm/index.md) ## Questions ### Is the EVM a computer owned by Ethereum? No. Many computers run implementations of shared execution rules. The virtual-machine description refers to those rules and their state transitions. Evidence: [Ethereum Virtual Machine](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/evm/index.md); [Nodes and clients](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/nodes-and-clients/index.md) ### Can EVM execution read a random website? Not directly during ordinary consensus execution. Uncontrolled external responses could differ between nodes, so external facts must enter through explicit inputs. Evidence: [Introduction to smart contracts](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/smart-contracts/index.md); [Ethereum Virtual Machine](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/evm/index.md) ### Are all EVM chains the same network? No. Compatible execution can exist on independent chains with different security and settlement arrangements, including sidechains. Evidence: [Scaling overview](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/index.md) ## Claims and scope ### ethereum-virtual-machine-quick-answer The Ethereum Virtual Machine, or EVM, defines how contract instructions execute and change Ethereum state. Given the same starting state, transaction and applicable rules, nodes should obtain the same result. Gas bounds resource consumption. The EVM is a set of execution rules, not a single physical computer or a guarantee of application safety. Scope: {"collection":"ethereum","dataAsOf":null,"blockHeight":null} ### ethereum-virtual-machine-fact-determinism Determinism: The same inputs and rules produce the same execution result Scope: {"collection":"ethereum","dataAsOf":null,"blockHeight":null} ### ethereum-virtual-machine-fact-persistent-data Persistent data: Contract storage survives between transactions Scope: {"collection":"ethereum","dataAsOf":null,"blockHeight":null} ### ethereum-virtual-machine-fact-work-budget Work budget: Gas meters execution resources Scope: {"collection":"ethereum","dataAsOf":null,"blockHeight":null} ## Sources - [Ethereum Virtual Machine](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/evm/index.md) — ethereum.org contributors. Supports deterministic execution, opcodes and the distinction between temporary execution memory and persistent state. Locator: State transition function; EVM instructions; storage. Retrieved: 2026-10-02T14:35:40.399163+00:00. - [Gas and fees](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/gas/index.md) — ethereum.org contributors. Supports gas units, ETH/gwei units, base/priority fees, resource limits and charges for executed failed transactions. Locator: How are gas fees calculated; base fee; gas limit. Retrieved: 2026-10-02T14:35:40.393022+00:00. - [Introduction to smart contracts](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/smart-contracts/index.md) — ethereum.org contributors. Supports contract code/state, deterministic rules, illustrative vending logic, external-data limits and multisignature access. Locator: What is a smart contract; a digital vending machine; limitations; multisig. Retrieved: 2026-10-02T14:35:40.398357+00:00. - [Nodes and clients](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/nodes-and-clients/index.md) — ethereum.org contributors. Supports execution/consensus client roles, independent validation, RPC services and node-versus-validator distinctions. Locator: What are nodes and clients; benefits to you; alternatives. Retrieved: 2026-10-02T14:35:47.541421+00:00. - [Scaling overview](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/index.md) — ethereum.org contributors. Supports rollup execution/settlement roles and distinct security assumptions of sidechains and offchain data systems. Locator: Layer 2 scaling; rollups; sidechains; validium. Retrieved: 2026-10-02T14:35:47.354550+00:00. ## Revision history - 2026-10-02: First publication after primary-source research and independent automated verification. ## Cite this entry Degrees of Satoshi editorial project. “The Ethereum Virtual Machine: how different computers agree.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/ethereum-virtual-machine/