Allo Protocol S17 Workstream Budget Proposal
During Season 17, the GPC workstream (Gitcoin Product Collective) has decided to split into two workstreams: Gitcoin Allo which is focused on the continued development of our Grants protocol and stack, and Gitcoin Passport which is focused on our Passport protocol and stack. Splitting GPC into two workstreams will allow for a more “complete” team structure in the future. This will allow for a more “complete” team structure in the future. @nategosselin and @kevin.olsen will be workstream leads for this workstream (h/t to @kyle for his assistance getting this initial draft up and running).
We are focused on a number of the Essential Intents. Specifically the following two:
- Protocol Adoption + Growth
- Financial Sustainability
This season the Allo workstream will be focused on transitioning from alpha to beta, with Eth Denver as a key milestone and inflection point. At a high level, we will be focused on three key themes:
- Finish Protocol v0 — finalize the payouts interface and build our first payout mechanism so that there is an end-to-end protocol flow
- Engage the developer community — with the foundational protocol complete, we will ramp up our DevRel efforts and work on getting external teams building on Allo
- Productize QF on Grants Stack — Enabling communities to run Quadratic Funding rounds is a major opportunity for protocol adoption and growth. We want to make running QF rounds to be truly self-serve for non-technical operators on Grants Strack. We received great feedback during our alpha rounds and will continue building solutions to that feedback this season.
Based on what we learned in Season 16, we recognize the need to continue being nimble with our development roadmap so that we can quickly adapt to the needs of the market. This season’s roadmap will likely change month-to-month as we get feedback, so our objectives read more as high-priority user needs than concrete features.
For more context regarding our vision, the current state of the workstream and more please refer to the Workstream Notion Page. This page has not been updated to reflect the new workstream structure at time of writing, but you can find details on our vision and what we are building towards.
Gitcoin Allo (GA) is requesting $803,533 for S17. A breakdown of the budget can be found at the end.
|Gitcoin Season||Season 15||Season 16||Season 17|
1) The amount of GTC requested and the value of the reserves will be adjusted based on the current market value at the time this proposal is moved to Tally using the lower of the current price or the 20 day moving average, whichever is lower.
Objectives and Key Results
Milestone Report for the past Season
Success / completed / shipped
Incomplete but will hit goal and/or priority changed for initial description
Incomplete, will not hit goal (see description for reasons why)
Canceled (see description for reasons why)
|Round Operators can run a Quadratic Funding round on the protocol||NO||Ran 5 Alpha rounds (UNICEF, Fantom, 3 Gitcoin Alphas) + 2 simulated quadratic funding rounds|
|Round Operator can run a Quadratic Voting round on the protocol||NO||The team did significant scoping and discovery but, in consultation with other workstreams, ultimately decided to deprioritize QV in favor of remaining focused on QF, Alpha round support, and payouts work|
|Round Operator can execute payouts on the protocol||NO||The team originally planned to have this completed by Eth Denver, despite including it as a milestone on our S16 budget. We are still on track to build this by the launch in Denver.|
|Donors can browse and assess the projects in a round||NO||All alpha rounds mentioned above used the Explorer front end designed for this experience. The Gitcoin Alpha rounds also included a first integration with Passport for Sybil Defense.|
|Project Reputation||NO||Our workstream had multiple S16 milestones that were effectively the same problem: enabling project reputation. The Grants Hub team spent significant time exploring the problem area of users bringing project reputation to other protocols, but ultimately learned that this was not an immediate need. Given these learnings, we’ve refocused on an Allo-specific funding use case for project reputation and will be working on that area in S17.|
Objectives and Key Results
As mentioned above, we are tracking three key themes for Season 17. Given the need to be nimble, we will primarily use a monthly roadmap for how we translate those themes into development work. In February we are focusing on three high-priority needs for launch (payouts, repo refactor, and application flow improvements). We will share an updated Season 17 roadmap in the coming weeks and update it on a monthly cadence as our plans crystallize.
Note: at this stage of development we have yet to establish baseline metrics for our products. We plan to establish our core metric portfolio and begin measuring baselines this season. Our goal is to transition to metrics-lead objectives in future seasons. For now, we have left metrics blank and instead focused on likely focus areas.
List of S17 OKRs
Finish Protocol v0
Complete the payouts interface so that end-to-end funding programs can run on Allo Protocol.
|Protocol||-||- Finalize payouts interface
- Build bulk payout mechanism
Engage the developer community
Ramp up our DevRel efforts to begin getting developers building on the protocol.
|Protocol||-||- Refactor repos into easy-to-use Allo repo
- Improve Documentation, Legibility, DX
- Partnership and Project Incubation (likely focused on allocation mechanisms + payouts)
Productize QF on Grants Stack
Enabling communities to run QF rounds is a major adoption and growth opportunity for our products. We want to remain laser-focused on the feedback we heard during the Alpha rounds and build a first-class QF grants exerpeince.
|Stack + Protocol||-||- General iteration on Alpha round feedback
- Improve Application experience for Operators + Grantees
- Improve project review flow for Operators
- Improve and enrich the explorer experience for donors
- Enable new verified credentials so that projects can accrue reputation (including KYC)
We have broken the budget down by staffing, contracting, devrel, opex as we feel like this gives fairly granular details into where the funding will be going.
View: USD per Category
|Gitcoin Allo denoted in USD|
|Leadership / Ops||34,865||34,865||34,865||104,596|
|Hackathons & Bounties||5,000||5,000||5,000||15,000|
|Saas Fees (AWS, Datadog, fleek, etc.)||20,000||20,000||20,000||60,000|
|Total GPC Budgeted Spend||268,066||267,733||267,733||803,533|
|60 Day Reserves||535,635|
|S16 Treasury Balance||645,628|
|Total S17 Request||693,540|