This post describes the ongoing experiment of impact metric based voting and asks for input and feedback from the community!
Metrics based voting
Currently, voting in Retroactive Public Goods Funding (Retro Funding) is made up of reviewing and comparing individual applications to come up with an allocation of tokens among applicants. This process is intensive in manual labour and highly dependent on the individual experience and expertise of citizens.
In recent Retro Funding rounds, Open Source Observer has outlined an alternative approach to evaluating impact, by leveraging data to allow citizens express what types of impact matter most and how they should be rewarded instead of revieweing individual projects.
Badgeholders are badgeholders because they care deeply about the health and growth of the ecosystem as a whole, not because they know the intricacies of projects. For most badgeholders, evaluating the quality of a portfolio of projects is a much better way of leveraging their time and expertise than evaluating each individual project. This will become even more apparent as the mechanism scales to more projects.
See @ccerv1ās blog posts here and OS Observers work on Impact vectors.
Different types of impact require different measurements
While some contributions to Optimism have rich data associated with them, which we can leverage to evaluate impact today, such as onchain contracts and open source libraries, others lack high quality and standardised data for impact evaluation, such as IRL events, education initiatives and offchain tooling.
A metrics based voting experience is only viable for a subset of impact today and canāt be applied to evaluate all contributions to the Optimism Collective.
Impact Calculator: Experimenting with a metric based voting experience
To further explore how citizens could leverage data to evaluate the impact of a number of projects, we started by putting up a project idea for a prototype of a metric based voting interface called impact calculator. This prototype leverages OS Observer data for impact metrics.
Buidl Guidlās prototype
Via Buidl Guidlās Impact Calculator a user is able to
- Select Impact Vectors: Allows users to choose from various impact vectors (e.g. metrics) with descriptions and creator names, search functionality, and options to view detailed pages or add vectors to a ballot.
- Ballot View: A ballot system where users can select or deselect impact vectors and edit their configurations. This includes a graphical representation of the allocation of OP among projects.
- Detailed View: Each impact vector has a detailed view, including a name, description, creator, and a link to GitHub. Users can visualize the impact vector and configure it.
- Configuration Option: Users can set a scale or weight to deterimine how flat or skewed the eventual distribution of tokens to projects should be.
TLDR; pick what types of impact you think are important and assign weight to them.
RetroPGFhub.com is in the early stages of developing their own version of the impact calculator protoype and will share for input once ready.
Request for input and feedback
At this early stage input and feedback from the community are very valuable in shaping the iteration of this prototype. For the purpose of this prototype weāre focusing on evaluating the impact of onchain deployments and open source libraries.
- What are your thoughts on impact metric based voting? What excites you about it or what makes you skeptical?
- What do you think of the current selection of impact vectors? What impact vectors would you want to see to reward onchain deployments/builders?
- Does the weighting help you in expressing what impact you find valuable? Would you want to have additional configuration options?
- Does the graph help you visualize the impact of your impact vector weightings? Do you understand what the graph is showing you? Do you want to see how individual projects are impacted by your weightings?
Check out the impact calculator here
This thread is used for an open discussion on impact metric based voting and will be used for further updates on the impact calculator prototype.