[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-4922":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":16,"forks30d":16,"starsTrendScore":19,"compositeScore":20,"rankGlobal":10,"rankLanguage":10,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":22,"hasPages":24,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":26,"readmeContent":27,"aiSummary":28,"trendingCount":16,"starSnapshotCount":16,"syncStatus":29,"lastSyncTime":30,"discoverSource":31},4922,"EIPs","ethereum\u002FEIPs","ethereum","The Ethereum Improvement Proposal repository","https:\u002F\u002Feips.ethereum.org\u002F",null,"Go",13880,6014,973,18,0,10,44,4,45,"Creative Commons Zero v1.0 Universal",false,"master",true,[],"2026-06-12 02:01:05","# Ethereum Improvement Proposals (EIPs)\n\n> **_ATTENTION_**: The EIPs repository has recently [undergone](https:\u002F\u002Fgithub.com\u002Fethereum\u002FEIPs\u002Fpull\u002F7206) a separation of ERCs and EIPs. ERCs are now accessible at [https:\u002F\u002Fgithub.com\u002Fethereum\u002Fercs](https:\u002F\u002Fgithub.com\u002Fethereum\u002Fercs). All new ERCs and updates to existing ones must be directed at this new repository. The editors apologize for this inconvenience.\n\nThe 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](https:\u002F\u002Feips.ethereum.org\u002FEIPS\u002Feip-1) governs how EIPs are published.\n\nThe [status page](https:\u002F\u002Feips.ethereum.org\u002F) tracks and lists EIPs, which can be divided into the following categories:\n\n- [Core EIPs](https:\u002F\u002Feips.ethereum.org\u002Fcore) are improvements to the Ethereum consensus protocol.\n- [Networking EIPs](https:\u002F\u002Feips.ethereum.org\u002Fnetworking) specify the peer-to-peer networking layer of Ethereum.\n- [Interface EIPs](https:\u002F\u002Feips.ethereum.org\u002Finterface) standardize interfaces to Ethereum, which determine how users and applications interact with the blockchain.\n- [ERCs](https:\u002F\u002Feips.ethereum.org\u002Ferc) specify application layer standards, which determine how applications running on Ethereum can interact with each other.\n- [Meta EIPs](https:\u002F\u002Feips.ethereum.org\u002Fmeta) are miscellaneous improvements that nonetheless require some sort of consensus.\n- [Informational EIPs](https:\u002F\u002Feips.ethereum.org\u002Finformational) are non-standard improvements that do not require any form of consensus.\n\n**Before you write an EIP, ideas MUST be thoroughly discussed on [Ethereum Magicians](https:\u002F\u002Fethereum-magicians.org\u002F) or [Ethereum Research](https:\u002F\u002Fethresear.ch\u002Ft\u002Fread-this-before-posting\u002F8). Once consensus is reached, thoroughly read and review [EIP-1](https:\u002F\u002Feips.ethereum.org\u002FEIPS\u002Feip-1), which describes the EIP process.**\n\nPlease 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](https:\u002F\u002Fethereum.stackexchange.com). 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.\n\nIf you would like to become an EIP Editor, please read [EIP-5069](.\u002FEIPS\u002Feip-5069.md).\n\n## Preferred Citation Format\n\nThe canonical URL for an EIP that has achieved draft status at any point is at \u003Chttps:\u002F\u002Feips.ethereum.org\u002F>. For example, the canonical URL for EIP-1 is \u003Chttps:\u002F\u002Feips.ethereum.org\u002FEIPS\u002Feip-1>.\n\nConsider any document not published at \u003Chttps:\u002F\u002Feips.ethereum.org\u002F> 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.\n\n## Validation and Automerging\n\nAll pull requests in this repository must pass automated checks before they can be automatically merged:\n\n- [eip-review-bot](https:\u002F\u002Fgithub.com\u002Fethereum\u002Feip-review-bot\u002F) determines when PRs can be automatically merged [^1]\n- EIP-1 rules are enforced using [`eipw`](https:\u002F\u002Fgithub.com\u002Fethereum\u002Feipw)[^2]\n- HTML formatting and broken links are enforced using [HTMLProofer](https:\u002F\u002Fgithub.com\u002Fgjtorikian\u002Fhtml-proofer)[^2]\n- Spelling is enforced with [CodeSpell](https:\u002F\u002Fgithub.com\u002Fcodespell-project\u002Fcodespell)[^2]\n  - False positives sometimes occur. When this happens, please submit a PR editing [.codespell-whitelist](https:\u002F\u002Fgithub.com\u002Fethereum\u002FEIPs\u002Fblob\u002Fmaster\u002Fconfig\u002F.codespell-whitelist) and **ONLY** .codespell-whitelist\n- Markdown best practices are checked using [markdownlint](https:\u002F\u002Fgithub.com\u002FDavidAnson\u002Fmarkdownlint)[^2]\n\n[^1]: https:\u002F\u002Fgithub.com\u002Fethereum\u002FEIPs\u002Fblob\u002Fmaster\u002F.github\u002Fworkflows\u002Fauto-review-bot.yml\n[^2]: https:\u002F\u002Fgithub.com\u002Fethereum\u002FEIPs\u002Fblob\u002Fmaster\u002F.github\u002Fworkflows\u002Fci.yml\n\nIt is possible to run the EIP validator locally:\n\nMake sure to add cargo's `bin` directory to your environment (typically `$HOME\u002F.cargo\u002Fbin` in your `PATH` environment variable)\n\n```sh\ncargo install eipw\neipw --config .\u002Fconfig\u002Feipw.toml \u003CINPUT FILE \u002F DIRECTORY>\n```\n\n## Build the status page locally\n\n### Install prerequisites\n\n1. Open Terminal.\n\n2. Check whether you have Ruby 3.1.4 installed. Later [versions are not supported](https:\u002F\u002Fstackoverflow.com\u002Fquestions\u002F14351272\u002Fundefined-method-exists-for-fileclass-nomethoderror).\n\n   ```sh\n   ruby --version\n   ```\n\n3. If you don't have Ruby installed, install Ruby 3.1.4.\n\n4. Install Bundler:\n\n   ```sh\n   gem install bundler\n   ```\n\n5. Install dependencies:\n\n   ```sh\n   bundle install\n   ```\n\n### Build your local Jekyll site\n\n1. Bundle assets and start the server:\n\n   ```sh\n   bundle exec jekyll serve\n   ```\n\n2. Preview your local Jekyll site in your web browser at `http:\u002F\u002Flocalhost:4000`.\n\nMore information on Jekyll and GitHub Pages [here](https:\u002F\u002Fdocs.github.com\u002Fen\u002Fenterprise\u002F2.14\u002Fuser\u002Farticles\u002Fsetting-up-your-github-pages-site-locally-with-jekyll).\n","Ethereum Improvement Proposals (EIPs) 项目旨在为以太坊及其相关规范提供标准化和高质量的文档。该项目通过跟踪并记录以太坊共识协议、网络层、接口标准以及应用层标准等方面的改进提案，来推动以太坊技术的发展。核心功能包括对各种类型EIP（如核心EIP、网络EIP、接口EIP等）的状态追踪与分类管理，并要求所有新提出的ERC或更新必须在新的ERC仓库中进行。适合场景包括但不限于：开发者需要了解或参与以太坊技术改进讨论时；研究人员希望查阅以太坊技术演进历史及未来方向时；以及任何对以太坊生态系统内标准制定感兴趣的人士。",2,"2026-06-11 03:01:32","top_language"]