Hello, I hope youâre doing well.
Weâre also looking for a sponsor, we would appreciate it if youâre interested in sponsorship.
gm. I have revised this proposal based on feedback from delegates. I am seeking a top 100 delegate to sponsor this Mission Request. Thank you in advance for your consideration.
Delegate Mission Request Summary:
Develop an evaluation platform that produces attestations of impact to the OP collective and provides community members a way to showcase their impact and have it evaluated by domain experts.
S5 Intent: Intent 4: Improve governance accessibility
Proposing Delegate: Delegate name/pseudonym, linked to delegate profile
Proposal Tier: Ember
Baseline grant amount: 69,420 OP (34,710 / applicant)
Should this Foundation Mission be fulfilled by one or multiple applicants: Two
Submit by: To be set by Grants Council
Selection by: To be set by Grants Council
Start date: ASAP
Completion date: 30/06/2024
Specification
How will this Delegate Mission Request help accomplish the above Intent?
This Request will help achieve Intent 4 by developing an evaluation platform. The platform should allow collective members to make claims and evaluations of the impact and value they bring to the collective. Badgeholders can use the attestations produced by this platform to guide future RPGF allocations. One of the core governance design principles is âImpact = profit⌠to ensure that every individual is rewarded in proportion to their positive impact on the Collectiveâ. To fully realize this design principle, it is essential to continue building and experimenting with systems for evaluating the impact of individuals and projects in the collective.
The evaluation platform should provide a standard for evaluating ecosystem impact. The platform should incorporate qualitative impact, which is often hard to assess, and quantitative impact. The existing Impact Evaluation Framework established in season 4 should help guide the evaluation and data collected. Not only will this provide insights into community membersâ impact, but it can also be used as a part of reputation scores in the Collective.
What is required to execute this Delegate Mission Request?
- Research the existing reputation score system, current tools, EAS schemas, and the Impact Evaluation Framework.
- Develop evaluation platform including:
- Design standard forms and metrics for evaluating Impact.
- Standardizing EAS attestation schemas.
- Design and develop a front-end dashboard.
- Create a plan for selecting and incentivizing impact evaluators.
- Pilot the platform ahead of RPGF4
How should the Token House measure progress towards this Mission?
- Documentation of the evaluation platform.
- Documentation of all GitHub repos
- Number of evaluations attestations completed.
- Feedback from the collective on the platform.
- Product adoption in the public goods funding space
How should badgeholders measure impact upon completion of this Mission?
- Success of the pilot project and its added value to the RPGF Badgeholder process.
- Positive feedback from the OP collective on the evaluation platform.
- Adoption and usage of the evaluation platform.
- Number of evaluations attestations completed.
- Number of grants programs using the app
Have you engaged a Grant-as-a-service provider for this Mission Request? No
Has anyone other than the Proposing Delegate contributed to this Mission Request? Carlos Melgar
Custom OP Chains - Three POCs of OP Chains
Intent : Grow The Superchain
Proposing Delegate: Delegate name/pseudonym, linked to delegate profile
Proposal Tier: Fledgling
Baseline grant amount: 150,000 OP
Should this Foundation Mission be fulfilled by one or multiple applicants: One Applicant
Submit by: To be set by Grants Council
Selection by: To be set by Grants Council
Start date: ASAP
Completion date: Four months
Specification
How will this Delegate Mission Request help accomplish the above Intent?
Optimism provides an excellent opportunity for various applications to adopt the OP stack and create their own chains as needed. This presents a win-win situation for both the application and other participants in the OP stack ecosystem.
Setting up a new OP chain is a complex process, and the requirements and steps are often unclear to many developers.
This initiative will facilitate the creation of three separate proof-of-concept (POC) applications, where developers can develop their own chains and create an application utilizing their specific chain.
The output from each of these three POCs should include:
- A GitHub repository containing the applicationâs code.
- Three articles written by each team.
- 2-4 long-form videos that explain the problem statement, OP chain deployment, and application code.
What is required to execute this Delegate Mission Request?
For each POC we can expect the following outputs:
- A GitHub repository containing the applicationâs code.
- Three articles written by each team.
- 2-4 long-form videos explaining the problem statement, OP chain deployment, and application code.
How should the Token House measure progress towards this Mission?
The output is very clearly defined and the applications can be paid only upon completion of milestones.
How should badgeholders measure impact upon completion of this Mission?
The real impact will come over a few months as other developers refer to the output from these deliverables to create their own chains.
Advancing Optimism Anonymous Community and Governance Tooling.
Delegate Mission Request Template
Delegate Mission Request Summary:
This Mission focuses on testing and generating accessible implementations of ZK primitives to enhance privacy within the Optimism Ecosystem. The goal is to create implementations and test behaviours in low-risk, publicly verifiable governance and community interactions. The successful application in these initial scenarios will set the stage for integrating these privacy-preserving solutions into more critical, high-stakes implementations within the ecosystem.
S5 Intent: Intent 3 - Improve the Consumer Experience
Proposing Delegate: -
Proposal Tier: Ember Tier
Baseline grant amount: 8.000 OP per applicant
Should this Foundation Mission be fulfilled by one or multiple applicants: up to 4
Submit by: To be set by Grants Council
Selection by: To be set by Grants Council
Start date: - March 2024
Completion date: 3 months from the start date of the project
Specification
How will this Delegate Mission Request help accomplish the above Intent?
ZK is eating the world, and Optimism would benefit from generating more End User applications that can introduce OP Communities and Governance Participants to this technology. By developing tools that promote fair, candid, and balanced discussions, this mission will contribute to a more effective and equitable governance process.
Therefore itâs necessary to address these issues through the use of new privacy preserving governance applications that can lead to:
- Anonymous Feedback gated to specific Attestation holders (ex. Badgeholders) only
- Anonymous Whistleblowing gated to specific Attestation holders only
- Anonymous Voting gated to specific Attestation holders only
- Gated groups based on Optimism ecosystem IRL attestations & interactions
By implementing these tools and systems, the mission will contribute to building a higher level of trust, credibility and quality process within the Optimism governance framework and set the building blocks to enhance and provide privacy preserving governance processes.
What is required to execute this Delegate Mission Request?
This Delegate Mission Request will leverage:
-
EAS as an attestation layer for identity & credentials
-
Semaphore groups as industry-standard for anonymous ZK groups
-
Bandada as an easy-to-use UI & credential aggregator to lower the entry barrier for creating flexible anonymous groups, and finally
-
Privacy Preserving Governance Applications: that will be built in this Mission Request
Applicant teams must proof experience in web3 development using: addresses, messages, attestations, building with APIs.
Conceptual ZK knowledge to generate and verify a proof, knowledge on how to use SDKs and packages (Bandada o Semaphore) no need to be familiar with circuit creation.
Specific use case/community in mind, detailed scope on who would be using this application: hypothesis to be tested and expected outcomes of their use.
Technical Development:
- Design and Development of Applications: Building user-friendly web applications for governance and community engagement on the Optimism network.
- Initial âHappy Pathâ: 1) user connects wallet 2) if they are a badge holder, allow them to vote, give feedback, whistleblow
- These applications should be flexible enough so that they support other attestation-enabled groups like: RetroPGF recipient, previous badgeholder, delegates, etc.
- Integration with Bandada and EAS: Ensuring seamless integration to leverage the privacy and security features of Bandada (Semaphore) groups, along with the attestation issuing capabilities of EAS.
Community Engagement and Education:
- Outreach Programs: To educate the community about new tools and their benefits.
- Feedback Mechanisms: Implementing systems to gather user feedback for continuous improvement of the applications.
Testing and Deployment:
- Beta Testing: Conducting thorough testing phases to ensure reliability and user-friendliness.
- Deployment on Optimism Network: Ensuring the applications are fully compatible and optimised for Optimism Mainnet and/or testnet.
Documentation and Support:
- Comprehensive Documentation: Providing clear documentation for both users and developers so other communities or projects that can benefit from these builds can fork them and reuse them.
- Ongoing Support and Maintenance: Establishing a framework for regular updates and user support.
Governance and Reporting:
- Transparent Reporting: Regular updates to the community and stakeholders about the progress and impact of the applications.
- Collaboration with Governance Bodies: Working closely with Optimismâs governance system for alignment and support.
- Sharing learnings on the development process, user experiences, and adoption for the Optimism Ecosystem to learn and build upon.
Note: Semaphore & Bandada teams from Privacy Scaling Explorations team (EF) have committed to provide as much technical guidance and support needed for builder teams to successfully complete this mission and leverage anonymous groups infrastructure and integrate them into new governance or community applications. Semaphore is an OG Public good in the ZK space.
How should the Token House measure progress towards this Mission?
- Development Milestones:
- Initial Design and Concept Approval: Date by which the initial design and concept for the applications are approved.
- Prototype Development Completion: Target date for the completion of the first functional prototype of the applications. This should have initial UI and basic mocked APIs.
- Integration and Testing Phases:
-
Bandada and EAS Integration Completion: Deadline for successfully integrating the applications with Bandada(Semaphore) and EAS.
-
Alpha Release: Scheduled date for the alpha release, focusing on core functionalities.
-
Beta Testing Launch: Date for initiating beta testing, involving a select group of users to evaluate the applicationsâ performance.
-
Beta Testing Feedback Review: Deadline to review and analyze feedback from beta testing to make necessary improvements.
3. Deployment and Rollout:
- Optimism Mainnet/Testnet Deployment: Specific date for deploying the applications on the Optimism Mainnet and/or Testnet.
- Public Launch: Target date for the public release of the applications, post all necessary testing and refinements.
- Community Engagement and Education:
- Community Outreach Program Launch: Date for starting community outreach and educational programs about the new tools.
- Feedback Collection Initiation: Deadline for implementing feedback mechanisms to gather continuous user input.
During this mission it is expected for teams to provide:
-
Monthly Update Submissions: Regular bi-weekly updates to the Token House through the governance forum, detailing progress, challenges, and next steps.
-
A final report on learnings from the challenges faced in the adoption of this technology within the Optimism Ecosystem and suggestion for other communities looking to re-use this build.
How should badgeholders measure impact upon completion of this Mission?
- Number of unique users using the new applications.
- Number of unique interactions in these apps
- Amount of new anon-relevant groups created via the application
- Quality and quantity of feedback received from elected govNERDs, badgeholders and OP communities
- Quantity of incidents reported via the whistleblowing tool: Track the number and nature of incidents reported, assessing the effectiveness of the whistleblowing tool.
- Feedback from Badgeholders on their perceived ability to have more candid discussions (regardless of their tenure in the ecosystem) based on new interaction methods available.
Have you engaged a Grant-as-a-service provider for this Mission Request?
No.
Has anyone other than the Proposing Delegate contributed to this Mission Request? @LauNaMu and Andy from PSE
Hi Jon!
The development of an Impact Evaluation Framework (IEF) has already been funded and completed in the last season and was used by Badgeholders for project evaluation: you can find it here.
In addition, the Grants Council has a Milestones and Metrics Sub-Council that was created for this Season, whose job is to evaluate grant recipients milestones and deliverables. This mission would seem redundant work and I would suggest to look to collaborate with them in this front, since they will be building this piece of grant evaluation infrastructure.
Would be great to read though where what you suggest differs from what has been previously created to avoid redundancy. Thanks for sharing this proposal, Impact Evaluation is definitely key to progress in Governance.
Thanks for the response LauNaMu!
Can you point me to where I can connect with the Milestones and Metrics Sub-Council?
Hey all! Weâre looking for a top 100 delegate to sponsor our mission request. If there are any questions, please feel free to reach out, and thanks for reviewing.
Mission Request: Create Videos about Optimism
Delegate Mission Request Summary:
This mission seeks to create entertaining and educational videos that draw people into the Optimism Collective. The aim is to raise awareness for Optimism, make it easy for mainstream audiences to get involved, and inspire the next generation of leaders in the Superchain.
S5 Intent 4 - Improve Governance Accessibility
Proposing Delegate: Looking for a delegate
Proposal Tier: Ember
Baseline grant amount: up to 7,000 OP per application to accomplish the mission
Should this Foundation Mission be fulfilled by one or multiple applicants: Multiple
Submit by: To be set by Grants Council
Selection by: To be set by Grants Council
Start date: ASAP
Completion date: Mission must be completed within 12 months
Specification
How will this Delegate Mission Request help accomplish the above Intent?
The Delegate Mission Request for creating educational videos aligns with the intent to Improve Governance Accessibility by focusing on three key areas:
-
Community Education: The videos will serve as a vital tool to educate the broader community about Optimismâs governance and RetroPGF, using clear and engaging narratives that resonate with a wide audience.
-
Fostering Community: The videos can combine educational content about governance with other topics that interest viewers, which can help provide a welcoming atmosphere where more people are inspired to fulfill their goals with the Optimism Collective.
-
Simplifying Complexity: The mission is designed to distil the complexities of Optimismâs governance system into simple content, making it easier for newcomers to understand how they can participate and make informed decisions.
In essence, this mission will provide an accessible entry point for community members to engage with and contribute to Optimismâs governance, promoting inclusivity and understanding.
What is required to execute this Delegate Mission Request?
To execute this Delegate Mission Request, the content creator will be responsible for the following:
-
Knowledgeable Expertise: Stay updated on Optimismâs developments and demonstrate strong presentation skills
-
Alignment with Optimismâs Vision: Uphold and convey Optimismâs principles in all content
-
Video Production Proficiency: Possess necessary video production skills, such scripting, editing, and hosting.
-
Strategic Content Research: Research and organize content on pivotal topics within the Optimism ecosystem
-
Social Media Promotion: Actively promote videos across social channels like Twitter and Farcaster
Expected Deliverables:
- A series of educational and engaging videos that provide insights into Optimism governance and RetroPGF.
- Regular updates and posts on social media platforms to promote content and engage with the community.
- Reports on engagement metrics, viewer feedback, and the effectiveness of educational efforts.
How should the Token House measure progress towards this Mission?
The Token House can measure progress towards this Mission by reviewing the following resources provided by the content creator:
-
Links to the platform where the videos are published (such as Zora or Youtube)
-
Monthly video analytics such as viewership, impressions, and NFT mints (via onchain interactions, spreadsheet, or other resources)
-
Links to social media channels where there is engagement on the video (such as comments, likes, and bookmarks on Farcaster or X)
-
A summary of how the videos help Optimism to make it easier for the Token House to understand the impact without having to watch every video. This summary can include details of how the videos resulted in key governance metrics, such as delegated OP, activity on the governance forum, and participation in community events.
The content creator can set milestones regarding the date of video delivery, amount of videos published, amount of views, amounts of mints, amount of governance participation, and other engagement metrics.
How should badgeholders measure impact upon completion of this Mission?
To assess the impact of this Mission, badgeholders can focus on any of the following metrics:
-
Key Video Analytics: Overview of video content metrics such as total views, click-through rates, conversion rates and more
-
Supplementary Content Engagement: Total downloads, views, and mints of additional resources (e.g., free guides or NFTs) linked in the videos.
-
Community Queries: Total count of inquiries to the content creator about Optimism Governance and the Collective.
-
Onboarding Proof: Number of new wallets set up following the video content, indicating successful onboarding.
-
Contributor Tracking: Documented contributions from those newly onboarded, reflecting active participation (such as joining Optimism Fractal events or completing Layer3 Quests)
-
Feedback Summary: Analysis of a brief feedback form filled out by viewers and/or ecosystem participants.
-
New Conversations: Track the number of governance-related posts, and discussions initiated by participants post-onboarding.
These metrics can provide a clear, time-efficient method for badgeholders to evaluate the Missionâs impact. In addition, badgeholders can also use the metrics that the Token House uses to measure the positive impact of the Mission.
Have you engaged a Grant-as-a-service provider for this Mission Request?
No
Has anyone other than the Proposing Delegate contributed to this Mission Request?
This Mission Request was created by myself and @DanSingjoy
Wondering if the IEF should be an iterative process the same way RPGF is? It might be useful to have this continuously evolve, especially if every iteration includes contributions from people/ teams with more diverse skillsets.
I think you did a great job on the IEF btw, just thinking if it should stagnate or be open to continuous improvements.
I fully believe that the IEF should evolve and iterate with each Season.
I also believe that, in line with other iterations in the Collective, the goal is to build on top and take the learnings to inform future work (rather than starting with a blank slate if a base already exists).
The IEF is open for community improvements and changes, as all other Public Goods are. I would love and welcome for others to iterate on it and build new end-user facing applications of it.
Thanks again for the context/comments. I think naming it IEF was a mistake but perhaps what I am proposing can be revised as an iteration on the existing IEF?
My intent was to support the existing tools and build upon them not completely reinvent the wheel. This may not have been clear from the proposal. I believe Deresy can be a valuable tool as the collective iterates on IEF v1. I can definitely reach out to the Milestones and Metrics Sub-Council if they are tasked with refining the IEF you established.
I have another idea as well. How do you feel about a mission Request for the end-user dapp? I can see many grants programs benefitting from a front end that allows the current IEF, or various models of it to be implemented for measuring and funding impact. I know a few projects that would be interested in applying for this.
A Mission request for the end-user dapp would be a great approach, for both Grantees and Grant Operators emphasizing on design and accessibility since that is where projects struggle the most (based on the research Iâve completed in the OP Ecosystem).
Also, I think @Carlosjmelgar made a good point, and I will make a proposal to update the original IEF.
For the initial proposal you made, I believe trying out a series of different approaches to Evaluation is good. There is no one right solution and through testing different approaches weâll get to better outcomes. My recommendation here would be to 1) modify this proposal so that, in line with the design of Mission Requests at this stage, any evaluating platform (several which have contributed to Optimism before too) can apply to complete it (such as Karma, Thrivecoin, etc). If not modified now, this will probably modified later on in the process as Missions are meant to be general and not tailored to one project. 2) Increase the number of projects that can be awarded this mission to ensure we get to that diversity of approaches, it looks like the budget youâve suggested of 40k OP could already accommodate that expansion in number of selected builders.
Hello @Rosmari!
In the last season @dmars300 and Cryptoversidad did a great job creating educational videos about Optimism. I think future applicants should take previous content and boost it to spread awareness about the collective without repeat tasks.
Also I suggest to take a deep dive into Impact Evaluation Framework and Metrics Garden to select better impact metrics that further support the collective.
Update: IEF link broken, now itâs fixed
Looking for a Top 100 Delegate to Sponsor this Mission Request
Hacker Houses for the Superchain
Delegate Mission Request Summary:
Hacker houses are nice initiatives to provide initial training or bootcamps, aiming to promote the development and seed innovative projects, especially if they are associated and organized just before large events (Eth-Denver, Eth-Rio, Eth-Barcelona etc) and/or Hackathons. Hacker Houses make a lot of sense when talking about blockchain and Optimism Superchain and having as the main goal onboarding many new devs and seeding dozens of new projects at the Superchain.
S5 Intent Please list the Intent your Request aligns with here:
2 - Grow the Superchain
Proposing Delegate: Delegate name/pseudonym, linked to delegate profile
Proposal Tier: Please specify the Tier required for Mission Applications under this Request (ie. applications must be submitted by teams at the Fledging Tier)
Ember Tier
Baseline grant amount:
3000 OP for each proposal, a total of 9000 OP
Should this Foundation Mission be fulfilled by one or multiple applicants: Select from: âOne,â âUp to Xâ or âMultipleâ
Up to 3
Submit by: To be set by Grants Council
Selection by: To be set by Grants Council
Start date: TBD
Completion date: If applicable. Please note Missions must be completed within 12 months (i.e. marked as done
).
12 months
Specification
How will this Delegate Mission Request help accomplish the above Intent?
(Please explain alignment with the relevant Intent)
By engaging in the Hacker Houses, Optimism can stimulate developer growth on the OP Mainnet and across the Superchain. This involvement will provide the basis for unique contract deployments and interaction, a key metric for measuring the success of the Superchainâs growth. By supporting Hacker Houses new and regional use cases will be identified and seed. Furthermore, by providing the needed training and support for the initial development of new applications and solutions relevant to diverse communities, the Hacker Houses will be also enhancing the overall ecosystemâs innovation and reach.
What is required to execute this Delegate Mission Request?
(Please list responsibilities and/or expected deliverables)
- Number of Hacker Houses: 3
- Hacker House: documentation related to lectures, workshops and coding will be generated and organized for each proposal
- Alignment with Ethereum Ecosystem: In case of multiple partnerships for the Hacker Houses.
- Organizational Experience: Evidence of the ability to successfully host such events.
- Community Engagement Strategy: Plans for attracting and engaging a diverse group of developers
- Impact Metrics: Clear metrics for measuring the Hacker House contribution to Superchain growth, eg new contracts at OP mainnet and Superchain
- Post-Event Strategy: Follow-up plans for ongoing project support or integration into the Optimism ecosystem, encouraging Hacker House participants to submit their projects for funding at OP Grants, Gitcoin, Giveth, etc.
How should the Token House measure progress towards this Mission?
- These measures should focus on progress towards completion. Including expected completion dates for each is recommended
- Please be as specific as possible in defining measures of progress so that Token House delegates can accurately track execution
Hacker House Application Receipt:
- Measure: Count of applications.
- Deadline: End of each Hacker House.
Event Execution:
- Measure: (i) Successful Hacker House execution as scheduled. (ii) Documentation generated/updated
Post-Event Reporting:
- Measure: Submission of detailed post-Hacker House reports.
- Deadline: 1 month after Hacker House has ended.
Impact Review:
- Measure: Comprehensive assessment of missionâs impact on Superchain growth.
- Deadline: 3 months after Hacker House has ended.
How should badgeholders measure impact upon completion of this Mission?
- These measures should be focused on performance and may be used by badgeholders to assess your Missonâs impact in the next round of RetroPGF
- Please be as specific as possible in defining measures of impact so that Citizensâ House badgeholders can accurately measure the grantâs impact
Pre-cohort Milestones:
- Application Volume: Number of applications received for each Hacker House.
- Organizer Preparedness: Evaluation of logistical and resource readiness.
Post-Hacker House Milestones:
- Event Execution Success: Assessment of Hacker House execution and participant feedback.
- Project Initiations: Count of projects started during the Hacker House.
Ongoing Impact Measures:
- Projects Deployed on Superchain: Total unique GitHub repositories related to the Hacker House.
- On-Chain Attestations for Demoed Projects: Implementation of attestations for projects presented at the Hacker House.
- On-Chain Recognition for Hacker House participants that joined all activities: Issuing attestations or NFTs to acknowledge participants.
Have you engaged a Grant-as-a-service provider for this Mission Request?
If so, please disclose the details of this arrangement, to the extent possible.
No
Has anyone other than the Proposing Delegate contributed to this Mission Request? If so, who, and what parts of this application did they contribute to?
No
RetroPGF for any DAO
Delegate Mission Request Summary:
This mission proposal aims to create resources that allows any DAO, team, or community to run OP style RetroPGF Rounds.
This democratizes OP style RetroPGF so that any DAO can do it with their own token. We want other DAOs to be able to use it + easily follow the convention of RetroPGF Optimism, but also be able to configure it for their own needs.
S5 Intent : 4 Contributions that
- Educate the broader community about Optimism governance and RetroPGF
- Increase the resiliency of core governance infrastructure
- Create user interfaces to interact with governance programs.
- Create transparency and accountability for governance participants
Proposing Delegate: TBD
Proposal Tier: Eagle Tier
Baseline grant amount: 133,700 OP
Should this Foundation Mission be fulfilled by one or multiple applicants: One
Submit by: To be set by Grants Council
Selection by: To be set by Grants Council
Start date: March 2024
Completion date: First cohort within 6 months, second cohort within 12 months.
Specification
This mission proposal aims to create resources that allows any DAO, team, or community to run OP style RetroPGF Rounds.
This democratizes OP style RetroPGF so that any DAO can do it with their own token. We want other DAOs to be able to use it + easily follow the convention of RetroPGF Optimism, but also be able to configure it for their own needs.
Democratizing RPGF is important because
- It spreads the knowledge of how to actually design RPGF rounds (as opposed to just LARP about it on twitter).
- It creates more shots on goal for trying things (as opposed to just having theories about what might work)
- More funding for more public goods builders. That means more blockspace consumed (we will push people to use OP mainnet) + positive brand impressions for Optimism.
- It will create learnings about how to do RetroPGF that could then add value back into the Optimism ecosystem.
- RetroPGF will become a movement wherein RetroPGF rounds will feed other RetroPGF rounds, ultimately creating bottoms up signal about impact=profit in other DAOs.
How will this Delegate Mission Request help accomplish the above Intent?
- Maintaining the repo for a consumer facing dapp
- Creating a community of practice around it
- Running 2 training programs.
- Moderating the telegram channel
- Creating content about best practices.
- Supporting people who run EasyRetroPGF Rounds
What is required to execute this Delegate Mission Request?
- Weâve got the following in house already.
- 2 Program Managers
- 2 Educator
- 2 Developer
- Support channels for anyone interested in running RetroPGF rounds and trainees
How should the Token House measure progress towards this Mission?
- These measures should focus on progress towards completion. Including expected completion dates for each is recommended
- Progress reports on the forum through a Mission Communication thread
- Case Studies from each organization running a RetroPGF round
- Please be as specific as possible in defining measures of progress so that Token House delegates can accurately track execution
- How many rounds were run? How much capital was deployed?
- Round Manager Training Program run - did the program run?
- Round Manager Education - was 6 pieces of content about best practices created?
- Did any learnings inform the design of Optimism RetroPGF rounds?
- Case studies from each community running RPGF rounds?
How should badgeholders measure impact upon completion of this Mission?
- How many rounds were run? How much capital was deployed?
- How much blockspace was consumed on OP mainnet or superchain chains?
- Case Studies
Have you engaged a Grant-as-a-service provider for this Mission Request?
NO, but the initial EasyRetroPGF.xyz build was created Optimism Foundation RFP 104 and 106
Has anyone other than the Proposing Delegate contributed to this Mission Request?
No. But the software/thinking behind this proposal has been shaped by
- Kevin Owocki
- Scott Moore
- Linda Xie
- Lefteris
- Carlos Melgar
- Optimism Foundation
This proposal has also been shaped by years of Gitcoin/Optimism alignment. We have always felt very mission aligned with Optimism. Here are a couple data points.
- OP/GC have similar missions regarding public goods.
- Plasma Group (the corporate predecessor to Optimism) raised money on Gitcoin Grants during round 1, 2, and 3.
- Plasma Group were some of the earliest funders of the Gitcoin Grants Matching Pool.
- Gitcoin donors were rewarded in OP Airdrop 1.
- Optimism was one of the first L2s that Gitcoin Grants Stack supported.
- Iâve done a handful of greenpill episodes with members of Optimism.
- https://publicgoods.network/ (a L2 for supporting public goods which Gitcoin has helped to seed) was built on top of OP Stack + is part of the superchain.
- Iâve participated in the OP Onchain summit in Istanbul, and weâve also done public speaking together at Schelling Point (on multiple occasions).
- Weâve commissioned custom art about Ethers Phoenix.
- In RPGF Round 3, we build the round3.optimism.io interface for the OP collective.
Mission Name:
Making Impact Evaluation Accessible
Delegate Mission Request Summary
Update and expand the Impact Evaluation Framework based on the new intents set for Season 5 and diversify access to the Metrics Garden through new interfaces. This will increase the adoption of existing Impact Metrics and leverage existing and new tools to demonstrate impact, enhancing the collectiveâs ability to identify and support impactful contributions.
S5 Intent
This Request aligns with Intent 4:
- Educate the broader community about Optimism governance and RetroPGF
- Increase the resiliency of core governance infrastructure
- Create user interfaces to interact with governance programs.
- Create transparency and accountability for governance participants
Proposing Delegate
TBD
Proposal Tier
Fledgling Tier
Baseline Grant Amount
30k OP per team, with additional rewards to be received via RetroPGF based on impact/outperformance.
Should this Foundation Mission be Fulfilled by One or Multiple Applicants
Up to 2 teams.
Submit by
To be set by Grants Council.
Selection by
To be set by Grants Council.
Start Date
March or as soon as the Council selects teams.
Completion Date
Within 2 months after the start date.
Specification
This Delegate Mission Request will update and expand the Impact Evaluation Framework in line with Season 5âs intents, making Optimismâs governance more accessible and understandable. It includes creating a new interactive interface for the Metrics Garden and hosting bi-weekly live sessions to guide projects. This will result in more impactful contributions, improved RetroPGF applications, and a better voting experience for Badgeholders.
Key Responsibilities and Deliverables
- Deliverable 1: Updated Impact Evaluation Framework based on Season 5âs intents.
- Deliverable 2: Stand-alone, interactive, and open-source website hosting the updated Framework.
- Deliverable 3: A set of 8 evaluating criteria with defined scales per intent, composable across intents.
- Deliverable 4: Awareness Roadmap and feedback tracking from the live sessions.
- Deliverable 5: Live interactive interface for the Metrics Garden.
- Deliverable 6: Report on learnings and improvements in the execution of this Mission and User Needs identified from both Applicant projects and Badgeholders.
How Should the Token House Measure Progress Towards this Mission
Weekly updates in the governance forum, with the following table tracking milestones, titles, deliverables, due dates, and evidence of completion:
Milestones | Title | Deliverable | Due Date | Evidence of Completion |
---|---|---|---|---|
Milestone 1 | Framework Update | Updated Impact Evaluation Framework based on Season 5âs intents | [Specify Due Date] | [Link to updated framework] |
Milestone 2 | Interface Development | Stand-alone, interactive, and open-source website hosting the updated Framework | [Specify Due Date] | [Link to the live website] |
Milestone 3 | Criteria Formulation | Set of 8 evaluating criteria with defined scales per intent, composable across intents | [Specify Due Date] | [Documentation of criteria] |
Milestone 4 | Community Engagement | Awareness Roadmap and feedback tracking from the live sessions | [Specify Due Date] | [Summary of feedback & roadmap] |
Milestone 5 | Metrics Garden Accessibility | Live interactive interface for the Metrics Garden | [Specify Due Date] | [Link to the interface/proof of integration] |
How Should Badgeholders Measure Impact Upon Completion of this Mission
- Number of projects applying to RetroPGF4 with an Attestation for using the Metrics Garden.
- Increase in the creation of on-chain impact data as per Metrics Garden descriptions.
- Quantity and Quality of user feedback results from interactions with the website.
- Number of Badgeholders using the composable evaluating criteria during RetroPGF4 voting as reported by Badgeholders.
- Quantity and Quality of Badgeholder feedback on quality of applications participating in RetroPGF4.
Have You Engaged a Grant-as-a-Service Provider for this Mission Request
No
Has Anyone Other than the Proposing Delegate Contributed to this Mission Request
Proposal was generated by @LauNaMu
Note: @LauNaMu will support any of the teams that execute this Mission for 2 hours per week if needed.
Hi there, Iâm willing to sponsor this, EthCC is a great event with the perfect audience to spread the good word about Optimism. Let me know if the proposal is ready for me to repost.
Hi @brichis I have seen you like my Open Source OP Stack Developer Tooling mission request, it would be a pleasure if you help sponsorship this mission.
Crowdsourcing useful verifiable data.
Delegate Mission Summary:
Crowdsourcing verifiable data about the constituent components of Web3 will significantly enhance discoverability and trust at the user interaction layer. This enhancement improves the Web3 customer experience by simplifying decision-making, making it easier for users to understand and engage with our extremely complex ecosystem. By offering users accessible, community-sourced insights, we will make Optimism the most user-friendly and easily navigable choice in this field.
S5 Intent: Intent 3 âImprove the Consumer Experienceâ
Proposing Delegate: TBD
Proposal Tier: Ember
Baseline grant amount: 300,000 OP total (maximum individual applicant grant size 125k OP, or 41% of the grant pool)
Should this Foundation Mission be fulfilled by one or multiple applicants: Up to 5 applicants, with the expectation that requested grant size will be in proportion to scope size.
Submit by: To be set by Grants Council
Selection by: To be set by Grants Council
Start date: To be set by applicant
Completion date: Before December 31, 2024
Specification
How Will this Delegate Mission Request help accomplish the above intent?
The âcrowdsourcing useful verifiable dataâ mission is a strategic initiative aimed at enriching the consumer experience within the web3 space. Achieving this will require multiple efforts working along side each other.
Some may choose to build ambitious protocol level primitives that empower developers and users by introducing generalized attestation and querying, while others may focus on more niche use-cases such as reputation features intended to enhance Optimismâs âTrust Tiersâ. Folks may also build specific social applications or gamified platforms that encourage the collection and curation of verifiable data in the form of an open knowledge graph, such as which smart contracts are safe to interact with and which token contracts may be dangerous.
These aforementioned examples are designed to provide context to the mission and spark creativity, and are not designed to pigeon-hole developers into a handful of ideas.
What is required to execute this Delegate Mission Request?
The successful execution of this Delegate Mission Request requires a RFP selection process that can evaluate technical proposals. Moreover this Delegate Mission Request will need to attract technical teams with strong design fundamentals.
Below is a generalized list to consider should this Delegate Mission Request be lucky enough to receive RFPâs down the line. It should be understood that âcrowdsourcing useful verifiable dataâ can take many forms and responsibilities/deliverables should be adjusted proportionally. Generally speaking, we think it prudent to attract builders that have the ability to technically forecast and roadmap.
Listed responsibilities and/or expected deliverables:
Technical roadmap
⢠Design and publish a comprehensive technical roadmap that details the methodologies for crowdsourcing useful verifiable data. The roadmap should specify the types of data to be gathered (application features, social interactions, security, reputation metrics, etc). Additionally, the roadmap should illustrate understanding and application of a generalized product development lifecycle. The roadmap should encompass stages from initial concept development to final deployment, ensuring a structured and efficient progression of the project.
Smart contract design and development
⢠High level plans for how smart contracts will be used to verify information and how data will be stored.
⢠RFPâs should make it clear if they already have smart contract development resources or are planning to source development resources should they be accepted.
Smart contract audit & testing
⢠Builders whose contracts involve advanced logic, sensitive data, or financial operations should anticipate the need for contract audits. Furthermore, it is important to clarify whether a team has prior experience with such audits or if they will require guidance in this process.
⢠Pass at least one third party audit if deemed necessary.
⢠Deploy the contract(s) on Optimism.
Open developer API development and deployment
⢠RFPs should clearly outline the core features of their API that will be accessible to other developers. This includes providing details such as the programming languages in which the API will be available. Emphasizing these high-level functionalities is essential for effective communication and collaboration.
⢠Publish the API and accompanying developer documentation.
⢠RFPâs should make it clear if they already have API developer resources or are planning to source development resources should they be accepted.
End user GUI design, development, and deployment
⢠RFPâs should include a list of core end user features expected to be included in the GUI - wireframes are acceptable.
⢠Deploy and test end user GUI to ensure that functionality is reliable.
⢠RFPâs should make it clear if they already have design and development resources or are planning to source resources should they be accepted.
How should the Token House measure progress towards this Mission?
We hope to work closely with Token House to finalize how to measure progress toward this mission, and have summarized our proposed path forward below. Essentially, we suggest dividing the process into three distinct phases. Successful completion of each phase would unlock OP from the Delegate Mission Request pool.
Phase 1: Planning & Design (25% of total grant received)
This phase can be generally considered complete after the awarded RFP team provides:
⢠Product development roadmap, showing the milestones to be achieved between now and the product launch date.
⢠Low fidelity front end designs or wireframes.
⢠Backend infrastructure schematic.
⢠Mission memo, a 1 - 2 page written document that establishes the teamâs north star to help with consistent internal decision making. The document may include a why, what, how breakdown for the product, a mission statement, and pervasive design and development ethos.
Phase 2: Development (50% of the total grant received)
This phase can be generally considered complete after the awarded RFP team provides:
⢠A staging environment to interact with frontend design.
⢠Operational smart contracts on testnet.
⢠API developer documentation along with functioning API.
Phase 3: Testing & Deploying (25% of the total grant received)
This phase can be generally considered complete after the awarded RFP team provides:
⢠3rd party smart contract audit passing results (if applicable).
⢠Demonstrate internally developed successful tests for smart contract functionality.
⢠Deploy on mainnet.
How should badge-holders measure impact upon completion of this Mission?
Given that Intent #3 is centered on enhancing the consumer experience, we propose the use of metrics that specifically track consumer usage. This should include both developer and end-user engagement, as both groups are key consumers of useful verifiable data.
Developer Usage
⢠How many subsequent applications are using verifiable data infrastructure in their own application design?
⢠Has the introduction of crowdsourced useful verifiable data introduced new features and use cases to subsequent application developers?
End user usage:
⢠How much verifiable data has been crowdsourced?
⢠How many user wallets are submitting or verifying new data?
⢠How many user wallets are accessing/reading data?
⢠How many user wallets are interacting with applications that have integrated crowdsourced verifiable user data?
I support this message!
Any delegates interested in this one? Have a bunch of thoughts here & think we could make this super impactful; very happy to closely collab.
is your expectation that you would be administering this program?