Encyclopedia Ethereum · Entry 08
The Ethereum Virtual Machine: how different computers agree
In this article
At a glance
Key facts
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.
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.
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.
Direct answers
Questions people ask
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.
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.
Are all EVM chains the same network?
No. Compatible execution can exist on independent chains with different security and settlement arrangements, including sidechains.
Inspect the evidence
The answer and key facts have stable claim links. These records retain the scope and qualification when reused.
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: Ethereum. Verification: verified · 2026-10-02T15:10:23.134Z.
Link to this claimDeterminism: The same inputs and rules produce the same execution result
Scope: Ethereum. Verification: verified · 2026-10-02T15:10:23.134Z.
Link to this claimPersistent data: Contract storage survives between transactions
Scope: Ethereum. Verification: verified · 2026-10-02T15:10:23.134Z.
Link to this claimWork budget: Gas meters execution resources
Scope: Ethereum. Verification: verified · 2026-10-02T15:10:23.134Z.
Link to this claimRevision history
- — First publication after primary-source research and independent automated verification.
Source register
Sources and references
Retrieval dates and locators are recorded individually.- Ethereum Virtual Machineethereum.org contributors
Supports deterministic execution, opcodes and the distinction between temporary execution memory and persistent state.
Locator: State transition function; EVM instructions; storage · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:40.399163+00:00Open source - Gas and feesethereum.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 · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:40.393022+00:00Open source - Introduction to smart contractsethereum.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 · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:40.398357+00:00Open source - Nodes and clientsethereum.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 · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:47.541421+00:00Open source - Scaling overviewethereum.org contributors
Supports rollup execution/settlement roles and distinct security assumptions of sidechains and offchain data systems.
Locator: Layer 2 scaling; rollups; sidechains; validium · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:47.354550+00:00Open source
Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.
Editorial method and correctionsDegrees 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/