We have received a lot of feedback from the Delegator community since mainnet launch in Dec last year that are reflecting on the Delegator experience at The Graph. A cross-network group consisting of Delegators, Core Devs and Indexers have worked together to consolidate all of the feedback we have received in many different Forum posts. I want to thank @ariel , @Topher66 , @chris , @cryptovestor and @davekaj for your engagement in a number of workshops over the last few weeks that has produced this Forum post which presents Delegator feedback in one holistic view.
We are looking to achieve two main goals with this very Forum post:
Transparency – a number of Forum posts we reviewed are dormant at this point and did not conclude with specific proposals that received broad community support. The Prioritization List (below) keeps these discussions on the radar to ensure they are not being forgotten. However, many of those Forum posts still require deeper community discussions to gain consensus and better understanding of detailed requirements. Therefore, the list is not meant to communicate a commitment to implementing solutions to the listed items, but rather aims to capture those discussions for everyone’s visibility.
Alignment – the Prioritization List shown below aims to reflect broad community sentiment, sorted in the order of importance from top to bottom. That list is a product of many Forum post reviews and discussions within the workshop group. For the Core Dev teams, this list should inform their own roadmap around protocol experience enhancements for delegation and the opportunity to align their prioritizations with the views of the community.
We have various data points included in the below table to create some clarity and common understanding. We have given each item a Name, which could be an issue or an idea, and we provide a brief Description of what it refers to. We have categorized items as overarching discussions that may have taken place across different Forum posts.
At a high level, we then directionally discussed what the community aimed to solve for by raising these items and we evaluated their Protocol Impact, meaning whether those requests have a general positive or negative effect on the protocol vis-à-vis its Design Intent. Our purpose was to provide some initial feedback to the question: will this result in a positive or negative outcome for all network participants as well as the integrity of the protocol itself? Naturally, these are rough assessments and should merely inform any deeper discussions the community may have on those items in the future.
In a similar approach, we also assessed Feasibility of each item. These too are rough assessments as we often did not have specific requirements to perform a detailed evaluation. We generally considered the impacted systems and also interdependencies to other codes and parameters in order to gauge anticipated complexity.
The Status column provides an update on where each item is today with regards to its progress:
Community Discussions – items with this status are still early on in the process. We were not able to confirm either community consensus, detailed requirements or both. It is generally fair to assume that there is currently no active IT development work around this item that aims to solve it. Should you feel strongly about an item with this status, then please create a new Forum post or resume discussions in an already existing thread in order to bring back attention to it (click Forum Link in the table).
Research – Items with this status currently have either technical or economical research being performed in order to assess feasibility or protocol impact. Feel free to raise follow-up questions in associated Forum posts if you would like to receive an update to the progress on any of these items.
GIP Development – items with this status are in active development for a protocol update. Progress on these items will generally be communicated in our monthly Core Devs Calls as well as Community Talk. Feel free to raise questions during these calls!
Polling/Voting – this status reflects the last major step in the governance process that typically concludes with a Council vote seeking to approve implementation.
Please note that you are able to scroll the table up/down and left/right to get visibility to all data points mentioned above.
There are a few things you can do now in response to this post:
The workshop group has attempted as best as possible to prioritize the items in the order we feel the community views them, mainly based on the activity levels we have seen in various Forum posts. We very much like to hear from the community if we got it right and everyone is welcome to provide feedback
Raise New Ideas
If you feel that there is a Delegation Experience item or issue missing from this list, please create a new Forum post and open up new discussions around it. The above prioritization list is not set in stone and our intention is to establish a living document. Which gets us to …
Own the Prioritization List
The workshop group has created the Prioritization List with the intent to implement a format and process that can be repeated in the future with more ease. This post is titled #1 and we plan on getting together again in about three months for a review: add new items, remove completed ones, change prioritization where necessary, provide updates in Notes and publish an updated version #2. This can flow into a regular cadence where we get together once a quarter in an effort to provide the community with the latest update on Delegator Experience Enhancement Prioritizations. The workshop group is not exclusive and everyone is invited to participate. It would be great to see the ownership of this list transitioning over to the Delegator community in the next couple of quarters. If you are interested in participating in that, please reach out to me via discord, or any other workshop group member.
Looking forward hearing from you!