Allowlist Configurability - A strategic investment

Thanks to Feems and @DisruptionJoe from ThankARB for pointing this out to me! Thanks to @meglister and @renaobrien for reviewing this doc before publishing!

Allowlist Configurability - A strategic investment

Right now, Gitcoin Grants Stack has a limitation in utility for grants round operators because a key configuration variable (who gets to vote?) is not very tunable.

To do a QF Round on Grants stack I must decide whose votes count in allocating the matching pool. In doing so I must choose between

  1. No Sybil Resistance
  2. Passport > 20

Because there are only 2 options, that means that round managers cannot really tune their capital allocation. If I want to just upload a simple list of Badgeholders, like Optimism does, I can’t do that. If I want to give a specific Hats role in my DAO the ability to do a vote, I can’t do that.

Strategic Investment

We should make this parameter more tunable.

I should be able to configure this very important parameter.

As @meglister pointed out to me, JokeRace does a great job of providing a UX. eg you can upload a lsit of addresses, tokens, criteria like β€œyou have held token for x amount of time”, etc and then those people can vote on the JokeRace. We could perhaps take some inspiration from that.

Some options that seem like no brainers to me:

  1. Configure passport. What if I want to use a non-Gitcoin scorer, or specific set of stamps? What if I want the threshold < 20?
  2. Other options:
    1. Easiest - CSV Upload of addresses I want to be able to vote.
    2. More advanced stuff
      1. Hats role.
      2. Owner of SAFE Multisig
      3. People who have more than x amount of y token (I should be able to vote with these tokens, either with the number of votes being the number of tokens, 1 per account, or other formulas in between).
      4. EAS Attestations
      5. Guild roles
  3. Use other sources for sybil resistance.
    1. Worldcoin or brightid or zupass

Conclusion

Giving round managers the ability to be able to tune these parameters would give them the ability to sculpt very specific capital allocation requirements into their rounds. It would allow Gitcoin Grants Stack to be more configurable to capture not just QF, but RPGF, or other novel use cases.

Open Questions

  1. What 1-3 allowlist options are the most important ?
  2. How do we make sure we are continuously keeping up with the markets needs?
  3. Is this an Allo build or Grants Stack build?
2 Likes

I believe this would be worth pursuing. To answer your questions:

  1. I think we can start simple and enable allowlisting via 1) simple delegation (i.e. who is an admin versus a reviewer, etc.) 2) .csv upload of allowlist (the badgeholder example you share) and 3) integration with best of breed partners like Hats Protocol.

  2. Develop partnerships with others in the space who are specializing in this domain and keep our internal functionality (simple delegation/.csv upload) limited. We should also be actively looking to fund integration partners that are best of breed versus internalizing effort ongoing.

  3. IMO simple integration (the delagation example and .csv uploads) could be Grants Stack with more advanced/partner integrations being an Allo build that eventually can make its’ way upstream to Grants Stack if feasible.

1 Like