Gitcoinby
umarkhan.eth
Ratify the Results of GG20 and Formally Request the Community Multisig Holders to Payout Matching Allocations
The GG20 final results have been shared and discussed in the governance forums and are ready for a vote to ratify.
GG20 saw a number of exciting developments including a $1M OSS matching pool across four tightly-scoped rounds, the election of a grants council, an upgrade to our core protocol, and a deepened partnership with our friends at Arbitrum.
We implemented a two-pronged sybil resistance strategy. We used a pluralistic variant of QF and we used Passport’s model-based detection system. We did not do any closed-source silencing of Sybils/Donors. Instead, we’re solely relying on our mechanism and Gitcoin Passport. We've shared links to access both the underlying code and data used to arrive at these calculations in our forum.
We ask our Community Stewards to ratify the GG20 payout amounts as being correct, fair, and abiding by community norms, including the implementation of Connection-Oriented Cluster Matching, and Passport scoring.
More details and the final results can be found in the governance forum post: https://gov.gitcoin.co/t/gg20-program-round-matching-results/18816
Options to vote on:
-
Ratify the round results You ratify the results as reported and request the keyholders of the community multisig to payout funds according to the GG20 final payout amounts.
-
Request further deliberation You wait to ratify the results and request keyholders of the community multi-sig wallet to delay payment until further notice.
-
Abstain
Off-Chain Vote
Loading…
- Author
umarkhan.eth
- IPFS#bafkreia
- Voting Systemsingle-choice
- Start DateMay 23, 2024
- End DateMay 28, 2024
- Total Votes Cast4.94M GTC
- Total Voters1.64K
Timeline
- May 23, 2024Proposal created
- May 23, 2024Proposal vote started
- May 28, 2024Proposal vote ended
- Apr 29, 2025Proposal updated