[S14 Proposal] dCompass budget request


The dCompass workstream is requesting a total of 110 200$ (19k GTC - $5.8/GTC) for Season 14, which is 2 times less than our previous budget request and it will be the last season that dCompass receives recurrent funding from Gitcoin DAO’s treasury.

The focus for this season will be on:

  • Season 13 catch up:
    • Beta release & deployment on Polygon
    • Onboarding new projects, DAOs and protocols
  • Season 14 goals:
    • Gitcoin quests migration over dCompass
    • Build incentives for quest creators

Milestone Report

Contributors :

  • 3 full-time devs
  • 6 part-time (Alp moving from FT to PT, adding 2 new PT contributors)
    • 1 new dev
    • 1 new token engineer
    • 1 scrum master/PM
    • 1 designer
    • 1 business dev
    • 1 content creator/quest migrator

Funds spent: 16 291 GTC (April spendings included but not yet executed)
Funds carrying over the next quarter: 26 691 GTC
Have the actions of the workstream brought back value into the DAO/treasury ?
Not yet but we do expect to generate value and revenue by the end of Season 14.

Season 13 retrospective
[v] = success [x] = failure

Main goals:

  • [v] Rewarding users going through pathways & quests
  • [v] Alpha release on the Rinkeby testnet and Schelling Point live demo
  • [x] Beta release & deployment on mainnet and Polygon
  • [x] Onboarding new projects, DAOs and protocols

Product goals:

  • [v] Project Sponsor Pass (stake required to submit a project for review)
  • If any, display all the smart contracts of a project
  • [v] ERC20 allocation and distribution for pathway and quest creation
  • [v] Claim ERC20, ERC701 and ERC1155 rewards
  • [v] Public profile page & browse profiles by pathway & quests progress(eg: query all users that completed the Gitcoin Grants 101 pathway)
  • [v] Performance, additional datastore to act as a caching layer such as ThreadDB or PostgreSQL
  • [v] Website (about, features, values, go to dapp)
  • [v] Allow users to choose between use markdown or use the Gitbook integration for pathway & quest guides
  • [x] Smart contract audits, mandatory before going to production and we’d appreciate any advice from the community on our contracts .
  • [x] Beta launch on mainnet and Polygon + research and potential deployment on other scaling solutions
  • [WIP] Responsiveness

Proposal Body

Season 14 Roadmap

Budget distribution


FOR - If you vote “yes”, the dCompass Workstream will get funded for a last season, and the proposed budget above will be allocated to the multisig of the dCompass Workstream 0x756239E5B7D2aa6F3DA0594B296952121Fb71606 and we would work towards a mutual grant agreement post Season 14.

AGAINST - If you vote “no”, the dCompass Workstream won’t be funded by the Gitcoin DAO anymore and the requested budget won’t be allocated.


Hey Huxwell, I want to call out that this really rubbed me the wrong way - “no mutual grant agreement would be created.” Gitcoin has bootstrapped your entire development effort, extended its brand, conference and community for you test your ideas thus far (AFAIK). Putting the point in here that no funding for S14 would have you walk away from that support with no upside to Gitcoin is wild to me.

I wonder if I am miss-understanding what you mean here?

Asking for 19k GTC is relatively small, but dCompass has continually missed outcomes is has stated it would achieve and fails to attract traction (outside of those in Gitcoin trying to support your efforts with paths like Grants and FDD). I believe you are learning an immense amount about why it is so hard to start a project as a technical founder and still make progress on growing/testing your hypothesis, but largely defecting from the Gitcoin DAO does not seem to have paid off.


Echoing the intensity of the YES/NO vote dynamic in terms of relationship and work that has already been done together. As the past couple of seasons’ milestone reports show, the workstream can improve on delivery so a collaborative vs a split approach may be more constructive?

And apologies if I missed this but wasn’t there a plan to work with @kyle on a potential business plan? Or a finer delineation of structure, setup and mission?


Sorry it was a clumsy statement coming from this post, in the context of a failure, why would Gitcoin even bother for a mutual grant ?

But even if we stop getting funded by Gitcoin, we’ll continue to work on the product anyway and I’m confident that we’ll get better and better. So having a mutual grant agreement regardless the outcome of this proposal makes a lot of sense.

This is a great question and something I want to really make sure I spell out. A decision to not fund dCompass (IMO) is not because it is a failure. It would be because Gitcoin needs to focus on the most important thing and cover off spend in areas that are adjacent to its core protocol ambitions.

The work you are doing, the product you are building and community you are growing is not something I would ever call a failure. It may be something that now longer fits where Gitcoin can spend resources though. Hopefully you don’t assume that a decision to not fund in S14 means failure. It could mean instead that its time for Gitcoin to refocus where it invests, and for you to continue to grow and launch to see if you can get traction.

This is great to hear. Thanks for calling that out.


I’d like a clarification on the need to fund dCompass for this quarter as there’s currently more funds carried over this quarter than the requested budget itself.

Can dCompass sustain itself this quarter without requesting for more budget? It does seem possible based on the budget breakdown hence for now there isn’t much need to get funding either.

Thank you!

Yes we could eventually use the funds carrying over this season but then it means that we wouldn’t have any reserve at all when Season 14 ends.
So if the mutual grant agreement isn’t set up by then it means we will be without funds during our product launch… and I think that no one in our workstream would be comfortable with that.

Yes, hence the format that most workstreams have followed thus far is:

Requested Budget + 60-days reserve - current reserves

This will probably suffice for this workstream.

Which would be
19k + 11.4k - 26.9k = 3.5k GTC

*as another note, I don’t think 3000 GTC is enough for smart contract audits

1 Like


I would like some clarification on the goals.

What are some of the bullet points? Any link for more information/explanation?

What is Free quest creation, what is reward alocation etc. ?


As I am writing to the other workstreams I would like to generally tighen the belt for everyone as we are in a bear and we need to ensure the continuing existence of Gitcoin DAO and the completion of its main goals.

But looking at your budget it seems pretty logical. With $6 per GTC and 9 people for 3 months it seems to amount to $3,555 per person per month. Which is a normal salary for us in Europe.

But compared to the other budgets I have seen it’s much smaller. Do I misunderstand something? Is it not 9 people who will be paid their salaries through this?


Sorry about the lack of context, I’ve updated the Season 14 goals with a link to the respective Trello cards with more informations.

I hope that it can help for now but we’ll work on official documentation during S14.

Yes the calculation is pretty much right as an average for the PT & FT contributors. I’d even say that we’re underpaying ourselves if we were to compare with the dev salaries of other workstreams/in the space. But we were fine with that as it reduces our burn rate and helps the project over the long run.

Gitcoin DAO is doing a good job at incubating us!
However, we have bigger needs than what’s on our budget request and I don’t think that it would be healthy to stay as a workstream that keeps requesting more GTC over time while the focus of the DAO seems to be around funding other initiatives.

1 Like

I think dCompass should be moved to a mutual grant. Gitcoin should see upside in the product, but not run it.

That also means not being a workstream which participates in CSDO.

Overall, I’m very supportive of dCompass. I’d like to see them get the funding they need via the mutual grant structure rather than the workstream structure.


Last conversation that we had was to meet up with @kyle and start to plan/design a business plan/roadmap that could be sustainable in the future, have you guys work on that part?

I would personally love to see this project come to life, I do not wish to put any blockers on that but we should look back in time on what is working and what is not at this point and decide if a mutual grant or still being funded by the organization is the right fit.

The gitcoin Flywheel: Learning while earning/meeting and creating more leaders… In that retrospective I am still supporting this project


Jumping in to provide my two cents as I go through all the proposals.

At a macro level, I very much also echo the questions raised about whether dCompass should continue to exist as a workstream in the context of the DAO. While the Trello links are helpful to dive into some of the specific objectives, I believe this budget request lacks context as to the ‘why’ of dCompass & the broader vision it is setting out to accomplish, and how that fits into the rest of the work the DAO does.

Given our focus on Grants 2.0 & becoming a Protocol DAO and my lack of clarity as to how dCompass fits into that, I plan to vote ‘no’ on this budget request. That said, I am eager to explore @DisruptionJoe’s suggestion of evaluating dCompass in a Mutual Grants context.

Finally, if this budget request is indeed pushed forward as a workstream funding request as proposed - to @fishbiscuit’s point, in keeping consistent with the approach of all the other workstreams, I believe the requested amount should be 3.5K GTC, not 19K GTC.


for dCompass,
I have some questions:

  1. what is the goal (could benefit Gitcoin)? - maybe I missed some context.
  2. what is the business model (revenue) after season 14 (or without funding from Gitcoin)?
  3. what is the growth plan? (how to get more projects in and get more quests)



@Huxwell it would be great to have these addressed before the council call happening this afternoon CET

1 Like

This is a great proposal, and a great project… but I have to vote no on this proposal as is… sadly given the current market conditions I don’t think the DAO can take on revitalizing quests :-/


dCompass’ primary mission is to onboard, guide and educate users about trustworthy Web3 protocols and DAOs.

For the recurring revenue, there is a fee for the creation of quests with ERC20 tokens as rewards.

We’re also working on a sponsor pass that might act as a partnership deal.

The growth plan is to reach out to projects with some quests already built for their community and get feedback as well as users.

Did I read this right? dCompass will be renegging on the previously offered governance rights if this proposal is not funded? (see below)

Are you saying that dCompass has no funding options other than GitcoinDAO?

I believe that we shouldn’t be investing in teams that won’t invest in themselves. If dCompass isn’t going to continue without funding from GitcoinDAO, that’s a pretty negative signal to me.

No that’s not what I’m saying! I mean that in the worst case scenario, if we were not able to deliver the MVP in production after season 14, I thought that it would be considered as a failure for Gitcoin DAO and that the community wouldn’t even consider our mutual grant proposal.

I’ve never said that and it seems clear on the conclusion of the same post that you quote above

OK - Sounds Good. Maybe I misread. Thanks for clarifying.

1 Like