Ethereum Consensus Specifications: Beacon Chain and Proof of Stake

Authors Ethereum consensus-specifications contributors
Year 2020 (living specification)
Project Ethereum
License CC0-1.0
Official Source https://ethereum.github.io/consensus-specs/

This page is an educational summary and analysis of an official whitepaper or technical paper, written for reference purposes. It is not a verbatim reproduction. CryptoGloss does not claim authorship of the original work. All intellectual property rights remain with the original author(s). The official document is linked above.

Directories Ethereum Whitepapers & Research

The Ethereum consensus specifications are a maintained set of technical rules for consensus-layer clients, not a single fixed whitepaper written by a short list of authors. The repository organizes specifications by network upgrade: each upgrade builds on earlier rules and describes the changes introduced at that point. It is the implementation reference for the Beacon Chain and Ethereum proof-of-stake consensus layer.

Beacon Chain and The Merge

The Beacon Chain began operating on December 1, 2020 as a proof-of-stake coordination chain alongside Ethereum’s proof-of-work execution chain. At first it coordinated validators and consensus without processing the ordinary Ethereum execution workload. The Merge on September 15, 2022 connected the proof-of-stake consensus layer to Ethereum’s existing execution layer and ended proof-of-work mining on mainnet.

Today, consensus and execution are distinct parts of one Ethereum network. Consensus clients follow the Beacon Chain rules for proposing and attesting to blocks, fork choice, and finality. Execution clients process transactions and smart-contract state. A consensus specification should therefore not be confused with the Ethereum Yellow Paper, which focuses on the execution-layer state machine.

What the Specifications Define

The repository describes the state transitions and data structures that consensus clients must implement so independently operated software can agree on validator status, attestations, blocks, and chain updates. It includes versioned upgrade specifications, tests, and related technical interfaces. The exact rules are version-specific; older Phase 0 descriptions do not capture every later change.

Casper FFG and LMD-GHOST are parts of the consensus design discussed in the Gasper paper, while the consensus repository defines the evolving protocol rules used by clients. The 2020 Gasper paper is an analysis of an idealized Beacon Chain protocol; it is not a substitute for the live, versioned specifications.

Validator Balances: 32 ETH Is a Minimum

Some older summaries describe 32 ETH as the validator stake limit. EIP-7251 changed the maximum effective balance for eligible compounding validators while retaining 32 ETH as the minimum activation balance. The proposal sets the Electra maximum effective balance at 2,048 ETH. Validator balance behavior depends on the applicable specification and withdrawal credentials, so 32 ETH should not be presented as a universal maximum.

How to Read This Source

The repository changes as Ethereum upgrades are specified and activated. Readers should identify the relevant version before relying on a rule, and should distinguish stable specifications from proposals that are still under development. This entry summarizes the repository’s role; it does not reproduce its code or replace the versioned source documents.

Social Media Sentiment

A 2026 r/ethereum discussion about Minimmit frames finality as a design trade-off: its author compares a proposed one-round gadget with Casper FFG, while commenters discuss fault tolerance, censorship, recovery, and validator diversity. The thread documents one technical debate; it does not show that Ethereum has adopted Minimmit or that the wider community has reached consensus.

Last updated: 2026-10

Related Terms

See Also

Sources