The EIPIP Roadmap
A reflection of the EIPIP survey results
The first step in problem-solving is finding what the problems are. A simple way to find problems is to ask the community who’s involved.
We asked stakeholders a set of emotional questions. “What’s your biggest frustrations?” can identify current problems. “What’s your biggest fears?” can identify possible future problems. And, “What do you currently like?” can identify things that shouldn’t be changed.
The Results
The final results are almost the same as the survey results shown in May. There were three main categories:
- Decision making
- Clarity
- Capacity for completion
We also found community values for the EIP process:
- Transparency
- Low barrier to entry
- A high bar of acceptance
- Structure and legitimacy
These values guide what to keep in the process. While the problems will serve as a roadmap for progress moving forward.
The Roadmap
The survey revealed frustrations. To begin thinking of solutions, we can start by changing those frustrations into questions. Following this format, the roadmap is a series of questions.
Part 1: How can we formalize the decision-making process?
- How can we clarify the EIP process from hard-fork coordination decision-making?
- How can we make decisions less reliant on the Core Dev live calls?
- How can we create finality for EIPs?
- How can we ensure no one single party prevents the launch of an EIP?
- How can we ensure no one single party has the power to launch an EIP?
- How can the community be formally represented in the process?
- How can we ensure proposals have enough exposure to be decided on?
- How can we track/organize community consensus?
- How can we clarify what’s been considered for EIPs and who’s in favor?
- How can we increase represented groups/diversity in the Core Devs?
- How can we keep the EIP process apolitical?
- Should EIP authors be required to present their EIP on the All Core Devs call?
Part 2: How can we increase clarity in the EIP process?
- How can we clarify what steps EIP authors need to take for their EIP to be included in clients?
- How can we make the EIP process more well known?
- How can the community track progress for EIPs and who has it implemented?
- How can discussions around EIPs be more easily followed?
- How can we keep the attention away from the process, and towards the technical discussion?
- Should EIP authors create a reference implementation in a client as a requirement?
- Should a tagging header be added to organize EIPs?
- Should EIPs include a list of use cases?
- Should EIPs include a list of pros and cons?
Part 3: How can we increase the capacity to finalize EIPs?
- How can we onboard more EIP editors?
- How can we onboard and assign more EIP champions?
- How can we reduce the backlog?
- How can we reduce the turnaround time?
- How can we organize working groups for different EIP categories?
A Reflection on the Survey
Pursuing a survey open to all stakeholders in the EIP process has helped the EIP working group organize what issues should be worked on. It is successful in this way, paving the way for success for EIPIP.
One thing that can be done differently next time for the EIPIP survey is seeking more understanding of community goals and values. This can be the inclusion of a question, “What are your wants and aspirations with the EIP process?”
Regardless, the EIPIP working group aims to consider responses into what has become the roadmap for EIPIP for the next few months.
