Hello, I am running to keep my place on the Grant Council, which recieved an NPS of 9.3 last season. I am proud of the work I’ve done there – and of the directions I’ve helped guide it in – and would like to continue this work.
Council sub-committee: Optimism mission reviewer
If you are a delegate, please provide the link to your delegate commitment:
https://vote.optimism.io/jackanorak.eth
If you are a delegate, please indicate what % of votable supply is delegated to you: (voting power can be referenced here ) 1.94%
If you are a delegate, please indicate your voting participation rate in OP governance to date: (You may link to your profile on Karma , if applicable. If not, you can divide the number of Optimism votes under your Snapshot profile by 87, which is the number of Token House votes through Season 2, and add a possible 2 votes from Agora.)
85% (100% since posting a delegate commitment)
Please link to your voting history and any voting rationale you’ve shared: (You may link to your Snapshot 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.)
[Jack anorak - delegate communication thread ](https://Communication thread)
Do you have a technical background? If so, please elaborate:
I’m technical right up to the point of the actual software engineering of protocols. Conversant in code and design. Deeply involved in quantitative protocol construction and am credibly ‘technical’ in defi. Regularly code to extract insights and perform actions onchain.
Have you previously served in a representative role in the Collective? If so, please specify which:
I was on the shadow committee, which was an unofficial committee that I believe made valuable contributions.
I was then on the Builder Grants subcommittee of the Grant Council, which I’m currently rerunning for.
Please outline your contributions, and their impact, to the Optimism ecosystem to date:
- Integral contributor to Velodrome’s design and launch, with coordination of OP Labs
High level of contributions to OP governance as delegate, commenter, grant council member
Aided in the onboarding of some 70-odd protocols to Optimism, made introductions, advised on optimal product and liquidity strategy
Advised several OP protocols as they applied for governance grants
Published Optimism’s first review of passed grants, which was directly responsible for making builder grants in scope for Governance.
Leading most comprehensive retrospective of OP grants to date, which has already surfaced major insights and revelations of protocols’ handling of OP: Received RPGF for this
Was voice influencing major changes in direction of grants, including the implementation of the Grants Council itself, requests for grants, increased focus on builder grants, and the developer advisory board
Please describe your philosophy on what makes a good Mission Application:
I believe in a structured approach, where the council articulates where OP is and where it wants it to go. It should outline what sorts of people, teams, and activities are needed to get to this desired future, and it should shape and approve grants that get Optimism those people, teams, and activities.
Grants should be designed with justifiable, measurable, and achievable objectives, and they should be reviewable periodically so that the Grants Council can guide them and retain the ability to withhold future grants. They should be scaled appropriately to the objectives (and the objectives’ value to the ecosystem), not to the projects’ size or perceived importance.
Although there is room to take a slight shotgun approach, grants should go to the projects that are most promising in their domains. This requires the Grants Council to have an informed opinion about the likely winning teams in each space.
Just like the best tools are multifunction tools, the best grants will have second-order benefits affecting the largest number of builders. That is, you fund the project that makes other projects more achievable. This is how you accelerate ecosystems.
In the course of a grants program, major things might change. This is crypto. So the grants council should also allow for some opportunism in approving grants.
Please demonstrate any experience you believe is relevant to this role:
I am a builder and have gone through the process of going from zero to a major ecosystem player, building something while facing a threadbare budget, maximum skepticism, and vocal detractors. My team has gotten an OP Labs Grant and an OP governance grant and I believe raised the bar on applying for and reporting on grants of this nature.
As a delegate, I’ve voted on grants, and as a member of the Shadow Committee, I’ve helped to push people’s thinking on what grants ought to be used for.
As a Grant Council member, I pushed for a more proactive stance on what sorts of grants we want to give out and introduced a new level of rigor to our selection process.
As an individual, I’ve proposed ecosystem-wide initiatives rethinking how Optimism manages its resources, and I’ve staked much of my career in crypto on making Optimism succeed.
In short, I’ve experienced virtually all tasks and perspectives that could go into the construction of grants, and there’s little in the way of subject matter that I haven’t personally worked with, from crosschain messaging to staking to security to NFTs.
I’ve now also been on the Grant Council and have an intimate understanding of how it works and how processes will improve next round.
Please demonstrate expertise relevant to your Council sub-committee: (if applicable)
I chose to apply for builder grants instead of growth experiments for three reasons.
- I already have a track record of independent voting and have advised my delegators that I would always vote and argue against Velodrome’s immediate interest if it was in conflict with what I thought was best for Optimism. That said, it seems that perceived conflicts of interests are less pronounced in this group; more growth experiments are likely to touch velodrome than builder grants.
- This vertical also plays well into my day job, which has me doing a lot of outreach to builders. In this capacity, hopefully it’s not a stretch to say I’ve likely spoken with more active and prospective builders on Optimism than anyone outside of the OP Foundation. In this way I can help guide builders to the program and get the initiatives we’re looking for.
- I think builder grants at this stage are more critical for the long-term viability of the Optimism project; there’s a lot of exciting stuff that OP is going to roll out that the builder community needs to be prepared to exploit.
What types of Mission Requests do you think will help achieve the Season 6 Intents?
Please refer to a thread I wrote some time ago on what sorts of grants I"d like to see.
Top of mind remain a generalized price oracle, audits/bug bounties to support innovative applications, and proofs of concept highlighting the OP stack, Account Abstraction, and new forms of lending (especially with staked ETH).
That is, we want to fund the things that let builders know that we can offer the best ecosystem to work in, the best tools to work with, and the best funding to derisk experimentation.
Please disclose any anticipated conflicts of interest:
If I am elected, I will review grants that could have a material impact on Velodrome. As I did last season, I will make clear to my subcommittee when a grant seems to be in Velodrome’s area.
They will attest that, as before, I’ve consistently voted in Optimism’s interest, even when doing so would be against Velodrome’s immediate interests. I do so because I want Optimism to win, and in any case I see Optimism’s success as more necessary for Velodrome’s success than any individual grant.
Please verify that you understand you may be removed from this role via the Representative Removal proposal type in the Operating Manual : Yes
Please verify that you understand KYC will be required to receive Council rewards at the end of Season 6: Yes
Please verify that you are able to commit ~20 hours / week to reviewing grant applications and other Council operations: Yes. To date, this role has required more than 20 hours/week.