ethereum/eips

★ 13,849GoAudience · developerComplexity · 1/5Setup · easy

Mindmap

mindmap
  root((Ethereum EIPs))
    EIP categories
      Core protocol
      Networking
      Interface
      Meta and process
    ERCs
      Token standards
      NFT standards
      Separate repo now
    Proposal process
      Public discussion first
      EIP-1 rules
      Automated checks
    Website
      eips.ethereum.org
      Run locally with Jekyll

mindmap root((Ethereum EIPs)) EIP categories Core protocol Networking Interface Meta and process ERCs Token standards NFT standards Separate repo now Proposal process Public discussion first EIP-1 rules Automated checks Website eips.ethereum.org Run locally with Jekyll

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Browse and track the status of active Ethereum protocol proposals and token standards like ERC-20 and NFTs.

USE CASE 2

Submit a new Ethereum Improvement Proposal by following the EIP-1 process and automated formatting checks.

USE CASE 3

Look up the exact rules that define how ERC-20 tokens or NFTs must behave for your smart contract project.

USE CASE 4

Run the eips.ethereum.org website locally to preview documentation changes before submitting a pull request.

Tech stack

MarkdownJekyllGo

Getting it running

Difficulty · easy Time to first run · 5min

No license information is mentioned in the explanation.

In plain English

This repository is the official home for Ethereum Improvement Proposals, commonly abbreviated as EIPs. Ethereum is a public blockchain network, and like any large technical system, it needs a formal process for proposing and tracking changes. EIPs are the documents that define those changes, covering everything from low-level protocol rules to how applications built on Ethereum should behave. The repository organizes proposals into several categories. Core EIPs deal with the fundamental rules of how the Ethereum network reaches agreement. Networking EIPs cover how the individual computers running Ethereum communicate with each other. Interface EIPs standardize how users and outside applications connect to the blockchain. Meta EIPs handle process and governance questions. Informational EIPs document things that do not require a formal vote. There is also a related category called ERCs, which stands for Ethereum Request for Comments. These cover standards for applications built on top of Ethereum, such as the rules that make tokens and NFTs work in a predictable way. ERCs have recently been moved to a separate repository at github.com/ethereum/ercs, so new ERC proposals and updates go there rather than here. If you want to propose a change, the process requires first discussing the idea publicly on Ethereum Magicians or Ethereum Research before writing a formal document. The rules for what a valid EIP looks like are themselves defined in EIP-1, which is the starting point for anyone who wants to participate. All pull requests go through automated checks for formatting, spelling, and compliance with those rules before they can be merged. The repository also contains the source for the public status website at eips.ethereum.org, which lists all proposals and their current state. Instructions for running that site locally are included in the README for contributors who want to preview changes.

Copy-paste prompts

Prompt 1

I want to propose a new Ethereum token standard. Show me how to write an EIP following the EIP-1 template and pass the automated checks before submitting a pull request.

Prompt 2

Find all active Core EIPs related to gas optimization on Ethereum and summarize what changes each one proposes.

Prompt 3

Explain the EIP lifecycle stages, Draft, Review, Last Call, Final, and what steps are required to move a proposal forward.

Prompt 4

Show me the ERC-20 standard from the EIPs repository and explain each required function in plain English for someone building their first token.

Open on GitHub → Explain another repo

← ethereum on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.