Proposed Transactions (signal only – transactions are manually executed by the Foundation)
// Request 1A: [Alternative CL/EL client Mission Request] requesting 0 OP transfer to 0x42...0042
In Season 5, the Token House will approval rank Mission Requests that work towards our Collective Intents. Mission Requests outline specific initiatives aimed at achieving one of the Intents. Once approved, teams will apply to fulfill each Request by submitting a Mission Application. Below are the Mission Requests under Intent #1: Progress towards technical decentralization.
NOTE: YOU WILL NOT BE ABLE TO CHANGE YOUR VOTE ONCE CAST
This vote utilizes approval voting. Mission Requests will be approval ranked based on the number of yes votes. Each Mission Request must receive a minimum number of yes votes, equal to 51% of quorum. Any Mission that does not receive > required number of yes votes will not qualify for a budget allocation. The top ranked Requests, above the minimum number of yes votes, will be accepted until the Intent Budget runs out. If a Mission would push the Intent Budget over the approved amount, it will not be included. Any Intent Budgets left over will be returned to the Governance Fund. For examples, see How to Vote on Missions Guide.
As a voter, you should vote yes on all Mission Requests you think should be approved, and you should abstain from voting on Mission Requests you do not think should be approved. You can view some guidelines on factors to consider here.
Request 1A: Alternative CL/EL client Mission Request
Request 1B: Decentralized rollup-as-a-service
Request 1C: Fraud Proof CTF Mission Request
Request 1E: OP Stack Research and Implementation
Request 1F: Open Source OP Stack Developer Tooling
In this threshold-based proposal, all options passing the approval threshold of 13.54M OP votes will be executed in order from most to least popular, until the total budget of 1.33M OP runs out. Voters can select up to 6 options. If the quorum is not met, no options will be executed.