Merged by EIP-Bot.
|1 day ago|
|.github||1 day ago|
|EIPS||1 day ago|
|_data||2 years ago|
|_includes||2 weeks ago|
|_layouts||2 months ago|
|assets||3 days ago|
|config||3 days ago|
|rss||1 week ago|
|.gitattributes||9 months ago|
|.gitignore||3 months ago|
|404.html||3 months ago|
|CNAME||5 years ago|
|Gemfile||3 years ago|
|Gemfile.lock||1 week ago|
|LICENSE.md||11 months ago|
|README.md||1 month ago|
|_config.yml||9 months ago|
|all.html||5 years ago|
|core.html||5 years ago|
|eip-template.md||2 months ago|
|erc.html||5 years ago|
|index.html||1 week ago|
|informational.html||5 years ago|
|interface.html||5 years ago|
|meta.html||5 years ago|
|networking.html||5 years ago|
Ethereum Improvement Proposals (EIPs)
The goal of the EIP project is to standardize and provide high-quality documentation for Ethereum itself and conventions built upon it. This repository tracks past and ongoing improvements to Ethereum in the form of Ethereum Improvement Proposals (EIPs). EIP-1 governs how EIPs are published.
The status page tracks and lists EIPs, which can be divided into the following categories:
- Core EIPs are improvements to the Ethereum consensus protocol.
- Networking EIPs specify the peer-to-peer networking layer of Ethereum.
- Interface EIPs standardize interfaces to Ethereum, which determine how users and applications interact with the blockchain.
- ERCs specify application layer standards, which determine how applications running on Ethereum can interact with each other.
- Meta EIPs are miscellaneous improvements that nonetheless require some sort of consensus.
- Informational EIPs are non-standard improvements that do not require any form of consensus.
Before you write an EIP, ideas MUST be thoroughly discussed on Ethereum Magicians or Ethereum Research. Once consensus is reached, thoroughly read and review EIP-1, which describes the EIP process.
Please note that this repository is for documenting standards and not for help implementing them. These types of inquiries should be directed to the Ethereum Stack Exchange. For specific questions and concerns regarding EIPs, it's best to comment on the relevant discussion thread of the EIP denoted by the
discussions-to tag in the EIP's preamble.
If you would like to become an EIP Editor, please read EIP-5069.
Preferred Citation Format
The canonical URL for an EIP that has achieved draft status at any point is at https://eips.ethereum.org/. For example, the canonical URL for EIP-1 is https://eips.ethereum.org/EIPS/eip-1.
Consider any document not published at https://eips.ethereum.org/ as a working paper. Additionally, consider published EIPs with a status of "draft", "review", or "last call" to be incomplete drafts, and note that their specification is likely to be subject to change.
Validation and Automerging
All pull requests in this repository must pass automated checks before they can be automatically merged:
- eip-review-bot determines when PRs can be automatically merged 1
- EIP-1 rules are enforced using
- HTML formatting and broken links are enforced using HTMLProofer2
- Spelling is enforced with CodeSpell2
- False positives sometimes occur. When this happens, please submit a PR editing .codespell-whitelist and ONLY .codespell-whitelist
- Markdown best practices are checked using markdownlint2
It is possible to run the EIP validator locally:
cargo install eipv eipv <INPUT FILE / DIRECTORY>
Build the status page locally
Check whether you have Ruby 2.1.0 or higher installed:
If you don't have Ruby installed, install Ruby 2.1.0 or higher.
gem install bundler
Build your local Jekyll site
Bundle assets and start the server:
bundle exec jekyll serve
Preview your local Jekyll site in your web browser at
More information on Jekyll and GitHub Pages here.