Chapter 2: Ethereum

Overview

Ethereum is far more than a cryptocurrency — it is a programmable blockchain platform that forms the foundational infrastructure of modern decentralized finance (DeFi) and the broader Web3 ecosystem. While Bitcoin focuses on store of value and peer-to-peer payments, Ethereum was designed with a far more expansive ambition: to serve as a "World Computer" capable of executing arbitrary logic on a blockchain. At the heart of this vision are Smart Contracts and the Ethereum Virtual Machine (EVM), which together enable a vast ecosystem of decentralized applications (dApps).

This chapter systematically explores the core technical concepts that make Ethereum work. Beginning with the EVM as the execution environment, we progress through the fee structure (Gas, EIP-1559), the consensus mechanism (Proof of Stake, The Merge), token standards (ERC-20), and scalability solutions (Rollup, Blob Transactions) — covering 19 foundational concepts that define the Ethereum stack. These concepts are deeply interconnected: understanding one consistently deepens your comprehension of the others.

Since its launch in 2015, Ethereum has evolved through a continuous series of upgrades. The transition to Proof of Stake (PoS) via The Merge in 2022, followed by the introduction of Blob Transactions through the Dencun upgrade in 2024, represent landmark milestones in Ethereum's ongoing pursuit of three simultaneous goals: scalability, security, and sustainability. By the end of this chapter, readers will have a thorough understanding of Ethereum's technical foundations and a clear sense of why the modern blockchain ecosystem has coalesced around Ethereum as its center of gravity.

---

Ethereum Virtual Machine (EVM)

Definition

The Ethereum Virtual Machine (EVM) is the stack-based computational engine that executes Smart Contract bytecode on the Ethereum network. It is a deterministic virtual computer designed so that thousands of nodes worldwide can simultaneously run the same code and arrive at exactly the same result. Smart contracts written in high-level languages like Solidity or Vyper are compiled down to low-level bytecode that the EVM can interpret and execute opcode by opcode.

Key Points

• Stack-Based Architecture: The EVM performs all computations using a stack rather than registers. Opcodes such as ADD, MULTIPLY, STORE, and CALL pop operands from the stack, perform the operation, and push the result back. The stack is capped at a maximum depth of 1,024 items.
• Guaranteed Deterministic Execution: Given identical inputs, every node anywhere in the world must produce identical outputs. To enforce this, the EVM categorically excludes non-deterministic elements such as floating-point arithmetic and external system calls. When a smart contract needs external data, that data must first be written on-chain via an oracle before the EVM can consume it.
• The De Facto Industry Standard: The EVM has proliferated far beyond Ethereum itself. Most major Layer 2 rollups — including Arbitrum, Optimism, Base, and zkSync — maintain EVM compatibility, as do numerous alternative Layer 1 blockchains such as BNB Chain, Polygon, Avalanche C-Chain, and Fantom. This widespread adoption stems from the powerful advantage of being able to reuse Ethereum's mature developer tooling, languages, and library ecosystem without modification.
• Sandboxed Execution Environment: The EVM runs in an isolated sandbox, meaning smart contract code cannot directly access the host system's filesystem, network, or memory. This isolation simultaneously strengthens security and underpins deterministic execution guarantees.
• Storage Model: Each contract maintains its own persistent storage structured as 256-bit key-value pairs. Reading from and writing to storage are computationally expensive operations and are therefore assigned relatively high Gas costs, incentivizing developers to minimize unnecessary state changes.

Related Concepts

Because the EVM is Ethereum's execution environment, it connects to virtually every other concept in this chapter. Most directly, Smart Contracts are the code that runs on the EVM, and Gas is the unit that measures the computational cost of executing each opcode. Rollups are scaling solutions that move EVM execution off Layer 1 while preserving EVM compatibility. The EVM's universal adoption also forms the technical bedrock that makes Composability possible across the Ethereum ecosystem.

---

Smart Contract

Definition

A Smart Contract is a self-executing program deployed on a blockchain that runs automatically when predefined conditions are met — with no intermediary required. Where traditional contracts depend on legal systems and trusted third parties for enforcement, a smart contract encodes its logic directly in code, records it immutably on-chain, and executes automatically when conditions are satisfied. Trust is replaced by code and mathematics. Once deployed, a smart contract's code is immutable and executes deterministically, always producing predictable outcomes.

Key Points

• Immutability and Deterministic Execution: Once a smart contract is deployed to the blockchain, its code cannot be arbitrarily modified or deleted. This provides powerful trust guarantees, but simultaneously makes bug remediation extremely difficult. Design patterns such as the upgradeable proxy pattern have emerged to address this limitation while preserving the core trust model.
• The Core Infrastructure of DeFi: Every DeFi application — decentralized exchanges (DEXs), lending protocols, stablecoin systems — is implemented as a smart contract. The automated market maker (AMM) logic of Uniswap, the collateralized lending rules of Aave, and the DAI minting mechanism of MakerDAO are all encoded directly in smart contract code.
• The Foundation of Tokens and NFTs: Both ERC-20 tokens and ERC-721 NFTs are implemented as smart contracts. Total supply, transfer rules, ownership tracking, and access controls are all defined within the contract code itself.
• Security Vulnerability Risks: Because code is law, bugs in smart contracts can have catastrophic consequences. The 2016 DAO hack ($60 million lost) and the 2021 Poly Network hack ($600 million compromised) illustrate the critical importance of rigorous smart contract security audits. Well-known vulnerability classes include reentrancy attacks, integer overflows, and access control flaws.
• Solidity and the Developer Ecosystem: Solidity is the dominant smart contract development language on Ethereum, with Vyper serving as a popular alternative. Development frameworks such as Hardhat and Foundry, alongside battle-tested libraries like OpenZeppelin, form a rich ecosystem that supports secure and efficient contract development.

Related Concepts

Smart contracts execute on the EVM and consume Gas with every operation. The ERC-20 token standard is one of the most widely deployed smart contract interfaces. Composability arises directly from the ability of smart contracts to call one another within the same atomic transaction. Account Abstraction is an effort to extend smart contract capabilities to ordinary user accounts, blurring the line between the two account types.

---

Gas

Definition

Gas is the abstract unit that measures the amount of computational work required to execute operations on the Ethereum network. Every Ethereum transaction must pay a Gas cost proportional to the computational resources it consumes. Gas serves two essential functions: it provides economic compensation to node operators and validators for supplying computational resources, and it prevents spam and denial-of-service (DoS) attacks by making it prohibitively expensive to flood the network with computationally intensive operations such as infinite loops. Gas prices are denominated in gwei, where 1 gwei equals one-billionth of an ETH (0.000000001 ETH).

Key Points

• Wide Variance in Gas Costs: The Gas consumed by a transaction varies enormously depending on its complexity. A simple ETH transfer costs a flat 21,000 Gas, while a complex DeFi transaction — such as a multi-hop token swap — can require hundreds of thousands to millions of Gas. Deploying a new smart contract to the blockchain is also a Gas-intensive operation.
• Gas Limit: Users set a Gas limit on each transaction, defining the maximum amount of Gas they are willing to consume. If the transaction completes within that limit, only the Gas actually used is charged and unused Gas is refunded. However, if execution runs out of Gas before completing, all state changes are reverted — and the Gas spent up to that point is not refunded.
• Block Gas Limit: Each Ethereum block has a maximum total Gas capacity, known as the block Gas limit, which bounds how many transactions can be included per block and ensures that nodes can process blocks within a reasonable time frame. This limit adjusts dynamically in response to network conditions.
• Per-Opcode Gas Pricing: Every EVM opcode carries a Gas cost calibrated to the computational resources it requires. For example, an ADD operation costs just 3 Gas, while an SSTORE (writing a new value to persistent storage) costs 20,000 Gas. This pricing structure creates strong incentives for developers to write Gas-efficient code.
• The Importance of Gas Optimization: Given Ethereum's historically high transaction costs, Gas optimization is a first-class concern for smart contract developers. Common techniques include using memory instead of storage for temporary variables, emitting events instead of storing data on-chain, and leveraging bitwise operations to reduce computational overhead.

Related Concepts

Gas measures the cost of executing each opcode within the EVM, and more complex Smart Contracts inherently consume more Gas. EIP-1559 fundamentally reformed the Gas pricing mechanism, introducing a dynamic base fee and burn model. Rollups dramatically reduce the effective Gas cost for end users by moving execution to Layer 2 and only settling compressed proofs or state roots on Layer 1.

---

EIP-1559

Definition

EIP-1559 (Ethereum Improvement Proposal 1559) is a fee mechanism reform introduced via the London hard fork in August 2021. It replaced the simple first-price auction model — where transactions bidding the highest gas price were processed first — with a dual-component structure consisting of a dynamically adjusted base fee and a user-specified priority fee (tip). The upgrade substantially improved fee predictability for users and introduced a base fee burn mechanism that has had profound implications for ETH's monetary policy.

Key Points

• Dynamic Base Fee: The base fee is set algorithmically by the protocol and adjusts automatically with each block by up to ±12.5%, depending on how full the previous block was relative to its target size. When blocks are consistently above the target, the base fee rises; when they fall below, it decreases. Users must pay at least the current base fee to have their transaction included, but estimating the correct amount to pay is now far more straightforward.
• Base Fee Burn (ETH Burn): Critically, the base fee is not paid to validators — it is permanently destroyed (burned). This represented a watershed moment in Ethereum's monetary history. The higher network utilization climbs, the more ETH is burned per block, exerting deflationary pressure on supply. When the burn rate exceeds the rate of new ETH issuance, ETH becomes a net deflationary asset — a dynamic that has been branded the "Ultra Sound Money" narrative by the Ethereum community.
• Priority Fee (Tip): The only portion of the transaction fee that actually reaches validators is the priority fee, or tip, set by the user. The tip serves as an incentive for validators to include a specific transaction in their proposed block. During periods of low network congestion, even a minimal tip is sufficient to achieve fast inclusion.
• Max Fee Per Gas: Users specify a maximum total fee they are willing to pay (maxFeePerGas). If the actual base fee at the time of inclusion is lower than this ceiling, the difference is refunded to the user. This design ensures users do not inadvertently overpay during sudden drops in network congestion.
• Improvements Over the Legacy Model: Prior to EIP-1559, users had to guess an appropriate gas price to bid in a blind first-price auction, often resulting in large overpayments during periods of congestion. The new mechanism dramatically improved the user experience by making fee estimation far more reliable and predictable.

Related Concepts

EIP-1559 is a reform layered on top of the Gas system and continues to operate in the post-Merge Proof of Stake environment, meaning ETH burning persists under PoS consensus. The ETH burn dynamic is directly relevant to the economics of Liquid Staking Tokens (LST), since the balance between staking rewards and burn-driven supply reduction determines ETH's effective real inflation rate.

---

The Merge

Definition

The Merge was the historic upgrade completed on September 15, 2022, in which Ethereum transitioned its consensus mechanism from Proof of Work (PoW) to Proof of Stake (PoS). The name derives from the literal merging of the Beacon Chain — a standalone PoS consensus chain that had been running in parallel since December 2020 — with Ethereum's existing execution layer. The upgrade reduced Ethereum's energy consumption by more than 99.9% and formally separated the network's architecture into a distinct Execution Layer and Consensus Layer.

Key Points

• Dramatic Reduction in Energy Consumption: Under Proof of Work, Ethereum mining consumed electricity comparable to that of a small nation. The transition to PoS eliminated over 99.9% of that energy usage, decisively addressing long-standing environmental criticisms of the network and lowering barriers to adoption among institutional investors and environmentally conscious users.
• Separation of Execution and Consensus Layers: The Merge restructured Ethereum into two independent but coordinated layers. The Execution Layer handles transaction processing and EVM execution, while the Consensus Layer (the Beacon Chain) manages validator coordination and block finalization. The two layers communicate via the Engine API. This modular architecture significantly increases the flexibility of future upgrades.
• Transaction Throughput Largely Unchanged: Contrary to a widespread misconception, The Merge itself did not materially increase transaction throughput or reduce fees. Block time decreased slightly from roughly 13 seconds to approximately 12 seconds, but fundamental capacity improvements depend on separate scaling solutions such as Rollups. The Merge was a consensus upgrade, not a scaling upgrade.
• End of Mining and the Rise of Validators: The Merge permanently ended Ethereum mining. GPU miners lost their role in the network entirely, replaced by validators who lock up ETH as collateral and earn rewards for proposing and attesting to blocks.
• The Most Complex Upgrade in Ethereum's History: The Merge was the product of years of research, development, and dozens of testnet rehearsals. Replacing the live consensus mechanism of a network securing hundreds of billions of dollars in assets without disruption was an unprecedented feat of distributed systems engineering.

Related Concepts

The Merge is the event that enacted the transition to Proof of Stake (PoS), and PoS-specific mechanisms such as Slashing and Finality became active features of Ethereum from that point forward. The combined effect of EIP-1559's burn mechanism and the reduced ETH issuance under PoS together define Ethereum's post-Merge monetary policy. Liquid Staking Tokens (LST) saw explosive growth in the wake of The Merge, as demand for accessible staking solutions surged.

---

Proof of Stake (PoS)

Definition

Proof of Stake (PoS) is the consensus mechanism Ethereum adopted following The Merge, in which validators earn the right to propose and validate blocks by locking up (staking) ETH as collateral. Participating as a validator requires a minimum stake of 32 ETH. Validators who behave honestly earn staking rewards, while those who violate consensus rules are punished via slashing, which can destroy a portion or all of their staked ETH. Ethereum's PoS implementation structures time into 12-second slots and epochs of 32 slots (approximately 6.4 minutes), providing a regular rhythm for block production and finalization.

Key Points

• Slots and Epochs: Time on Ethereum's PoS network is divided into 12-second slots. In each slot, one validator is pseudo-randomly selected as the block proposer. Thirty-two consecutive slots form an epoch (approximately 6.4 minutes), and it is at the epoch boundary that checkpoint justification and finality are processed.
• Validator Roles: Validators perform two core duties. A validator selected as the block proposer for a given slot constructs and broadcasts a new block. All other validators in that slot act as attesters, signing cryptographic attestations that confirm the proposed block is valid. These attestations accumulate to drive the justification and finalization of blocks.
• The 32 ETH Minimum: Operating a solo validator node requires a minimum of 32 ETH — a substantial capital commitment worth tens of thousands of dollars at prevailing prices. This high barrier to entry has driven the growth of Liquid Staking Token (LST) protocols and staking pools, which allow users to participate in staking with any amount of ETH.
• Validator Economics: Validators earn rewards for two activities: successfully proposing blocks and submitting timely attestations. A portion of the block reward also includes tips from users (per EIP-1559) and, in some cases, MEV (Maximal Extractable Value) captured through block ordering. Running a validator node also carries the risk of penalties for downtime (inactivity leaks) or protocol violations (slashing).
• Security via Economic Incentives: PoS achieves security through crypto-economic incentives rather than raw computational power. Attacking the network would require an adversary to acquire a majority of staked ETH, making such an attack enormously expensive to mount — and self-defeating, since a successful attack would collapse the value of the attacker's own stake.

Related Concepts

PoS is the consensus mechanism formalized by The Merge. Slashing is the enforcement mechanism that penalizes validator misbehavior and makes dishonest behavior economically irrational. Finality is the property that emerges from the aggregate weight of validator attestations across epochs. Liquid Staking Tokens (LST) exist precisely because the 32 ETH minimum creates a participation barrier that liquid staking protocols solve.

---

Slashing

Definition

Slashing is the punitive mechanism in Ethereum's Proof of Stake system that penalizes validators for behaviors that provably undermine network integrity. When a validator commits a slashable offense — such as signing two conflicting blocks for the same slot or attempting to vote for conflicting chain histories — a portion of their staked ETH is permanently destroyed, and they are forcibly ejected from the validator set. Slashing serves as the economic enforcement mechanism that makes dishonest behavior irrational for validators.

Key Points

• Slashable Offenses: There are two primary categories of slashable behavior. The first is double proposing (equivocation), where a validator proposes two different blocks for the same slot. The second is double voting (surround voting), where a validator signs contradictory attestations that could support conflicting chain histories. Both behaviors are detectable on-chain using cryptographic evidence.
• Penalty Structure: The immediate slashing penalty destroys at least 1/32 of the offending validator's staked ETH. The validator is then placed in a lengthy exit queue, typically lasting 36 days, during which they continue to accrue penalties. Additionally, a correlation penalty is applied: if many validators are slashed simultaneously (suggesting a coordinated attack), the penalty scales up proportionally, potentially destroying the validator's entire stake.
• Whistleblower Rewards: Any validator who submits evidence of a slashable offense to the network is rewarded with a small portion of the slashed ETH. This incentive structure crowd-sources the detection and reporting of misbehavior, making it practically impossible for violations to go unnoticed.
• Distinction from Inactivity Penalties: Slashing specifically targets provably malicious behavior. Validators who simply go offline and miss their attestation duties face a separate, milder penalty called an inactivity leak — a gradual reduction of their stake. This distinction ensures that honest validators who experience technical issues are not catastrophically penalized.
• Implications for Liquid Staking: Slashing risk is a critical consideration for Liquid Staking Token (LST) protocols. If the underlying validators managed by a liquid staking protocol are slashed, the value of the corresponding LST tokens decreases. Leading protocols like Lido mitigate this by distributing stake across a diverse set of professional node operators.

Related Concepts

Slashing is a core component of Proof of Stake (PoS) enforcement and was activated as part of The Merge. The slashing risk faced by validators is a key reason why Liquid Staking Tokens (LST) carefully curate their operator sets and implement insurance mechanisms. Restaking (EigenLayer) introduces additional slashing conditions by extending validator obligations to secure external protocols, compounding the risk exposure that validators must manage.

---

Finality

Definition

Finality is the property of a blockchain transaction or block whereby it can no longer be altered, reversed, or removed from the canonical chain. In Ethereum's Proof of Stake system, finality is achieved through a formal process in which a supermajority of validators (at least two-thirds of total staked ETH) attest to the validity of a checkpoint block. Once a block is finalized, reversing it would require an adversary to destroy at least one-third of all staked ETH — an economic cost so enormous as to be practically infeasible under normal conditions.

Key Points

• Checkpoint-Based Finalization: Ethereum PoS uses the Casper FFG (Friendly Finality Gadget) finality mechanism. At the end of each epoch, the last block is designated as a checkpoint. When a checkpoint receives attestations representing at least two-thirds of total staked ETH weight, it becomes "justified." When a subsequent epoch's checkpoint is justified while building on a justified checkpoint, both become "finalized." Under normal network conditions, finality is achieved approximately every two epochs, or roughly 12–15 minutes after a block is first proposed.
• Economic Finality vs. Probabilistic Finality: Ethereum PoS provides economic finality — a formal, cryptographically verifiable guarantee backed by the threat of slashing. This is qualitatively stronger than the probabilistic finality of Proof of Work systems, where transaction safety is a function of the number of subsequent blocks added (confirmations) but never reaches absolute certainty.
• The Role of the Inactivity Leak: If network participation drops so severely that no checkpoint can achieve a two-thirds supermajority — halting finality — Ethereum's protocol activates an inactivity leak. This mechanism gradually reduces the stake of inactive validators, shifting the supermajority threshold toward the actively participating minority until finality can resume. The inactivity leak prevents finality from being permanently stalled by validator dropouts.
• Finality and User Trust: For users and applications, finality represents the point at which a transaction can be treated as truly irreversible. Exchanges and financial applications often wait for finality before crediting deposits. Rollup systems that settle on Ethereum benefit from Ethereum's finality guarantees when anchoring their state roots to Layer 1.
• Single-Slot Finality (SSF) — Future Direction: The Ethereum research community is actively investigating Single-Slot Finality (SSF), which would achieve finality within a single 12-second slot rather than requiring multiple epochs. SSF would dramatically improve user experience and simplify protocol design, but requires significant changes to validator committee structures and signature aggregation schemes.

Related Concepts

Finality is a direct output of Proof of Stake (PoS) attestation aggregation and is intrinsically linked to Slashing — it is the threat of slashing that makes finality economically binding. Rollups inherit Ethereum's finality guarantees when they post their state commitments to Layer 1. Data Availability (DA) is a prerequisite for finality: validators cannot attest to a block whose data they cannot access and verify.

---

ERC-20

Definition

ERC-20 (Ethereum Request for Comments 20) is the technical standard that defines a common interface for fungible tokens on the Ethereum blockchain. Proposed by Fabian Vogelsteller in 2015 and formalized as an Ethereum standard, ERC-20 specifies a minimal set of functions and events that a token smart contract must implement, enabling seamless interoperability between tokens and the broader ecosystem of wallets, exchanges, and DeFi protocols. Virtually all fungible tokens on Ethereum — from stablecoins like USDC and DAI to governance tokens like UNI and AAVE — conform to the ERC-20 standard.

Key Points

• Standardized Interface: The ERC-20 standard mandates a specific set of functions: totalSupply() (returns the total token supply), balanceOf(address) (returns the token balance of an account), transfer(to, amount) (sends tokens from the caller to a recipient), approve(spender, amount) (authorizes a third party to spend tokens on the caller's behalf), and transferFrom(from, to, amount) (executes a transfer on behalf of an approved spender). This common interface means any ERC-20 token can be integrated into any compatible protocol without custom code.
• The Backbone of the Token Economy: The ERC-20 standard underpins an enormous portion of Ethereum's economic activity. Stablecoins (USDC, USDT, DAI), wrapped assets (WBTC), governance tokens, and liquidity provider (LP) tokens issued by DeFi protocols are all ERC-20 tokens. The standard's widespread adoption created the conditions for the explosive growth of DeFi during the 2020–2021 "DeFi Summer."
• The Approve-TransferFrom Pattern: A key design choice in ERC-20 is the two-step allowance mechanism. To enable a DeFi protocol (such as a DEX or lending platform) to spend tokens on a user's behalf, the user must first call approve() to grant an allowance. The protocol then calls transferFrom() to execute the transfer. While functionally effective, this pattern has historically been the source of security vulnerabilities — unlimited approvals, in particular, have led to significant user fund losses in phishing attacks and exploits.
• Known Limitations and Extensions: The ERC-20 standard has known limitations, including the absence of a callback mechanism when tokens are sent to a smart contract (leading to tokens being permanently locked in contracts that cannot handle them). Subsequent standards such as ERC-777 and ERC-4626 have been developed to address specific shortcomings, though ERC-20 remains the dominant standard by an overwhelming margin.
• ERC-721 and Beyond: ERC-20 defines fungible tokens, where every unit is identical. The ERC-721 standard, by contrast, defines non-fungible tokens (NFTs), where each token has a unique identity. The ERC-1155 standard supports both fungible and non-fungible tokens within a single contract, optimizing gas efficiency for applications such as gaming items.

Related Concepts

ERC-20 is a Smart Contract interface standard executed on the EVM. Every token transfer consumes Gas. The fungible token standard is a fundamental building block of Composability — because all ERC-20 tokens share a common interface, any DeFi protocol can interact with any ERC-20 token without bespoke integration. Liquid Staking Tokens (LST) such as stETH are themselves ERC-20 tokens.

---

Rollup

Definition

A Rollup is a Layer 2 scaling solution that executes transactions off the Ethereum mainnet, batches them together, and posts compressed transaction data or proofs back to Layer 1 as a single settlement. By processing computation off-chain while anchoring security to Ethereum's Layer 1, rollups achieve dramatically higher throughput and lower per-transaction costs than executing directly on mainnet, while inheriting Ethereum's security and decentralization guarantees. The two primary rollup paradigms are Optimistic Rollups and ZK Rollups, which differ in how they prove the validity of off-chain execution.

Key Points

• The Core Scaling Insight: The fundamental insight behind rollups is that not every computation needs to happen on Layer 1 — only the final settlement does. A rollup operator (the sequencer) collects thousands of user transactions, processes them off-chain, compresses the results, and submits a succinct state update to Layer 1. The cost of that single Layer 1 transaction is amortized across all bundled transactions, dramatically reducing the per-transaction fee.
• Ethereum as the Settlement and Data Layer: Rollups post their transaction data (or at minimum, state roots and proofs) to Ethereum Layer 1. This ensures that even if the rollup operator disappears, any party can reconstruct the rollup's full state from on-chain data and withdraw funds back to Layer 1. Ethereum's security, censorship resistance, and finality guarantees therefore extend to rollup users.
• Two Proof Paradigms: Optimistic Rollups assume transactions are valid by default and rely on fraud proofs submitted during a challenge window (typically 7 days) to detect and penalize invalid state transitions. ZK Rollups generate cryptographic validity proofs (ZK-SNARKs or ZK-STARKs) for every batch, enabling near-instant verification of correctness without any challenge period.
• The Rollup-Centric Roadmap: Ethereum's official scaling strategy, articulated by the research community since 2020, is explicitly rollup-centric. Rather than increasing mainnet throughput directly, Ethereum focuses on making Layer 1 an optimal settlement and data availability layer for rollups. This is the context for upgrades like EIP-4844 (Blob Transactions), which directly reduces the cost of posting rollup data to Layer 1.
• Leading Rollup Ecosystems: Arbitrum One and Arbitrum Nova (Optimistic Rollup), Optimism (Optimistic Rollup), Base (Optimistic Rollup built on the OP Stack), zkSync Era (ZK Rollup), and StarkNet (ZK Rollup) are among the most widely used rollups by transaction volume and total value locked (TVL). Each has developed its own ecosystem of protocols and applications.

Related Concepts

Rollups execute transactions in an EVM-compatible environment, inheriting Ethereum's developer tooling. The Sequencer is the centralized component of most rollup architectures responsible for ordering and batching transactions. Data Availability (DA) is critical for rollup security — rollup data must be available for users to verify state and exit if needed. EIP-4844 (Blob Transactions) significantly reduced the cost of rollup data posting. Optimistic Rollup and ZK Rollup are the two primary rollup implementations.

---

Optimistic Rollup

Definition

An Optimistic Rollup is a type of Layer 2 rollup that operates on the principle of optimistic execution: transactions are assumed to be valid by default and processed without immediate proof of correctness. Instead of generating cryptographic proofs for every batch, Optimistic Rollups rely on a dispute resolution mechanism — fraud proofs — to detect and correct invalid state transitions. Any party who believes a submitted state transition is fraudulent can challenge it during a defined challenge window, and if the challenge succeeds, the invalid state is reverted and the dishonest sequencer is penalized.

Key Points

• Optimistic Assumption and Fraud Proofs: The "optimistic" design assumes that submitted state roots are valid unless challenged. During the challenge period (typically 7 days on Arbitrum and Optimism), a challenger can submit a fraud proof that identifies the specific invalid opcode in the disputed transaction batch. If the fraud proof is verified on-chain, the invalid state root is rejected and the responsible sequencer loses their bonded collateral.
• The 7-Day Withdrawal Delay: The challenge window creates a significant UX friction: withdrawing funds from an Optimistic Rollup back to Ethereum Layer 1 requires waiting out the full challenge period (approximately 7 days) before the withdrawal is finalized. In practice, liquidity bridge services allow users to receive their funds on Layer 1 almost immediately in exchange for a small fee, with the bridge provider absorbing the waiting period risk.
• EVM Equivalence: Optimistic Rollups typically achieve a high degree of EVM equivalence, meaning smart contracts can be deployed on them with little to no modification. Arbitrum's ArbOS and Optimism's Bedrock architecture are both designed to be as close to EVM-equivalent as possible, allowing developers to port Ethereum contracts with minimal friction.
• Multi-Round vs. Single-Round Fraud Proofs: Fraud proof systems differ in implementation. Arbitrum uses an interactive, multi-round bisection protocol that narrows the dispute to a single opcode before requiring on-chain verification. Optimism has historically used single-round proofs but has been transitioning to a more advanced fault proof system. The efficiency of the fraud proof mechanism directly impacts the system's security and finality assumptions.
• Adoption and Ecosystem: Arbitrum and Optimism (along with its OP Stack derivative Base, developed by Coinbase) represent the dominant Optimistic Rollup implementations by TVL and transaction volume. The OP Stack has enabled a "superchain" vision in which multiple rollups share common infrastructure and can eventually communicate natively.

Related Concepts

Optimistic Rollup is one of the two primary Rollup paradigms, contrasted with ZK Rollup. Both types benefit from EIP-4844 (Blob Transactions) for cheaper data posting. The Sequencer plays a central role in ordering transactions, and its centralization is a recurring point of concern and active development. Data Availability (DA) is fundamental: fraud proofs can only be constructed if transaction data is available on-chain for challengers to inspect.

---

ZK Rollup

Definition

A ZK Rollup (Zero-Knowledge Rollup) is a type of Layer 2 rollup that generates cryptographic validity proofs — specifically ZK-SNARKs (Zero-Knowledge Succinct Non-Interactive Arguments of Knowledge) or ZK-STARKs (Zero-Knowledge Scalable Transparent Arguments of Knowledge) — to mathematically prove the correctness of every transaction batch before it is accepted by Layer 1. Unlike Optimistic Rollups, which assume validity and rely on fraud challenges after the fact, ZK Rollups provide instant, verifiable proof that all state transitions are correct. This eliminates the need for a challenge window, enabling much faster finality for withdrawals.

Key Points

• Cryptographic Validity Proofs: For each batch of transactions processed off-chain, a ZK Rollup's prover generates a cryptographic proof that attests to the correctness of the state transition without revealing the underlying transaction details. A verifier contract on Ethereum Layer 1 checks this compact proof, confirming validity in a single on-chain verification step. The proof is typically orders of magnitude smaller than the original transaction data.
• Near-Instant Finality: Because validity is cryptographically proven before a state root is accepted on Layer 1, there is no need for a challenge window. Once the Layer 1