• © Goverland Inc. 2026
  • v1.0.1
  • Privacy Policy
  • Terms of Use
GitcoinGitcoinby0x393BC37ea5493233D2bDC68FD59Dd97Ee01B18Cfdeltajuliet.eth

GG20 Eligibility Criteria - Community Rounds

Voting ended almost 2 years agoSucceeded

This Snapshot vote serves to ratify details of the eligibility criteria for the Gitcoin GG20 Community Rounds. You can read the full proposal here: https://gov.gitcoin.co/t/review-gg20-eligibility-criteria-community-rounds/17846/11

TLDR: How to get a “Community” Round Approved Identify the Round Operator and at least two other partner team members who will be reviewers and/or be involved in managing the round.

Every round must raise their own matching pool (no minimum)

The round should align with Gitcoin’s Mission and Essential Intents 3

All rounds must comply with Gitcoin’s core rules, which include no fraudulent activity, no quid pro quo, hate speech, or other activities out of alignment with Gitcoin’s essential intents.

Show proof of funds in a multisig (similar to how anyone can view the funds in Gitcoin’s multisig)

We highly recommend that proof of matching funds and any further plans for funds raised by communities be provided by the time applications are in review. This will help council members review applications more easily.

In the proposed new structure, we will create a dedicated pool of funds (up to $125K quarterly) available to support “matching on matching” pools. Communities with any amount raised for matching and meeting the round criteria can apply for up to $25K in funding from Gitcoin to go toward their matching pool. The GG20 Community Council (a Gitcoin DAO-elected external council) will proceed to review applications and vote on which communities to fund in the upcoming round.

Off-Chain Vote

Yes - Approve with this criteria
5.31M GTC99.9%
No - Amend this criteria
2.97K GTC0.1%
Abstain
280.03 GTC0%
Quorum:213%
Download mobile app to vote

Discussion

GitcoinGG20 Eligibility Criteria - Community Rounds

Timeline

Feb 25, 2024Proposal created
Feb 25, 2024Proposal vote started
Mar 03, 2024Proposal vote ended
Nov 04, 2025Proposal updated