---
# System prepended metadata

title: Gitcoin Passport S17 Workstream Budget Proposal

---

# Gitcoin Passport 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. 

Now that the protocols are both live, we feel we should construct each of the workstream teams to focus accordingly. In time, these two teams will run independent of each other. For S17, there will continue to be tight collaboration.

Gitcoin Passport is a billion dollar opportunity to create a truly sybil resistant web experience. We are increasingly of the opinion no one sybil solution will be enough, but we certainly have an opportunity to curb the vast majority of sybil attacks with Gitcoin Passport.


## Essential Intents

We are focused on a couple of the Essential Intents. Specifically the following two:
1) Protocol Adoption + Growth
2) Financial Sustainability

A case can probably be made that we are also focused on growing the Grants program as we will support Sybil prevention, but that is a secondary goal on our long arc roadmap.


## TL;DR

This season the Passport workstream is going to focus on the following outcomes:
1) Continue to grow the number of Passport holders, and the number of communities integrating with passport
2) Introduce and test at least one new scoring mechanism for other communities to consume
3) Create a first class developer experience for those integrating with passport (either in app or scoring), and drive the number of integrations up to 25

**Based on what we learned in Season 16**, we will continue to refine infrastructure, strengthen partnerships and take a more thoughtful approach to roadmap planning and feature development. We were just crushed by instability in upstream service providers and so we are making some infrastructure changes to prevent this from happening in the future. We are also going to ensure that we give users the ability to record their passport details on-chain, which will further help reduce the load on key components of our infrastructure.

We have had changes in our team composition in S16; we lost two team members (and had another go out on parental leave). As a result we will focus on building context and team cohesion while rallying around our two sided protocol (one side for passport holders and one side for those who seek to access passports).


> 💡For more context regarding our vision & the current state of the workstream, please refer to the [📄Notion page for Passport](https://www.notion.so/gitcoin/Passport-843e5bfda1ba44f7b9d2cd3cd7059911).

## Amount

Gitcoin Passport (GP) is requesting **291,538GTC = $512,691** for S17. We will be leaving all reserves with the Gitcoin Allo workstream, and as a result we are requesting the full amount of reserves be funded (full 60 days @ ~201k GTC). This means however that the Allo workstream should be requesting less GTC as they will have a relatively large reserve. 

A full breakdown of the budget can be found at the end of this post.

|Gitcoin Season|Season 15|Season 16|Season 17|
|---|---|---|---|
|Season Budget|$N/A|$N/A|$512,691|

*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.*


## Milestone Report for the past Season

**Legend**
🟢 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)


|Initiative/Project|Always-on|Key Results|Value Delivered|
|---|---|---|---|
|Gitcoin Grants protocol is able to use Passport to programmatically identify donors as unique humans|NO|🟢 Passport used in Alpha Rounds|Analysis is needed to confirm the expected result (low fraud tax)|
|Passport has a productized set of scoring methods that meet the use cases of the majority of interested of communities|NO|🟢 Multiple scoring mechanisms developed with FDD|Scoring for alpha rounds, and scorer API|
|Passport and its components are verifiable on-chain so any dApp can integrate passport, verify, and trust the source of passports data/components|NO|🟡 the scoring API is live, passports on not on-chain (outside ceramic)|This has enabled programatic integration of our scoring service|
|Passport holders are able to easily navigate their passports to understand how it could be used across different communities (Research and Design output)|NO|🟡 We have had turn over on the Product Marketing and Product Management roles for Passport, this has slowed down our ability to make progress here|This will make advocates of Passport holders||


## Objectives and Key Results
S17 is going to bring a renewed focus on our product practice to ensure we are intentional in the items we are scoping and building. What this means is, we are going to try and get ahead of the feature development we would like to complete, scope those features on Github, and ensure they are appropriately described such that we can bounty some of that scope if we want to. Essentially, this is the first season where we want to build muscle around inviting outside contributors to help us build functionality that we see as valuable.

You can expect us to deliver on the following next season:
1) Improving the passport holder's user experience by bolstering the education in app and streamlining workflows for stamp verification. 
*(Milestone: Passport Holder User Experience)*
2) On chain passport data / scores. We have found developers want to access this data on chain, and not just through Ceramic.
*(Milestone: On-chain scoring)*
4) Continued infrastructure scaling to ensure we can handle the load of Gitcoin Grants Rounds :sweat_smile: 
*(Milestone: Scoring API Minimum Viable Product)*

We are eager to strengthen our partnership with DevRel and Product Marketing to relaunch Gitcoin Passport in February of this year (updated docs, updated marketing, more education, new website, etc.)

> [You can see some of the progress on the marketing front here](https://go.gitcoin.co/passport)
> (Huge thanks to MMM for leading this work!)

Though we are not defining this as a cmomitted objective, we will also be spending time expanding our GTC Staking use case, and improve that experience. We are seeing adoption of this utility and passport holders are using this as a means to increase their humanity score (for the Gitcoin Alpha Rounds). In time, we want to build out slashing capabilities to create a Sybil hunting microeconomy, thereby rewarding those helping us find and remove sybil actors.

### List of S17 Goals

|Initiative/Project|Always-on|Metrics|Expected Impact|
|---|---|---|---|
|**Protocol Adoption Growth**<br>Improve Passport Holder's User Experience|No|* Increase the number of average stamps a passport holders holds by 10% <br>* Reduce the time it takes to verify stamps by 25% |- Improved usability (especially on mobile)<br>- Improved sentiment of Passport <br>|
|**Protocol Adoption Growth**<br>Improve integratooooors experience|No|* Increase the number of devs integrating with Passport <br>* Improved sentiment of our documentation and developer experience |- Reduction in time required to integrate<br>- More creative and expansive use cases surfaced <br>|
|**Protocol Adoption Growth**<br>Develop a second scoring mechanism for integrators to select from|No|* Multiple scoring methods are used in App |- Diversified use cases for Passport|


## Budget Breakdown
We have broken the budget down by staffing, contracting, devrel, and opex as we feel like this gives fairly granular details into where the funding will be going. This does not currently show the cost for each initiative, but we hope to do this next season with the milestone based bounty work we may be doing.

We kept some budget for hackathons / contractor's work on scoring mechanisms, and also called out Dev Rel uniquely as we expect this to be an expense that **grows** for the DAO in the future. 

Finally, this budget grows slightly over the past season as we added another developer to bring the team to four FT devs (with a fifth on paternal leave right now). Once our developer who is on paternal leave returns, our extra engineer will move back to the Allo workstream. We are thankful for the coverage during the paternal leave.

Our New Multisig for funding the workstream is: [0x19E50fA5623895D5a2976693eaFF5C2F879510ed](https://app.safe.global/eth:0x19E50fA5623895D5a2976693eaFF5C2F879510ed/home) | the signers for this are: Kyle (kbw), Kevin Olsen, Michael, Janine, Annika)

### View: USD per Category

|Gitcoin Passport denoted in USD||||||
|---|---|---|---|---|---|
|Staffing||**2023.02**|**2023.03**|**2023.04**|**S17 Total**|
||Passport Core Contributors|96,751|96,751|96,751|290,254|
||Passport Leadership / Ops|26,147|26,147|26,147|78,435|
|**Total Staffing**||122,897|122,897|122,897|368,691|
|Contracting||||||
||DevOps|3,000|3,000|3,000|9,000|
|**Total Contracting**||3,000|3,000|3,000|9,000|
|DevRel||||||
||Devl Rel|15,000|30,000|30,000|75,000|
||Hackathons & Bounties|5,000|5,000|5,000|15,000|
|**Total DevRel**||5,000|5,000|5,000|90,000|
|OpEx||||||
||Saas Fees (AWS, Datadog, fleek, etc.)|15,000|15,000|15,000|45,000|
|**Total OpEx**||15,000|15,000|15,000|45,000|
|---|---|---|---|---|---|
|**Total GPC Budgeted Spend**||145,897|145,897|145,897|512,691|
|60 Day Reserves|||||341,760|
|S16 Treasury Balance|||||0|
|**Total S17 Request**|||||854,451|

Thanks for the consideration.

