Ethereum Improvement Proposal (EIP)

Overview

An Ethereum Improvement Proposal (EIP) is the primary format used to document technical changes and standards in the Ethereum ecosystem. A proposal normally describes the problem, specification, rationale, compatibility considerations, security issues, and reference material needed for review and implementation.

EIPs cover several scopes. Core proposals can change consensus or execution rules, networking proposals can change peer protocols, interface proposals can define client APIs, and ERCs can define application-level standards such as token interfaces. The category determines which implementers and users are affected.

Status matters. A draft can be actively discussed, a review-stage proposal can still change, and a final standards document can exist without every network or application supporting it. Core activation also depends on client releases and a scheduled network upgrade.

Examples include EIP-1559, which changed Ethereum’s execution fee market, and EIP-4844, which introduced blob-carrying transactions. The proposal text remains the technical reference, while current client specifications and deployed network behavior determine production reality.

Payment and infrastructure teams should track only EIPs relevant to their transaction types, fee estimates, addresses, APIs, and finality assumptions. An integration checklist should record whether a proposal is merely published, implemented by a client, activated on testnet, or deployed on mainnet under the active Blockchain Protocol.

An EIP number should not be used as a substitute for explaining the deployed feature. Users need to know which network upgrade activated it, which clients support it, and what behavior changed. Archived drafts and superseded proposals can remain searchable long after they stopped representing current practice.