EIP

An EIP (Ethereum Improvement Proposal) is a formal, peer-reviewed design document that proposes a new feature, standard, or process for the Ethereum network, functioning as the primary mechanism for introducing changes to the core protocol, application-layer conventions, and client APIs. Modeled after Bitcoin's BIPs, the EIP process provides a structured, transparent framework for developers to submit, discuss, and implement upgrades, ensuring all changes are thoroughly vetted by the community. Each EIP is assigned a unique number and progresses through distinct stages—from Draft and Review to Final—before potential inclusion in a network upgrade or hard fork.

EIPs are categorized into three primary types. Core EIPs require a consensus-layer fork and propose low-level changes to the Ethereum protocol, such as the transition to proof-of-stake (EIP-3675) or gas fee market reforms (EIP-1559). ERC (Ethereum Request for Comments) standards, like ERC-20 for fungible tokens and ERC-721 for non-fungible tokens (NFTs), define application-level conventions and interfaces. Networking and Interface EIPs specify improvements to APIs, RPC methods, and other client-level specifications that do not affect consensus.

The lifecycle of an EIP is governed by Ethereum Cat Herders and core developers who manage the review process. Proposals are discussed on the Ethereum Magicians forum and the Ethereum GitHub repository, where technical debates and revisions occur. For a Core EIP to be activated, it must achieve rough consensus among client teams and be scheduled into a specific network upgrade, such as London, Shanghai, or Dencun. This rigorous process balances innovation with network stability and security.

Notable EIPs have fundamentally reshaped Ethereum. EIP-1559 introduced a base fee mechanism that is burned, altering Ethereum's monetary policy. EIP-1962 laid the cryptographic groundwork for the Beacon Chain. The ERC-4337 standard enables account abstraction through a separate mempool, allowing for smart contract wallets and gas sponsorship. These examples demonstrate how EIPs drive both foundational protocol evolution and expansive ecosystem development.

For developers and projects, tracking EIPs is essential for anticipating network changes, ensuring smart contract compatibility, and adopting new standards. The official repository for all proposals is maintained on GitHub, providing a complete historical record. Understanding the EIP process is key to participating in Ethereum's decentralized governance and contributing to its ongoing development.

EIP stands for Ethereum Improvement Proposal. It is a formal, structured document that describes a proposed new feature, process, or standard for the Ethereum blockchain. Modeled after the Bitcoin Improvement Proposal (BIP) system, the EIP process provides a transparent and collaborative framework for developers to introduce, discuss, and implement changes. Each EIP is assigned a unique number and serves as the single source of truth for the technical specification of a change, ensuring clarity and preventing fragmentation.

The concept was formally introduced in EIP-1, authored by Ethereum co-founder Vitalik Buterin, which itself defines the EIP process, roles, and guidelines. This meta-proposal established the governance structure, dividing EIPs into categories like Core (network consensus changes), ERC (application-level standards), and Informational. The system's design emphasizes decentralization; while core developers have significant influence, ultimate authority rests with Ethereum's broad community of node operators, who must adopt the changes through client software updates.

The etymology reflects Ethereum's roots in open-source software engineering and its predecessor, Bitcoin. By adopting the "Improvement Proposal" nomenclature, Ethereum signaled its commitment to a standardized, community-driven evolution. Key historical EIPs illustrate this: EIP-20 created the ubiquitous token standard for fungible assets, EIP-1559 fundamentally reformed the transaction fee market, and EIP-4844 introduced proto-danksharding for scaling. The lifecycle of an EIP—from a Draft through Review, Last Call, and finally Final—is a meticulous process designed to ensure robustness and consensus before any change affects the live network.

An EIP (Ethereum Improvement Proposal) is a formal design document that provides information to the Ethereum community, describing a proposed new feature, process, or standard. The process is modeled after Python's PEP and Bitcoin's BIP systems, ensuring a structured path from ideation to deployment. Proposals are categorized into three primary types: Core EIPs for consensus-critical protocol changes (like EIP-1559), ERC (Ethereum Request for Comments) for application-level standards (like ERC-20), and Meta EIPs for process changes. The lifecycle begins when an author drafts an EIP following a strict template and submits it to the EIPs GitHub repository for initial review.

Once submitted, the proposal enters a period of community review and discussion. This occurs on the Ethereum Magicians forum, GitHub pull requests, and developer calls. For Core EIPs, this stage is critical for identifying security risks, implementation feasibility, and network impact. Ethereum Core Developers, particularly those in the AllCoreDevs group, play a pivotal role in the technical assessment. The proposal may undergo multiple revisions based on feedback. A key milestone is the assignment of an EIP number by an editor, which signifies the draft is properly formatted and ready for serious consideration, though not approval.

The final stages involve formal acceptance and network activation. For a Core EIP to be implemented, it must reach consensus among client teams (like Geth, Nethermind, Besu) and be scheduled for a specific network upgrade or hard fork. This is coordinated through the AllCoreDevs calls and Ethereum Improvement Proposal coordination posts. For ERCs, acceptance is signaled by widespread community adoption and eventual finalization status. The entire process is transparent and open-source, relying on rough consensus rather than formal voting, ensuring that changes to Ethereum are rigorously vetted and aligned with the network's long-term health and decentralization.

An Ethereum Improvement Proposal (EIP) is a formal design document that describes a new feature, process, or standard for the Ethereum network, providing technical specifications and rationale for its implementation. EIPs are the primary channel through which developers, researchers, and community members introduce and debate potential upgrades, ranging from core protocol changes like the transition to proof-of-stake to application-level standards like the ubiquitous ERC-20 token interface. Each EIP follows a strict lifecycle, beginning as a draft, undergoing peer review, and, if accepted, progressing to a final state for implementation or standardization.

The EIP process is a cornerstone of Ethereum's decentralized governance, functioning as a transparent and open-source alternative to top-down decision-making. Proposals are publicly debated on forums like the Ethereum Magicians and GitHub, where technical merits, security implications, and network effects are rigorously scrutinized. For changes to the core protocol, consensus must be reached among client developers, node operators, and the broader community before an EIP is scheduled for inclusion in a network upgrade, or hard fork. This multi-stakeholder process ensures that changes are thoroughly vetted and aligned with the network's long-term health and security.

EIPs are categorized to manage their scope and impact. Core EIPs require a consensus-layer fork and change fundamental rules like the consensus algorithm or gas fees. Networking EIPs affect the peer-to-peer communication layer, while Interface EIPs define improvements to client APIs. The most widely recognized category is ERC (Ethereum Request for Comment), which specifies application-level standards for tokens, wallets, and other smart contract interfaces, such as ERC-721 for non-fungible tokens. This categorization streamlines the review process by directing proposals to the appropriate expert groups.

The ultimate authority for an EIP's fate lies with its authors, editors, and the community's willingness to adopt it. While the EIP Editors—a group of appointed maintainers—manage the repository and process, they do not unilaterally approve proposals. For Core EIPs, adoption depends on client teams implementing the code and node operators upgrading their software. For ERCs, adoption is market-driven, determined by whether developers choose to build using the proposed standard. This model embodies Ethereum's ethos of rough consensus and running code, where functional implementation and broad acceptance are the true measures of success.

Historically, EIPs have been instrumental in Ethereum's evolution. Landmark upgrades like EIP-1559, which reformed the transaction fee market, and EIP-4844, which introduced proto-danksharding for scaling, began as contentious proposals that matured through this process. The EIP framework provides a structured yet flexible pathway for innovation, ensuring that even radical changes undergo rigorous, transparent debate before becoming part of the live network. It is this process that allows Ethereum to evolve in a decentralized manner while maintaining stability and security for its users and applications.