Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sustainable community treasuries: refill from CII issuance and fees #351

Open
brenzi opened this issue Sep 16, 2023 · 1 comment
Open

sustainable community treasuries: refill from CII issuance and fees #351

brenzi opened this issue Sep 16, 2023 · 1 comment

Comments

@brenzi
Copy link
Member

brenzi commented Sep 16, 2023

In the current protocol design, community leaders are expected to fund their activities from external sources (like grants from Encointer Association or donations). If they want to spend CC, they need to buy it from somewhere. This has the nice side-effect that it causes circulation of CC, but other designs would be imaginable. IT seems intuitive to send a fraction of money issuance to communitiy treasuries. The community should then be able to vote on who should control spending of their treasury

Moreover, the global protocol needs to be maintained and it appears fair to share this load among active communities

Possible Solution:

  • whenever participants claim their cycle rewards (CII), an additional fraction of CC is issued on behalf of the community treasury
  • tx fees go to treasuries instead of being burned
  • the community treasury is controlled by a democratically elected account (preferably multisig among active community leaders)
  • even faucets could help fund the treasuries: either upon creation or upon drip, a fraction of the faucet's token could be transferred to the treasuries. Upon creation would be more attractive for community leaders
@brenzi
Copy link
Member Author

brenzi commented Nov 3, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant