如何向以太坊社区提交一个eip？
Table of contents
如何向以太坊社区提交一个EIP？
前言
- 以太坊社区需要构建，早期建设者会得到真实的价值回报。
- 其他公链创造力很多是依靠以太坊社区，这也是以太坊社区的生命力所在。
- 除了炒币，支持或者参与创造到社区的规划和建设中来，是非常有价值的。
- EIP是以太坊提升提案，用来讨论任何有意思的建议，EIP721也就是NFT是之一，来自于Lara Labs。
- 嗯，我来自于jLabs.tech.
Resource
注意事项
首先深度阅读EIP-1:eips.ethereum.org/EIPS/eip-1
要点下面会列出。
ATTENTION! If you would like to submit an EIP and it has already been written as a draft (see the template for an example), please submit it as a Pull Request.
If you are considering a proposal but would like to get some feedback on the idea before submitting a draft, then continue opening an Issue as a thread for discussion. Note that the more clearly and completely you state your idea the higher the quality of the feedback you are likely to receive.
Keep in mind the following guidelines from EIP-1:
Each EIP must have a champion - someone who writes the EIP using the style and format described below, shepherds the discussions in the appropriate forums, and attempts to build community consensus around the idea. The EIP champion (a.k.a. Author) should first attempt to ascertain whether the idea is EIP-able. Posting to the the Protocol Discussion forum or opening an Issue is the best way to go about this.
Vetting an idea publicly before going as far as writing a EIP is meant to save the potential author time. Asking the Ethereum community first if an idea is original helps prevent too much time being spent on something that is guaranteed to be rejected based on prior discussions (searching the Internet does not always do the trick). It also helps to make sure the idea is applicable to the entire community and not just the author. Just because an idea sounds good to the author does not mean it will work for most people in most areas where Ethereum is used.
Once the champion has asked the Ethereum community as to whether an idea has any chance of acceptance, a draft EIP should be presented as a Pull Request. This gives the author a chance to flesh out the draft EIP to make properly formatted, of high quality, and to address initial concerns about the proposal.
解释
- 提案首先是有了一些上下文和想法，思考，大多数来自于实际的工作和开发中遇到的问题和困难，发现需要改进以太坊会更好。
- 例如社区项目在参与到元宇宙建设过程中，发现如果定义一套标准，会更有利于开发，而这套标准贡献给社区，能够帮助别人提升效率，也可以提升彼此的交互效率。
- EIP的提交过程，提供了如何说清楚、说明白的标准。
讨论
- 首先要有一个champion，也就是主笔作者。
- 然后在对应社区讨论，一般是github上建立一个issue（例如721的github.com/ethereum/eips/issues/721）或者一个论坛帖子：the Ethereum Magicians forum。
- 讨论过程需要ascertain whether the idea is EIP-able，是不是值得和能够去建立一个EIP。
- 另外，在写一个EIP之前，最好公开的讨论这个idea，询问以太坊社区是否可行，可以防止浪费太多时间在不必要的idea。
- PS: 魔法师论坛的readme：ethereum-magicians.org/t/welcome-please-rea..，发现需要很多时间逛一逛，熟悉规则。
- 如果询问和讨论社区后，你的帖子大家觉得有机会接受，则提交一个提案草稿。
草稿
- Fork EIP库，像我这样：
- 图床可以访问，为啥不显示？先不管了
- 使用模板template 撰写你的EIP，这里面有一大堆的概念，但先写再说。
- 完成草稿后，提交一个Pull Request，嗯，就是传说中的PR，哈哈。
- 提交后会被review，例如周博士的EIP4972:github.com/ethereum/EIPs/pull/4972
状态
- 提交PR后，社区核心审核人群：This PR requires review from one of [@lightclient, @axic, @SamWilsn]
- 反复沟通格式、表述，直到草稿被merge，则进入了EIP的状态列表。
- 状态列表很复杂
- Status
- 核心是：Idea-->Draft-->Review<-->Last Call-->Final
- Review会进入Living状态，反复迭代修改
- 也可能进入Stagnant的停滞状态。
其他
- 以太坊工作PM会议：github.com/ethereum/pm，包括议程，记录，对应twitter记录和视频。
- 例如最近一次会议讨论记录：github.com/ethereum/pm/blob/master/AllCoreD..
- Kiln和beacon chain的进展等等，目前我个人不清楚是否可以未经邀请去添加自己的agenda以及参与会议，看起来需要成为pm？。
- 本文会发布在Dapp Learning社区:github.com/Dapp-Learning-DAO/Dapp-Learning，以及个人Blog(jLab.tech)