An Ethereum Improvement Proposal (EIP) is a formal design document that describes a proposed change to the Ethereum protocol, its standards, or its processes, providing the technical specification and rationale for community review. EIPs are categorised into Core proposals affecting consensus, Networking proposals, Interface proposals, and Application-level standards known as ERCs. They follow a defined lifecycle from Draft through Review, Last Call, and Final, serving as the canonical mechanism for coordinating decentralised protocol evolution.
Overview
- The EIP process exists to let a decentralised, permissionless community converge on protocol changes without a central authority.
- Each proposal carries a unique number, an author, a category, and a status that advances through a defined lifecycle.
- Core EIPs that alter consensus require client implementation and broad social consensus before activation in a network upgrade.
- ERCs, the application-standard subclass, have produced widely adopted interfaces such as fungible and non-fungible token specifications.
Mechanisms
- Lifecycle stages: Draft, Review, Last Call, Final (or Stagnant, Withdrawn) govern maturity and revisability.
- Categories: Core, Networking, Interface, and ERC partition proposals by the layer they affect.
- Reference implementations and test vectors accompany Core proposals to ensure client interoperability.
- Editors curate the repository, enforcing formatting and ensuring proposals are technically complete before merge.
Applications
- Token interface standards (fungible, non-fungible, multi-token) enabling wallet and exchange interoperability.
- Account abstraction and fee-market reforms that reshape transaction economics.
- Precompiles and opcode additions extending the virtual machine’s capabilities.
- Meta proposals that define the EIP process itself and the governance of upgrades.
Provenance
Merged from EIP (needs reconciliation)
An Ethereum Improvement Proposal (EIP) is the formal, versioned design document through which changes to the Ethereum protocol, its standards and its processes are proposed, debated and ratified. Categories include core protocol changes, networking and interface proposals, and application-level standards known as ERCs such as the token interfaces. Each proposal moves through defined statuses from draft to final, providing a transparent, community-driven mechanism for evolving the network.
Overview
- Each proposal is authored, numbered and discussed openly before being accepted, rejected or withdrawn.
- Categories separate core consensus changes from networking, interface and application standards.
- Statuses such as draft, review, last call and final track a proposal’s maturity and stability.
Key aspects
- Versioned, numbered documents with a defined template.
- Distinction between core EIPs and application-level ERCs.
- A status lifecycle that signals readiness for implementation.
- Open, rough-consensus deliberation among contributors and clients.
Applications
- Defining a Token Standard for fungible and non-fungible assets.
- Specifying Smart Contract interfaces for interoperability.
- Coordinating protocol upgrades affecting the Ethereum Virtual Machine.
- Ratifying consensus changes such as the move to Proof of Stake.