Qaynaq LABS · TOOLS

CRYPTO GLOSSARY

Ethereum Improvement Proposal (EIP)

A standardized document for proposing changes to the Ethereum blockchain, covering technical upgrades, new features, or process improvements. EIPs are the primary mechanism for evolving Ethereum’s protocol.

Technical definition

An EIP is a design document that outlines a proposed change to the Ethereum ecosystem, including core protocol specifications, client APIs, contract standards, or process improvements. EIPs follow a structured format (e.g., EIP-1 defines the EIP process itself) and are categorized as Standards Track (e.g., EIP-1559 for fee market changes), Informational (e.g., EIP-5702 for account abstraction), or Meta (e.g., EIP-1014 for CREATE2 opcode). They undergo review by the Ethereum community, including core developers, researchers, and node operators, before potential implementation via network upgrades (e.g., hard forks like Berlin or Shanghai).

An analogy

An EIP is like a formal proposal in a city council meeting: it details a change (e.g., adding a new bus route or updating zoning laws), is reviewed by experts and stakeholders, and if approved, is implemented in a structured way. The proposal itself doesn’t change anything until the council (or in Ethereum’s case, the network) votes to adopt it.

Why it matters

EIPs ensure Ethereum evolves in a decentralized, transparent, and secure manner. They allow the community to collaboratively propose, debate, and implement changes without relying on a single authority, maintaining Ethereum’s open-source ethos.

Where it came from

The EIP process was formalized in 2015 by Ethereum co-founder Vitalik Buterin and others, inspired by Bitcoin’s BIP (Bitcoin Improvement Proposal) system. The first EIP, EIP-1, was published in October 2015, establishing the framework for future proposals.

Example in practice

EIP-1559, proposed in 2019 and activated in August 2021 (as part of the London upgrade), introduced a base fee mechanism to Ethereum’s transaction pricing, aiming to reduce volatility in gas fees and burn a portion of fees to reduce ETH supply.

Common misconceptions

  • EIPs are automatically implemented → Correction: EIPs are proposals; they only take effect if accepted by the community and activated via a network upgrade (e.g., hard fork).
  • EIPs are only for technical changes → Correction: While most are technical, EIPs can also propose process improvements (e.g., EIP-1014 for CREATE2) or informational updates (e.g., EIP-5702 for account abstraction).

Risks & limitations

  • Community fragmentation: Contentious EIPs (e.g., EIP-999 for DAO funds recovery) can split the community, leading to forks or reduced cohesion.
  • Implementation risks: Bugs in EIPs (e.g., EIP-2028, which reduced gas costs for zk-SNARKs) can introduce vulnerabilities if not thoroughly tested.
  • Activation delays: EIPs may take years to implement due to coordination challenges (e.g., EIP-4844 for proto-danksharding took ~3 years from proposal to activation).
  • Centralization risks: While EIPs are community-driven, major decisions (e.g., Ethereum’s transition to Proof-of-Stake) often require coordination with core developers and large stakeholders, which can introduce informal influence.

Related terms

About "Ethereum Improvement Proposal (EIP)" in crypto

Cryptocurrency vocabulary moves faster than any other technical field. New terms appear weekly, old terms quietly change meaning, and most "definitions" online were written by someone trying to sell you something. Qaynaq Labs' crypto glossary aims for the opposite: neutral, accurate, skeptical explainers that include the downside.

This entry covers the technical mechanics, a real-world analogy, where the concept came from, and what could go wrong. Pair it with the related terms to build a working mental model of how the pieces fit together.

Frequently asked

Who can submit an EIP?

Anyone can submit an EIP by following the process outlined in EIP-1. However, high-impact proposals (e.g., core protocol changes) typically require significant research, testing, and community buy-in to be considered.

How does an EIP become a reality?

An EIP must first be accepted as a ‘Draft’ by the community, then undergo rigorous review and testing. If approved, it is scheduled for activation in a network upgrade (e.g., hard fork) after consensus is reached among node operators, client teams, and miners/validators.

Are EIPs legally binding?

No. EIPs are technical proposals and do not have legal force. Their adoption depends on voluntary coordination among network participants (e.g., miners, validators, and users).

What’s the difference between an EIP and an ERC?

EIPs are broader and can propose changes to any part of Ethereum (e.g., protocol upgrades, process improvements). ERCs (Ethereum Request for Comments) are a subset of EIPs focused specifically on application-level standards (e.g., ERC-20 for tokens, ERC-721 for NFTs).

Can an EIP be rejected?

Yes. EIPs can be rejected at any stage if they lack community support, are deemed technically flawed, or conflict with Ethereum’s long-term goals (e.g., EIP-867, which proposed a controversial DAO fund recovery mechanism, was rejected).