Ethereum: A Secure Decentralised Generalised Transaction Ledger (Yellow Paper)

Authors Wood, Gavin
Year 2014
Project Ethereum
License Creative Commons BY-SA 4.0
Official Source Official Yellow Paper PDF (Shanghai version)

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.

Original paper Original paper
Directories Ethereum Whitepapers & Research

Ethereum: A Secure Decentralised Generalised Transaction Ledger, commonly called the Yellow Paper, is Gavin Wood’s formal specification of Ethereum’s execution layer. First published in 2014, it describes protocol rules for account state, transactions, the Ethereum Virtual Machine (EVM), and state changes.

Version note: The linked PDF is the Shanghai version, commit efc5f9a dated February 4, 2025. The official Yellow Paper repository’s version notice says the document reflects the Shanghai upgrade, activated in April 2023, and does not include Cancun changes. It should be read as a dated specification snapshot, not as a complete description of today’s Ethereum protocol.


Publication and Scope

Gavin Wood originally wrote the Yellow Paper as a formal account of Ethereum’s execution rules. Its mathematical definitions are useful when studying how transaction processing and EVM execution were specified for a particular protocol version. The linked PDF is scoped to the execution layer; Ethereum’s consensus layer is specified separately in the Ethereum Consensus Specifications.

What the Yellow Paper Describes

The paper models Ethereum’s world state and the transition from one state to another when a transaction is processed. It gives formal treatment to account data, transaction validity and execution, contract creation and calls, EVM behavior, and gas accounting. Its appendices also document data structures and version-specific instruction and cost details.

Some details in the PDF are specific to its Shanghai-era snapshot. Opcode behavior, gas schedules, precompiles, and other protocol rules can change through upgrades. Do not use an older table in isolation as a statement of current mainnet behavior.

Execution Layer and Consensus Layer

The Yellow Paper is not a single, current specification of every part of Ethereum. It focuses on execution: transactions, account state, and EVM computation. Consensus rules are maintained in a separate specification. This distinction matters especially for post-Merge Ethereum, where execution and consensus clients work together but follow separate protocol specifications.

How to Use It Today

Use the Yellow Paper for its formal definitions and to understand the design of the execution layer as captured by the linked version. For current fork behavior, consult the actively maintained Ethereum Execution Layer Specifications (EELS), which the repository describes as tracking network upgrades. The Ethereum Foundation’s introduction to EELS explains its role as a readable, executable successor to the older execution-layer specification. Check the relevant upgrade materials and consensus specifications when a question crosses those boundaries.

Social Media Sentiment

A January 2025 discussion on r/ethereum asked why newer protocol features were absent from the Yellow Paper. Replies pointed readers to fork-specific specifications and EELS; one response described EELS as current for the development networks it covered at the time. This small sample shows frustration about the gap between the familiar paper and newer protocol changes alongside positive reactions to the executable specification. One thread is not a representative survey of Ethereum developers.

Last updated: 2026-10


Related Terms

See Also

Sources


Last updated: October 11, 2026