web3wagmi
← All standards

EIP-1 EIP Purpose and Guidelines

LivingMetacreated 2015-10-273 later proposals build on it

Authors: Martin Becze, Hudson Jameson, et al.

Built on by (3)

Later proposals that name this one in their requires field.

EIP-5069EIP Editor HandbookEIP-5757Process for Approving External ResourcesEIP-7329ERC/EIP Repository split

What the specification covers

What is an EIP?EIP RationaleEIP TypesSpecial requirements for Core EIPsEIP Work FlowShepherding an EIPCore EIPsEIP ProcessWhat belongs in a successful EIP?EIP Formats and TemplatesEIP Header Preambleauthor headerdiscussions-to headertype headercategory headercreated headerrequires headerLinking to External ResourcesExecution Client SpecificationsEthereum System Contract ImplementationsExecution Specification TestsConsensus Layer SpecificationsNetworking SpecificationsPortal SpecificationsWorld Wide Web Consortium (W3C)Web Hypertext Application Technology Working Group (WHATWG)Internet Engineering Task Force (IETF)Bitcoin Improvement ProposalNational Vulnerability Database (NVD)Chain Agnostic Improvement Proposals (CAIPs)Ethereum Yellow PaperExecution Client Specification TestsDigital Object Identifier SystemExecution API SpecificationUnicode Technical Standards (UTS)Linking to other EIPsAuxiliary FilesTransferring EIP OwnershipEIP EditorsEIP Editor ResponsibilitiesStyle GuideTitlesDescriptionsEIP numbersRFC 2119 and RFC 8174HistoryCopyright

This proposal declares no Solidity interface, so there is nothing to compute. It may be a core protocol change, a meta proposal, or written in prose only.

Compare with

Parsed from the canonical specification