Season 6 Elections: Developer Advisory Board
Developer Advisory Board Members will be elected by the Token House in Special Voting Cycle # 23 b, which runs from June 13 th - June 19 th at 19 : 00 GMT.
At least one representative of OP Labs, or other Core Devs, must be on the Board in order to ensure coherence with roadmaps, etc. This representative will continue to be appointed by the Foundation. All other members must be elected.
Those that would like to nominate themselves for these roles must fill out the below template and post here 46 by June 5 th at 19 : 00 GMT.
Anyone is able to self-nominate at any point, but there is no guarantee to be an election until a budget renewal proposal passes a Token House vote on May 29 th.
The Foundation will facilitate a town hall 9 with all eligible candidates the following week, before elections take place.
Here you’ll find the governance-approved Season 6 Developer Advisory Board Operating Budget.
Representatives should only serve in one elected position per Season. There are no term limits for representatives, but they may be implemented in the future if the need arises.
There is no minimum voting power requirement to be a Member but the Foundation has recommended the following eligibility criteria:
History of development in the Optimism and/or Ethereum ecosystem
Deep understanding of developments in the Optimism ecosystem
Ability to read and write code and to assess protocol upgrades
Ability to dedicate sufficient time fulfilling member responsibilities
While less critical than the above, the Foundation also suggests the following qualifications:
Experience with security and or auditing
Experience evaluating technical grants (examples include, but are not limited to, evaluating grants for the Ethereum Foundation, ConsenSys, and/or other protocol grant programs)
You may consider whether all layers of the stack are represented by membership (the application layer, the protocol layer, etc.)
Developer Advisory Board Self-Nomination Template
Please keep your answers as concise as possible while conveying all relevant information.
If you are a delegate, please provide the link to your delegate profile:
If you are a delegate, please indicate what % of votable supply is delegated to you: (voting power can be referenced here 1 )
If you are a delegate, please indicate your voting participation rate in OP governance to date: (You may link to your profile on Karma 2 , if applicable.)
Please link to your voting history and any voting rationale you’ve shared: (You may link to your Snapshot and/or Agora profile for voting history. You may link to your delegate communication thread, or any other medium you use to communicate with your delegators, to share your voting rationale.)
Are you a representative of OP Labs:
Please elaborate on your technical background. Please include information about the layer of the stack you have the most expertise on:
Please demonstrate any non-Optimism experience you believe is relevant to this role:
Have you previously served in a representative (appointed or elected) role in the Collective? If so, please specify which:
Please outline your contributions, and their impact, to the Optimism ecosystem to date:
Please describe your philosophy on what makes a good Mission Application:
Please demonstrate your ability to explain complex technical topics to a non-technical audience:
Please disclose any anticipated conflicts of interest: If you are a top 25 delegate in another ecosystem, hold an elected position in another DAO, and/or are a multisig signer in another community please disclose here.
Please verify that you understand you may be removed from this role via the Representative Removal proposal type in the Operating Manual 2 :
Are you interested in the Ops Lead or Upgrade Czar roles? If so, please share relevant experience and one idea you have for how the role could contribute to the collective.
Please verify that you understand KYC will be required to receive Council rewards at the end of Season 6 :
Please verify that you are able to commit ~ 20 hours / month to Board operations:
What Does This Mean for Delegates?
Reviewers will be elected via approval voting in Special Voting Cycle # 23 b (full details in the Season 6 Reflection Period Guide.) Approval voting is a mechanism that allows each delegate to vote for as many nominees as they choose with equal voting power. The nominees with the highest percentage of approval votes will be elected to the Council. Please note this policy in Optimist Expectations:
In the case of approval/ranked choice elections, delegates may vote for themselves, so long as they also cast votes for the remaining elected positions.
Example: I can vote for my own candidacy on the Growth Experiments committee, so long as I also cast 4 additional votes (a total of 5 votes, as there are 5 open positions on the sub-committee.)
Please note the above outlined voting mechanism is subject to change depending on Council structure and number of eligible candidates.
