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

[DOC] DAO governance module Requirements document #10

Open
2 of 5 tasks
o-o-0 opened this issue Jul 30, 2020 · 2 comments
Open
2 of 5 tasks

[DOC] DAO governance module Requirements document #10

o-o-0 opened this issue Jul 30, 2020 · 2 comments
Labels
documentation Improvements or additions to documentation

Comments

@o-o-0
Copy link
Contributor

o-o-0 commented Jul 30, 2020

Type of Proposal

  • Feature Request (e.g. functionality)

  • Economic Model

  • Underlying Technology (e.g. performance)

  • Application Development

  • Others

Background

As we all knows that DeFi need decentralized governance to help them to keep decentralize,ist called as Decentralized Autonomous Organization (DAO).

The DAO can govern the DeFi contract or protocol ,member of it can use their tokens to vote for proposal and got some reward.

KuChain use PoS consensus and has own validators, its a natural governance machine work for the KuChain community,that was decentralized and perfect.

For the other consensus and community, KuChain gov module is insufficient.

So KuChain can build DAO tools/platform for DAOs do some governance in the feature.

Describe The Proposal (No more than 50 words)

KuChain need serve the DAO , and make them stake, vote with their own token.

Business Model (Optional for underlying technology)

DAO tools can make more activity on chain, and produce more gas fee , KuChain not only serve the tokens trade each other, but also support token staking and use .

So KuChain can attract high quality token,and high quality talents both.

Implementation Steps (Optional for economic model)

KuChain need implement the DAO module, with the functional about

  • new DAO with token

  • new proposals

    • Membership - Requesting new shares to join the DAO

    • Trading - Request the DAO to swap assets within the War Chest

    • GuildKick - Request to forcibly remove a malicious member through a vote

    • Funding** - Requesting funding from the DAO

    • Whitelist Token - Request to add support for a new ERC20 token.

  • sponsor a proposal

  • vote proposal with customize token

  • customize the params of DAO

    • voting period

    • voting sponsor number

    • voting weight

  • DAOs list

  • DAOs management

Expected Outcome
KuChain will have some awesome DAO in the network , one chain can accommodate many assets and organizations.

Timetable (Optional)

Estimate the timetable of your plan.

Implementation Steps Time Consuming
step 1 build DAO gov moudle
step 2 integrate with asset module
step 3 testing
Total duration 6 weeks

Contact Information

[email protected]

@o-o-0 o-o-0 added the documentation Improvements or additions to documentation label Jul 30, 2020
@angelorc
Copy link
Contributor

What you are looking is already implemented. cosmos-sdk use the gov module where the governance (validators and delegators) must vote on proposals (https://docs.cosmos.network/master/modules/gov/). The new version of sdk have also the upgrade module that can handle the upgrade on chain.

Can be useful to change the proposal and describe which kid of proposal should be added and the schema process for each proposal

@o-o-0
Copy link
Contributor Author

o-o-0 commented Jul 31, 2020

@angelorc Thank you for point out that cosmos-sdk has upgrate the gov module, but like what I said, KuChain need support the token which is issued by the user, the Token need to be treated as a voting power for their own DAO.

If you have read the source code of Kratos , you will figure it out ;-) .

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

No branches or pull requests

2 participants