What Is Ethereum? How the Platform Actually Works
A complete guide to Ethereum, ETH, the EVM, smart contracts, proof of stake, gas, and layer-2 rollups.
The short answer
Ethereum is a public blockchain network that operates as a shared state machine. Users submit signed transactions; validators order them into blocks; every validating node executes the same rules; and the Ethereum Virtual Machine updates accounts and smart-contract state. Ether, usually written ETH, is the network's native asset—not another name for the entire platform.134
Ethereum has used proof-of-stake consensus since the Merge on September 15, 2022. A node runs separate execution and consensus clients, while a validator adds signing duties and staked ETH. Most scaling now happens through layer-2 rollups that execute transactions outside Mainnet and use Ethereum for data or verification according to the rollup's design.86712
Key findings
- 01
Ethereum is a stack
The protocol, Mainnet, EVM, clients, validators, ETH, contracts, applications, and rollups are related components with different responsibilities.
- 02
Computation has a metered cost
Gas measures work performed by the EVM; users pay gas fees in ETH even when an application uses other tokens.
- 03
Layer 2 adds another system
A rollup can inherit parts of Ethereum's security while adding its own sequencer, proof, upgrade, bridge, and data-availability assumptions.
Ethereum is the network; ether is the native asset
Ethereum is an execution and settlement platform maintained by a peer-to-peer network. Its shared state records account balances, deployed contract code, and contract storage. A transaction asks the network to move ETH, deploy code, or call an existing contract; nodes independently verify the resulting state transition under the same protocol rules.134
Ether (ETH) has several protocol roles. It pays for computation, serves as the stake securing proof-of-stake consensus, and transfers value between accounts. Applications may also use ETH as collateral or a unit of account, but those application-level uses are separate from its required protocol roles.1097
Tokens such as ERC-20 assets are smart-contract records on Ethereum rather than native balances implemented exactly like ETH. A wallet may show both in one interface, but moving an ERC-20 token calls a token contract and normally still requires ETH for gas. This difference explains why holding a token does not automatically provide the ETH needed to transact with it.1195
| Component | What it is | What it is not |
|---|---|---|
| Ethereum Mainnet | The canonical public network and its shared state | A company, wallet, or exchange1 |
| ETH / ether | Native asset used for fees, staking, and value transfer | The protocol itself or an ERC-20 token10 |
| EVM | The deterministic execution environment for contract bytecode | A wallet or a consensus algorithm4 |
| Smart contract | Code and state deployed to a contract account | Automatically a legally enforceable contract5 |
| Wallet | Software or hardware used to manage accounts and sign messages | The place where on-chain assets physically reside2 |
| Layer-2 rollup | A separate execution system anchored to Ethereum in a defined way | The same thing as Ethereum Mainnet12 |
What happens when an Ethereum transaction is sent
Ethereum has externally owned accounts, controlled through private keys, and contract accounts, controlled by code. Both can hold ETH and tokens, but only an externally owned account directly initiates a protocol transaction. A contract acts when a transaction or another contract call reaches it. Wallet software is an interface to an account; it is not the account itself.2
A transaction includes a destination, nonce, value, optional input data, gas limit, fee parameters, and a cryptographic signature. The nonce orders transactions from one account and prevents the same signed instruction from being executed repeatedly. Calling a contract places encoded function data in the transaction; deploying a contract submits creation bytecode without an ordinary destination address.3
After broadcast, execution clients validate the transaction and may hold it in a mempool. A block proposer selects transactions and builds an execution payload. Other nodes re-execute the payload, verify signatures and state changes, and reject a block that violates the protocol. Inclusion is not the same as finality: consensus votes make a checkpoint finalized after the proof-of-stake supermajority conditions are met.367
1. Sign
The account's private key authorizes a specific transaction; the key should never be disclosed to the application or network.23
2. Broadcast
A wallet or node sends the transaction to peers, where valid pending transactions can enter local mempools.3
3. Execute
A proposer includes it in a block and the EVM applies its operations against the pre-transaction state.47
4. Verify
Other nodes independently reproduce the computation and confirm that the block follows execution and consensus rules.67
5. Finalize
Validator attestations create a supermajority link between checkpoints, making a reversion economically and protocolically exceptional.7
The EVM and smart contracts
The EVM is the virtual environment that every execution client implements. Contract source code—commonly Solidity or Vyper—is compiled to bytecode, deployed to an address, and executed as EVM instructions. Because validating nodes must reach the same result, contract execution is deterministic and cannot directly make an ordinary web request or depend on a node's local clock or private database.45
A smart contract combines functions with persistent state. Once deployed, users and other contracts can call its public interface. Contracts are composable: one contract can invoke another, allowing applications to combine token, exchange, lending, governance, and identity components. The same composability can spread risk when a dependency fails or changes.5
A contract cannot natively know an exchange rate, delivery result, court decision, or weather event. An oracle brings off-chain information on-chain, adding its own data sources, operators, incentives, and failure modes. Likewise, an upgradeable proxy or administrator key can change application behavior even though old blocks remain in Ethereum's history. 'On-chain' therefore does not automatically mean autonomous, immutable, or free of trusted parties.51617
| Property | What Ethereum provides | What the application must provide |
|---|---|---|
| Execution | Deterministic EVM rules and replicated verification | Correct, tested contract logic4 |
| Authorization | Signature and account primitives | Safe key management and access-control design217 |
| External facts | No native access to off-chain data | An oracle or human adjudication process16 |
| Upgrade policy | History and current state | Transparent admin, delay, multisig, or immutable-code choices17 |
How proof of stake secures Ethereum
The Merge joined Ethereum's existing execution layer with the Beacon Chain's proof-of-stake consensus and completed on September 15, 2022. It changed block production and finality; it did not replace ETH, erase transaction history, or make every application a new version. The original proof-of-work mechanism is no longer used on Ethereum Mainnet.8
A full Ethereum node runs an execution client and a consensus client. Adding validator software and a protocol deposit allows the operator to propose blocks and attest to others. Time is divided into 12-second slots and 32-slot epochs; a proposer is selected for a slot, while committees of validators attest to the chain they consider valid.67
A solo validator requires at least 32 ETH. Honest participation earns protocol rewards; downtime misses rewards and can incur smaller penalties; provably conflicting votes or blocks can trigger slashing and forced exit. Pools and liquid-staking products let users participate with less, but they are additional applications or custodial relationships with smart-contract, operator, liquidity, governance, and concentration risks.718
| Role | Software or asset | Responsibility |
|---|---|---|
| Execution client | Geth, Nethermind, Besu, Erigon, or another implementation | Validate transactions, execute the EVM, and maintain execution state6 |
| Consensus client | A Beacon-node implementation | Track proof-of-stake blocks, attestations, fork choice, and finality6 |
| Validator | Validator keys, duties, and staked ETH | Propose blocks when selected and attest to valid chain state7 |
| Non-validating node | Execution and consensus clients without validator duties | Independently verify the chain without proposing or attesting6 |
Gas measures computation; the fee pays for scarce block space
Gas is a unit of computational effort, not a separate token. Each EVM operation has a gas cost, and the transaction's gas limit caps how much work it may consume. The sender pays the fee in ETH whether the transaction succeeds or reverts, because validators still performed the attempted computation. Unused gas is not charged.9
For ordinary EIP-1559 transactions, the protocol sets a base fee and the sender may add a priority fee. The base fee is burned; the priority fee incentivizes the proposer to include the transaction. Wallets also set a maximum fee so users can bound their exposure while receiving any unused difference back under the fee rules.93
Fees rise when demand for block space is high, so a simple token price does not predict transaction cost. Contract complexity, storage writes, calldata, current base fee, and urgency all matter. A failed slippage check can therefore preserve the user's tokens while still consuming gas. Layer-2 networks often reduce user fees by batching activity, but their fee markets and withdrawal costs are separate.912
Ethereum's scaling strategy is rollup-centric
A rollup executes many transactions outside Ethereum Mainnet, compresses the result, and posts data or proofs back to Ethereum. Optimistic rollups assume state updates are valid unless challenged during a dispute window; zero-knowledge rollups submit validity proofs that Ethereum contracts verify. Both reduce Mainnet work per user transaction, but they do so with different proof systems and exit behavior.1213
Ethereum's Dencun upgrade introduced blob transactions in March 2024 so rollups could publish temporary data more cheaply than permanent calldata. Blobs improve data availability economics; they do not execute rollup transactions inside the EVM. The broader roadmap increases blob capacity and verification efficiency rather than returning to the abandoned plan for separate execution shard chains.1412
A layer 2 is not automatically as trust-minimized as Ethereum itself. Users should inspect whether a sequencer can censor or reorder transactions, whether proofs are active, who controls upgrades, how forced exits work, where data is available, and what bridge holds or releases assets. Sidechains and validiums can be useful, but their security or data assumptions differ from rollups that publish data to Ethereum.1215
| System | Execution | Data / verification | Main additional assumptions |
|---|---|---|---|
| Ethereum Mainnet | All validating execution clients | Mainnet consensus and full execution | Ethereum client, validator, and protocol assumptions67 |
| Optimistic rollup | Off-chain rollup system | Data on Ethereum; disputed updates use fraud proofs | Sequencer, challenge window, proof and upgrade design12 |
| ZK rollup | Off-chain rollup system | Validity proof verified by an Ethereum contract | Prover, circuit, data availability, sequencer, and upgrade design13 |
| Sidechain | Independent chain | Its own consensus; bridge connects assets | Independent validator set and bridge security1215 |
A practical risk checklist
Key and signature risk
A valid signature can authorize an irreversible transfer, token approval, or contract action. Verify the chain, destination, requested permissions, and wallet display before signing.23
Contract risk
Code can contain logic errors, unsafe external calls, broken access control, or economic assumptions that fail even when the EVM behaves correctly.17
Administrator and governance risk
Upgradeable contracts, pause functions, multisignatures, and governance votes can alter or stop an application. Read the actual control path and any execution delay.17
Oracle risk
A lending, derivatives, escrow, or stablecoin contract can execute perfectly against stale or manipulated external data.1617
Bridge and layer-2 risk
Moving an asset to another network usually adds custody, proof, messaging, sequencer, and upgrade assumptions beyond the original token contract.1512
Asset and counterparty risk
Ethereum settlement does not guarantee that a token is redeemable, solvent, legal, fairly priced, or backed by the assets its issuer claims.
Frequently asked questions
Concise answers to the questions readers most often ask about this topic.
Is Ethereum the same as ETH?
Does Ethereum still use mining?
What is gas, and why is it paid in ETH?
Can a smart contract be changed or deleted?
Is a layer 2 part of Ethereum?
Methodology
This guide prioritizes current Ethereum protocol and developer documentation for architecture, then uses dated Ethereum Foundation records for major historical changes such as the Merge. It avoids live throughput, fee, validator, and market-share figures because those require timestamped datasets rather than evergreen prose.1678912
CryptoDigest first covered Ethereum in 2018. This independently written edition replaces the unavailable historical text and explicitly separates enduring concepts from architecture introduced after that date.
Limitations
- Ethereum changes through network upgrades; client documentation and the live protocol take precedence over this guide.
- The page explains common rollup categories but does not assess any particular layer-2 network, bridge, wallet, staking provider, or application.
- Security properties depend on implementation and configuration as well as the base protocol.
- This is technical education, not investment, legal, tax, or operational advice.
Sources and evidence
Claims are linked to the technical documentation, standards, law, research, and enforcement records that support them.
- 1Technical introduction to Ethereum ↗
ethereum.org · Protocol education
Supports: Shared state machine, EVM, and application model - 2Ethereum accounts ↗
ethereum.org · Developer documentation
Supports: Externally owned and contract accounts, keys, nonces, and wallets - 3Transactions ↗
ethereum.org · Developer documentation
Supports: Transaction fields, signatures, fees, and typed transactions - 4Ethereum Virtual Machine ↗
ethereum.org · Developer documentation
Supports: Deterministic execution, bytecode, memory, storage, and opcodes - 5Introduction to smart contracts ↗
ethereum.org · Developer documentation
Supports: Contract accounts, deployment, composability, and limitations - 6Nodes and clients ↗
ethereum.org · Node documentation
Supports: Execution clients, consensus clients, and validator software - 7Proof of stake ↗
ethereum.org · Consensus documentation
Supports: Validator deposits, slots, epochs, attestations, penalties, and finality - 8The Merge ↗
ethereum.org · Protocol history
Supports: September 2022 transition from proof of work to proof of stake - 9Ethereum gas and fees ↗
ethereum.org · Developer documentation
Supports: Gas, base fees, priority fees, limits, refunds, and burning - 10Technical introduction to ether ↗
ethereum.org · Protocol education
Supports: ETH roles, denominations, gas, staking, and transfers - 11ERC-20 token standard ↗
ethereum.org · Token-standard documentation
Supports: Fungible token contracts and their interface - 12Scaling Ethereum ↗
ethereum.org · Protocol documentation
Supports: Rollups, sidechains, validiums, and the rollup-centric roadmap - 13Zero-knowledge rollups ↗
ethereum.org · Layer-2 documentation
Supports: Validity proofs, off-chain execution, data, and exits - 14Scaling Ethereum roadmap ↗
ethereum.org · Protocol roadmap
Supports: Dencun blobs and current rollup scaling direction - 15Blockchain bridges and their risks ↗
ethereum.org · Developer documentation
Supports: Smart-contract, systemic, and counterparty bridge risks - 16Oracles ↗
ethereum.org · Developer documentation
Supports: Off-chain inputs and oracle trust assumptions - 17Smart contract security ↗
ethereum.org · Security guidance
Supports: Access control, oracle manipulation, upgrades, and contract risk - 18Ethereum staking ↗
ethereum.org · Consensus education
Supports: Solo staking, pooling, rewards, penalties, and added trust layers
Cite this resource
Stable edition 2026.08.27
Version history
- 2026.08.27
Full editorial rebuild with claim-level citations, current primary sources, tables, and reader FAQs.
- 2026.08.26
Initial source-backed guide edition published.
- Earlier coverage
CryptoDigest previously covered this topic; the original article text is unavailable.