Skip to content

Instantly share code, notes, and snippets.

@pythonpete32
Last active September 5, 2019 21:59
Show Gist options
  • Save pythonpete32/5b0077cc12e44d8a7b2dc617b2c2a9b6 to your computer and use it in GitHub Desktop.
Save pythonpete32/5b0077cc12e44d8a7b2dc617b2c2a9b6 to your computer and use it in GitHub Desktop.
CRDAO

Community Rewards DAO: Specification, Application Process, and Governance settings

This document is a draft, suggestions on how it can be improved are welcome

Philosophy

The Aragon Network is a platform for DAOs, a tool kit for mechanism designers, a framework for decentralised applications, a global jurisdiction and much more. To achieve it's long term goals, it must Experiment with novel incentive mechanisms, grow it's community and foster participation from the wider blockchain ecosystem.

The Community Rewards DAO (CRDAO) will champion and incentivise community participation with its rewards program based on the 1Hive Rewards system. The DAO will initially be structured similarly to the Nest DAO

The Community Rewards DAO

  • Members of the CRDAO have a non-transferable membership token enabling them to vote in both the mainnet and rinkeby DAO
  • Funds awarded to the CRDAO are held in the Mainnet DAO
  • Until the Dot Voting application is live on mainnet, rewards will be decided in the rinkeby DAO after which the balances will be migrated to the mainnet DAO
  • CRDAO members also form an Aragon Working Group where they can communicate
  • Anyone from within the community can nominate another community member to be rewarded
  • Initially, CRDAO members will add nominations and vote directly using Dot Voting
  • when sourcecred integration is available, coursecred reputation holders will be responsible for allocating rewards with the Dot Voting App

Membership for the CRDAO

The initial membership of the DAO will be members of the CRDAO working group. These will be chosen by the association using the same mechanism for bootstrapping the Nest DAO

Application for membership

  • Flock and Nest teams can appoint (1?) team member

  • Members of the broader community can apply provided they can identify themselves as active (sourcecred?, discordbadge?, the discretion of CRDAO members?) It is intended that these form the majority of the membership

Requirements

  • Be an active community member
  • Flock/Nest/AA should be represented, however, this should be a community-run organisation (maybe limit membership to 1-2 members from each org?)
  • Members of the DAO must vote in every round. If a member is not voting and cannot justify why he or she will be offboarded

Onboarding

  • For the first membership round, the Aragon Association will be in charge of accepting/rejecting applications. After that, CRDAO members will manage membership autonomously
  • Once applications have been processed by the CRDAI, accepted applicants will have to submit an identity verification proof using Keybase to receive their membership token. This is not a KYC process but a way to avoid sybil attacks and enable a trusted setting

Offboarding

  • If some member is not actively participating in votes, he or she may be offboarded. The CRDAO membership or Aragon Association may burn its membership token

Governance settings and permissions

Intentions

The CRDAO and its members should be as autonomous as possible in the allocation of rewards. In the short term, The Aragon Association might keep ownership of sensitive settings such as creating permissions, burning tokens if considered necessary.

Any member of the Aragon community can nominate another member to be included in the next round of awards by adding mentioning them in the forum thread or rocket chat highlighting what they have done to be rewarded.

CRDAO members will come to consensus offline as to who will be included in the upcoming round

Summing up
  • The DAO will have a council of members voting on proposals and issuing grants. This council will also approve and reject the application of new members to the CRDAO.
  • The Aragon Association may keep centralized ownership over a few sensitive roles (creating permissions, creating transfers, burning/revoking tokens) initialy. These will eventually devolve to the DAO
  • Any Aragon community member should be able to nominate another Aragon community member
  • CRDAO should it's self decentralise reward allocation when possible

Voting settings

Finance settings

Token manager settings

Dot Voting settings

ACL settings

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment