An Ethereum Improvement Proposal (EIP) is a design document providing technical specifications for proposed changes to the Ethereum protocol — covering new features, bug fixes, process changes, or standards. EIPs are the formal mechanism through which Ethereum evolves: every significant protocol change begins as an EIP drafted by developers, reviewed by the community, debated, and eventually accepted or rejected through rough consensus. THE EIP LIFECYCLE Idea: Any developer or researcher can draft an EIP. Draft: Formally submitted as a pull request to the ethereum/EIPs GitHub repository. Assigned an EIP number. Review: Ethereum core developers and researchers provide technical feedback. The EIP editor facilitates the process. Last Call: Final 14-day review period. Accepted / Final: Core devs include the EIP in a planned hard fork (network upgrade). Stagnant / Withdrawn: EIPs that lose momentum are marked stagnant or withdrawn. EIP CATEGORIES Core EIPs: Changes to the consensus protocol, state machine, or networking layer. Require a hard or soft fork to activate. Networking EIPs: Changes to peer-to-peer protocol specifications. ERC (Ethereum Request for Comments): Application-layer standards — token standards, interface definitions. ERCs do not require protocol changes. Meta EIPs: Process changes, not technical changes. LANDMARK EIPS EIP-20 (ERC-20): The fungible token standard. Defined the interface every Ethereum token implements. EIP-721 (ERC-721): The NFT standard. EIP-1559: Introduced base fee burning and priority tips. Transformed Ethereum's fee market and created ETH deflationary mechanics. EIP-4337: Account abstraction standard. Smart contract wallets without protocol changes. EIP-4844 (Proto-Danksharding): Introduced blob transactions dramatically reducing L2 data costs — the most important scaling upgrade since The Merge. EIP-7702: Allows EOAs to temporarily act as smart contracts — enhancing account abstraction without full ERC-4337. ETHEREUM GOVERNANCE MODEL Ethereum has no formal on-chain governance voting. Changes happen through social consensus among: Core developer teams (Ethereum Foundation, client teams), researchers, miners/validators, and the broader community. This off-chain, rough-consensus model is slower but considered more resistant to plutocratic capture than token voting.