This document will give you a brief walkthrough on the core functionality of the Genesis DAO MVP.

Setup

Create a DAO

Go ahead and connect your wallet and hit create a New DAO.

Think a second or two about the DAO ID - this will as well be the symbol of your token.

Give the world some explanation about your. This information is later editable by the council.

Configure proposal lifecycle

The next step is to configure your DAO for majority vote. Genesis DAO is currently working on an extension ecosystem that'll give rise to a lot more options.

For now you can

• issue a specific number of tokens
• decide how many of that tokens are required to stake to create a proposal; for spam protection reasons staking with the native currency is required as well
• a minimum majority threshold to require some participation in proposals for being accepted
• how long a proposal should be active for voting, this is internally stored as number in blocks but conveniently you can enter days here

Council Management

The DAO will be released to a council that controls it's actions with a multisignature account. We use the multisig module for this.

The multisig setup currently works via polkadot.js.org (see below), so you should have at least two signers.

You can as well select initial recipients of the DAO tokens. The remainders will be sent to the council.

Welcome to your DAO!

Proposal Lifecycle

Create a proposal

As a DAO user you can create a proposal if you have at least the number of tokens configured above and ten native tokens. Click proposals in your DAO overview page and go ahead and create one!

You have a chance to review it before it goes to vote:

This document will give you a brief walkthrough on the core functionality of the Genesis DAO MVP.

Setup

Create a DAO

Go ahead and connect your wallet and hit create a New DAO.

Think a second or two about the DAO ID - this will as well be the symbol of your token.

Give the world some explanation about your. This information is later editable by the council.

Configure proposal lifecycle

The next step is to configure your DAO for majority vote. Genesis DAO is currently working on an extension ecosystem that'll give rise to a lot more options.

For now you can

• issue a specific number of tokens
• decide how many of that tokens are required to stake to create a proposal; for spam protection reasons staking with the native currency is required as well
• a minimum majority threshold to require some participation in proposals for being accepted
• how long a proposal should be active for voting, this is internally stored as number in blocks but conveniently you can enter days here

Council Management

The DAO will be released to a council that controls it's actions with a multisignature account. We use the multisig module for this.

The multisig setup currently works via polkadot.js.org (see below), so you should have at least two signers.

You can as well select initial recipients of the DAO tokens. The remainders will be sent to the council.

Welcome to your DAO!

Proposal Lifecycle

Create a proposal

As a DAO user you can create a proposal if you have at least the number of tokens configured above and ten native tokens. Click proposals in your DAO overview page and go ahead and create one!

You have the chance to review it before it goes to vote.

Your DAO is now up for voting.

Voting for a proposal as a community member

As a community member you can review the current count or cast your vote.

Marking a proposal as faulty

If you think a proposal is spam you can report it as faulty to the council.

This will mark this proposal as reported to the council.

Finalize

Once the proposal duration is over everyone can hit the finalize button to move change the proposals status (it is automatically prohibited to vote once the duration is over, but change states on the blockchain require an action on behalf of someone).

Acting as a council

Upcoming version of Genesis DAO will create a non-signed transaction for the Council, but currently this functionality lies within polkadot.js.org

Go ahead and click create multisig in polkadot.js.og

Select the signers that you have used in the DAO creation. In order for this to match the Multisig created within your DAO the order and the threshold must be identical because they are used to derive the address.

The multisig is now mirrored in polkadot.js.org:

You can now go ahead and interact with the DAO - most prominently fault or mark a proposal as implemented.

After a proposal is over it's finalized, meaning people can no longer vote and it changes it status. implemented means that the requested action has been taken - e.g. someone went to the website and made the logo bigger. While everyone can mark as finalized ones a proposal is over, implemented is a council action.

Be sure to copy the encoded call data, as it's required for the multisig.

You can now authorize the transcation in your multisig wallet.

And approve it:

We have created a video on all of this here.