[Discussion & Feedback Request] Gitcoin Program Beta Round Eligibility

Introduction

The Gitcoin Program Beta Round is the second set of Gitcoin Program QF rounds that will run on the new decentralized Grants Stack. The planned dates for this round are April 25th to May 9th and there will be 5 Core Rounds each with a distinct matching pool:

  • Climate Solutions
  • Ethereum Infrastructure
  • Web3 Community & Education
  • Web3 Open Source Software
  • ZK Tech

As we continue our efforts to decentralize and shape the new Gitcoin Grants Program, these rounds were chosen from a larger pool by the community through a Snapshot vote.


Note: There will also be a number of externally operated Featured Rounds that run in this same 2-week window; the details of which are still being determined.

The purpose of this post is to outline the general eligibility policy that ALL grants must meet in order to qualify for acceptance into any of the 5 core rounds. In addition to the general eligibility, grants must meet the extra criteria for the round they are applying for. The description of each specific round’s eligibility criteria is listed after the general eligibility policy.

The PGF team is asking DAO contributors, stewards, and community members to carefully read these eligibility requirements and provide feedback or engage in an open discussion where needed. The requirements are subject to change but will be locked in before the application window opens.


Gitcoin Program General Eligibility Policy

This policy is set and enforced by the FDD & PGF workstreams of the GitcoinDAO and is ratified by the GitcoinDAO stewards. The following are not permitted in Gitcoin-operated rounds:

  • Hateful Content - No racist, sexist, or otherwise hateful speech, no discrimination
  • Deceiving Users - Malicious content that could cause harm or unintended consequences to users
  • Falsification - Any type of hacking to falsify a contribution is prohibited. No encouraging or enabling Sybil attacks or other forms of malicious manipulation of the grants platform or the Gitcoin community
  • Fraud & Impersonation - Claiming to be a brand or person you are not. The Grant owner must be directly affiliated with the project, the funds must go to the project, and be used for the purposes stated in the Grant’s details
  • Quid Pro Quo & Bribery - The Grant may not have any form of quid pro quo that has financial value (a scenario in which a user gets some additional unique benefit/award in return for their donation)
  • Advertising - Using grants to showcase something you are selling like a token sale or NFT drop
  • Well-capitalized projects - Not have prior external funding of over $500k USD via venture capital, token launches, or NFT sales
  • Grantees cannot be subject to sanctions, and funding cannot be used in violation of any applicable law, rules, or regulations (for example those addressing sanctions, financing of terrorism, and anti-money-laundering)
  • Grantees can be eliminated from consideration in the round if they are found to be encouraging or enabling Sybil attacks or other forms of malicious manipulation of the grants platform or the Gitcoin community.

Additional criteria that projects must meet:

  • Project Update - If you are a returning grantee, you must provide an update on what work has been accomplished since the last grant round your project received funding from
  • Verified Github (if applicable) and/or Twitter account

Web3 OSS Round Eligibility

To qualify for the Web3 OSS round, in addition to meeting the criteria outlined in the program policy above, grants must:

  • Be an open-source project with meaningful Github activity in the prior 3 months that has demonstrated work completed towards the project’s mission
  • Primarily focused on developing on top of or advancing the broader Ethereum and/or Web3 industry

Ethereum Infrastructure Eligibility

  • The Grant must be in support of, or directly advancing the Ethereum ecosystem. This includes areas like:
    • Core client devs (e.g., geth / nethermind; prysm / lighthouse)
    • Tooling providers (e.g., hardhat / ethers.js)
    • Those showcasing the power of critical ecosystem ideas (e.g., dark forest with zero-knowledge proofs)
    • Those doing the hard work of educating developers (e.g., Austin (Gitcoin) / Nader (DeveloperDAO))
  • The Grant must be open source (if software-related)

Climate Solutions Round Eligibility

  • Projects must be at least 3 months old. Newer projects should establish themselves and submit to the next round.

  • The Grant must be primarily focused on climate solutions (the group may do other work but the grant proposal should be directly related to climate solutions). The proposal should explicitly outline how this project will help reduce GHGs or is an important core infrastructure for web3 climate solutions.

  • Grantees who received funding in previous rounds should report on project progress since GR15 or the Alpha round. We understand that some projects may have less progress given the timing of Alpha round disbursements. This will ensure accountability to supporters and also help encourage contributors by showing what you’ve been accomplishing.

  • All returning grantees are expected to update their proposal, in addition to project updates the proposal should include lessons learned from previous work and how they will use the additional funding from the upcoming round. The updated proposal should indicate how additional funding will help the project meet its goals, and include a rough timeline for the project overall.

  • There is a general expectation that projects are within the “realm of viability”.

    • Even if a project may be at a very early stage, it still must seem credible to the average person with an understanding of web3 technology and climate solutions.
    • Grantee founders must genuinely intend to build the project, and the project must not broadly be considered an impossibility.

Web3 Community & Education Round Eligibility

The Web3 Community & Education Round is a new category that has not been a Gitcoin Program round in the past; however there have been similar ecosystem rounds called ‘Media’ and ‘Community’.

Reflecting on the Alpha Rounds and all the legacy “Main Round” grants, there were many great projects that couldn’t join OSS due to specific “active OSS repo” requirements. In GR12 and before we had mutually exclusive categories like “infrastructure” “dapps” and “community” - and this would be like the old community category, which included podcasts, newsletters, educational projects, journalists, and more.

As we’ve now split open-source software into its own round, we will run this Web3 Community & Education Round to focus on non-software related projects that are helping to push the Web3 space forward.

The requirements to be accepted in this round are outlined below*:

  • The project must be focused on improving the Web3 ecosystem.
  • Examples of projects which may fit are those that are:
    • Growing new communities
    • Providing educational resources
    • Creating content (youtube tutorials, newsletters, blog posts, podcasts, etc)
    • Protecting users by investigating bad actors
    • DAOs focused on socialization
    • Onboarding new users
    • Working on inclusion/diversity/advocacy

*Note: As this is a new Core Round category, we’d love to have the community weigh in and narrow the scope or suggest more objective criteria.


ZK Tech Round Eligibility

  • The Grant must be in support of, or directly advancing the ZK tools, libraries, community, or protocols.

  • The Grant may not have any form of quid pro quo that has financial value (a scenario in which a user gets some additional unique benefit/award in return for their donation)

  • The Grant owner must be directly affiliated with the project and the funds must go to the project.

  • The Grant should be focused on accomplishing the following for ZK:

    • Usability - improving the user experience of zero-knowledge tools/libraries, not zero-knowledge rollups. This could also be technical education and documentation.
    • Tooling - improving the developer experience or making it easier to develop applications utilizing zero-knowledge proofs or technology.
    • Applications - technical implementations of zero-knowledge proofs and circuits, not simply applications built on top of zero-knowledge roll-ups.
  • The project should not have its own token or have raised VC funding (let’s keep the funds for the aspiring projects!)

  • The project must have been active in the last 3 months - social media and GitHub.

  • The project should have demonstrated either concrete progress, or evidence of a substantive technical roadmap that clarifies how ZK technology will be used and advanced.

  • The Grant deliverables should be open source.


Conclusion

These eligibility requirements are designed to ensure we capture and provide funding to the highest quality projects in each category. As a reminder, the requirements are not yet set in stone and we are highly encouraging the community to discuss what makes sense and what could be changed. Thanks for reading this far and stay tuned for more updates!

11 Likes

Really great to be discussing this topic! Two questions:

  1. For the general eligibility criteria that reads: “Well-capitalized projects - Not have prior external funding of over $500k USD via venture capital, token launches, or NFT sales.” Does this include having received over $500k USD in funding from grants including the sum of past Gitcoin grants rounds?
  2. Can a grantee apply & participate in more than one round if they meet the criteria of each? Related to this: Can a grantee apply/participate in a Core Round and a Featured Round?
8 Likes

I love these questions! Thanks for posting them. I was wondering a similar question on multiple rounds.

FWIW, I think the way the tech works, donors would need to contribute to the grant in each round. ie, contributing to the grant in a core round would not automatically enable matching in a featured round (as currently built).

3 Likes

Thanks for putting this together so quickly @koday! Glad we’re getting ahead of this and also glad we’re working to crowdsource opinions. I’m not sure we can really do a formal snapshot vote on the many various criteria and limitations, however, it would be INCREDIBLY helpful to get more input from the community: Stewards, grantees, donors, etc.

Some topics I’d love others to weigh in on, not all mentioned in the main post:

Multiple entries - Should one single grant be allowed in multiple rounds? Multiple core rounds (ie. OSS and Eth Infra)? A core and a featured round (ie. OSS and DeSci)? Can/should we as Gitcoin even moderate featured round reviews and approvals?

And on a similar wavelength - should a single person be allowed to have multiple different grants in the same round? Should they be allowed to have multiple different grants in different rounds? Is this really enforceable in an “anon-friendly” platform?

Quid Pro Quo - We’ve always had issues drawing the line here. Does a POAP count as QPQ? Does a Discord role count as QPQ? We’ve tried to draw the line at “monetary value”, but we’ve also seen things like POAPs act as incentives even without “value” - and of course, we get into potential airdrop speculation/farming territory.

NFT “sales” or drops have also been a bit of a gray area - would love to hear what others think about this.

Matching caps - are they good? Should they be higher? Lower? Removed altogether?

And in general, should we aim to be more strict on approvals to better curate quality projects, or be more lenient and trust the “wisdom of the crowd”? Should brand new projects with little history be allowed in, or should we aim to check and verify past work and some level of prior progress? The issue is we don’t want to discourage new ideas and prevent funding from getting into the hands of very early creators, however, we’ve also had many issues with “grant emulations”, or essentially, projects that look “legit enough” but in reality were just totally made up for the sake of farming donations.

I’ve found the community often has tons of opinions on criteria after a round is over, but ideally, we can start fixing these issues proactively :slight_smile:

6 Likes

Hey Connor - I love how we are working on codify the criteria. As we continue to grow, it would make sense to clarify how round eligibility changes over time (how and by whom). This clarification will help us avoid future disagreements.

I think that with the community input that @koday is seeking here, once the comments are integrated, it would not be a hard step to formalize an update process. I am adding this question to our D-RACI chart (to be shared shortly) as work to be done, which I am happy to help work through.

1 Like

Hey Connor! An aspect of Gitcoin that I find especially fascinating is the support for very very early stage projects. I’ve been working on science for 40 years+ and support of early ideas is something we must fix in TradSci to advance the human knowledge. I do believe this is an area that Gitcoin excels. Regarding ‘grant emulations’, we might be able to use some tools like Passport or Holonym in order for people to have the matching funds? Projects’ owners would still be allowed to apply :grinning:

2 Likes

Thank you Connor!
Cheers
Maria

Multiple entries – think it’s very fair for projects to fall under multiple categories, but think we should have an application process to be able to get funds from any additional round, or max cap to avoid people trying to abuse the system. Maybe in the future we can even weight it, so like the 1st pool a grantee is in has the most matching potential, and it halves in any additional round they get approved for, to give the most relevant grantees priority.

For multiple grants, I’m with you on the enforceable aspect lol. We could “strongly suggest” focusing on one grant per season. But someone can realistically have varying levels of responsibility in different projects, & seems hard to make a judgement call. For me, the potential for fraud outweighs this multi-grant scenario. IMO at least for Beta, we should place a limit of 1 per grantee (to the best of our control).

POAPs seem ok-ish to me if they’re not openly offered upfront, Discord roles feel a little weirder. Are we evaluating this just based on what grantees say in their applications, or are we/the public also auditing them during/after the process?

Don’t like Gitcoin funding NFT drops, but can imagine exceptions with less typical use cases–e.g. such as using grant funding to teach an underrepresented population like how to empower themselves creatively, releasing an NFT collection to further this cause. Giving NFT’s a soft no for Core Beta Rounds, just due to optics and abuse potential.

Matching caps = good :slight_smile: Keep for sure! No opinion on higher/lower

In general: my vote is to be more strict to curate quality projects. Know that our whole schtick is being decentralized af, but grants programs literally anywhere else on this planet are way more stringent, with good reason
 free money lol. As we narrow our public goods funding focus by reducing to 5 Core Rounds (which the community gets to decide) while branching out to wider cases with featured rounds, more eyes (and attacks) are going to be on us. Our teams are leaner now, & we literally don’t have as much manpower to identify donation farmers once they’re thru.

If my responses seem conservative, it’s because Partnerships works hard on a tight schedule to secure grant round support every single quarter :face_with_spiral_eyes: & it is really not easy in this market, so let’s do what we can to ensure it’s only going to the right places–would rather not work to line the pockets of scammers, even just a little bit lol :pensive:

Love that we’re fine-tuning the eligibility with these questions before the round happens! Thanks for kicking this off @koday :raised_hands:

4 Likes

Hi all!

From my perspective one project should be only on one core round, while there should be no limit related to Featured rounds.

2 Likes

A couple ideas to aid grantees in knowing who is eligible and how best to position themselves for the round–

Web3 OSS Round Eligibility

  • I get the sense that this has been unclear, and different grantees have provided different levels of detail in their updates.
  • Per request of many community members and supporters: quantitative updates are much appreciated. We would love to see the measurable impact you’ve had, via the metrics of success you use to guide your product. Example: “Shipped new code,” does not help us. Better: “Shipped 2 new features and gained an average of +20% new discord members month over month since product launch.”

Ethereum Infrastructure Eligibility

  • I would advocate that this round be subject to the same criteria as OSS: the project must have been in operation for 3+ months prior to submission for the grant. Any less time than 1 quarter means it’s very difficult for our communities to judge the legitimacy of the public good contribution offered

  • I would also specify/clarify that we will want an update of material progress for those grantees who are returning. Again- we <3 a good quantitative metric


Excited for this new category! I know we’ve excluded a ton of amazing work in this space for difficulty in determining which communities are “public goods” and we’ll be excited to let this get decided democratically!

As far as eligibility goes, I would suggest that we ask grantees for this particular round to include any and all social channels that they use to reach their audience, along with audience size. Bigger != better with nascent projects in this space, but this for me is similar to our github requirement: we want to see that you are building. This also gives us an opportunity to share your channels with supporters who can discover you when the grant round opens!

Another thought as we grow into our protocol-led future: for ZK Tech Round Eligibility it would be amazing to take a couple community volunteers who are familiar with ZK to perform technical audits. If you’re interested- please reply here to post your desire to help with this!


And a final point in response to @connor’s post above:

Since we are moving to on-chain protocol underwriting for every piece of the grants process, our protocol must treat individual project wallets for the sake of measuring support for matching eligibility. This is not only the auditable, technically sound solution, but also simply more fair.

In the spirit of giving a platform & giving pre-pre-seed funds to as many new and upcoming projects as possible, it is my belief that we should allow only 1 project per team. Thank you @GoretiFreitas for lovely summary here and +100 to our amazing ability to find and support the super, super early folks!

While we can see you on-chain :eyes: shifting your money through multi-sigs (and we will use more and more on-chain signals to establish grantee reputation), I think we want to trust here that projects not abuse this space to present the same project as if it were actually several public goods contributions, when it is in fact the same project in new clothes
 While you are building amazing open source software that we’d love to fund, your blog talking about that software is not a public good :sweat_smile:, nor is your discord server, nor is your merch shop
 in my humble opinion
 Let’s keep it classy out here, folks.

It is my suggestion that for the beta round, each project is able to join 1 and only 1 of these 5 core rounds; but can be considered automatically for inclusion in any of our amazing partner-matching featured rounds.

I’d love, love us to explore a dynamic process like the one @juanna suggests for the future!

1 Like

Hey thanks for this.

So lots of thoughts and questions in here.

Multiple projects per round

By this we mean I guess, an org having multiple grants for multiple of their subprojects in as many different rounds as possile. This should not be allowed. The organization behind the grant should be identified and if the same, then disallowed to have multiple grants in different rounds to maximize return.

Otherwise we are all incentivized to split our grants into smaller subprojects. I for example could split a part of rotki that deals with infra of the ethereum network and put it in infra and the rest of the opensource app in opensource. And double dip.

Others can do the same. Then it becomes a mess.

Quid pro quo

I really dislike even POAPS and discord roles for donations. Why? Because it’s neither about POAPs, neither roles. It’s about the expectations of future airdrops.

Through the years we have been using gitcoin at rotki people are constantly coming and asking for a discord role because they donated. I explain to them this is not possible, due to quid pro quo rule and also that a discord role would not mean anything.

As the conversation with the user progresses, it always, without fail ends up in one thing. They want the role/POAP as a way to count eligiblity for the future token drop they are sure we will do.

Funding

  • Well-capitalized projects - Not have prior external funding of over $500k USD via venture capital, token launches, or NFT sales

I am one of the people who talk about well funded projects not being eligible. But this sounds a bit too broad. It depends on a lot right? So when did they raise the money? What if they raised a small seed in 2018 and it’s all spent now and they are 100% community based and open now? What’s their burn rate? What’s the team size? etc.

It can get really, really complex really fast. I am afraid I don’t have a good answer as to how a proper rule should look like. It’s more like, every time a well capitalized project tries to use gitcoin, it’s obvious to all and there is community pushback. But don’t know how to codify that in a fair way that won’t exclude projects. Have had talks with many projects like Umbra, dappnode and more about fairness here and it’s very hard to codify it.

3 Likes

Thanks @koday for this. And to all for the good input. To your request about further defining Web3 Education - * Providing educational resources:

Do workshop series / a book doing a deep dive into one subject or discipline or one community demographic meet the definition for inclusion?

I would argue “no” for this. Disclaimer: As a long time grantee, I do not meet this criteria, but others may. If true, this is a change to the current way things work, and deserves more discussion.

1 Like

I would argue very strongly against this. Not only that, I would add an item to the general requirements so that a single group of people (physical human beings) not present more than one project.

In the past, some groups have presented five or six separate projects for the same exact people. This does not seem fair to me.

One might argue that they are cannibalizing their own potential, but I think more likely people do it to unfairly increase their grant income, particularly if they don’t disclose that the projects are affiliated. If not banning this outright, then perhaps there should be a requirement that they disclose it’s an affiliated project. (With a proviso that if found later to be affiliated, they are disqualified.)

1 Like

No. They shouldn’t. It may not be enforceable, but you’all could require that grants disclose that the multiple projects are affiliated and, if later, it’s found out that people did not disclose this, they could be disqualified.

2 Likes

Heavy +1s to @lefterisjp and @tjayrush on their further comments on the multiple-entries per project question. Well said on both counts :clap: And I would go so far as to question whether many members of our community were even aware that this was happening or was habitually attempted
 glad we’re getting it cleared up now.

Re: Well-capitalized projects

I appreciate this. And while it can get a bit murky- I’m optimistic on a transparent way forward.

To add clarity in terms of the way we can start to assess grantee reputation as a community - let’s specify that opening a funding round of any size wherein the project/company/DAO in question sold off shares or promised dividends in a formal agreement with investors will show up on a financial audit. As we happily have grantees from all over the world, some countries may document this in differing ways, and bylaws of investment cycles vary, but in any case where publicity exists announcing ongoing funding raises, we will want to consider this criteria for non-inclusion. I think this should feel like “graduation” more than a penalty :upside_down_face: should you have been so lucky as to catch the eye of the traditional investment world.

So - I advocate this criteria in the spirit of prioritizing pre-pre-seed projects, but also out of respect for our stalwart projects who have disdained formal funding due to concerns of competing priorities that would sacrifice their open source mission or the integrity of their solution.

In future rounds, we can get more specific about on-chain inflow/outflow expectations to qualify a fair playing ground amongst projects of different maturity levels - again- using always public data and signals to perform any checks and balances.

I agree that this is a significant change which might surprise some folks if we were to implement after a quick forum discussion


What we can do is improve the availability of real (and on-chain audited!) grant award totals so that we (Gitcoin) and our partners (anyone running their own round), our grantees and their supporters can see the true amount of funding achieved through Gitcoin Grants Program over time. As we start making these numbers more widely available, I hope the discussion will continue to evolve. Perhaps we see supporters prioritize the lesser funded grants of their own accord, or perhaps we start cohorting projects so that those more mature are in their own camp to compete for matching funds, and those newcomers have a distinct matching pool to draw from
 I imagine some grants program partners may have their own ideas about a cap or cut-off for previous grant funding - so allowing them to make their own criteria seems crucial to me.

Thanks to everyone for all these excellent thoughts and considerations! Thanks to @koday for ensuring these conversations happen in public!!

1 Like

Thank you for opening this discussion.

As an active contributor in the Web3 Education and community category, I really appreciate this being a separate category in the beta round. I suggest adding these requirements:

  • Projects should add data on it’s viewership such as demographics, age, onchain history etc in order to better gauge groups being targeted via content being developed
  • Sorting projects who have verifiably created onchain activity via it’s viewers or subscribers. Further choosing top ‘x’ projects via this method.
  • For projects which produce multi-lingual content, add a third party verification of translation or original content in the criteria. This third party can be trusted members within the community who speak/read/write the language.
  • Allow projects which proliferate web3 culture or create cultural artefacts