Motions guidelines
How to achieve consensus in our Colony
Overview of the Motion and Objection process
The DAO will make decisions using the built-in optimistic consensus in Colony.
This is the overall process illustrated in a few steps:
A member of the Colony creates a Motion in a specific team (e.g., Root or Marketing)
The motion to be visible inside the Colony should be supported by staking the native tokens.
Only people with a reputation in that specific team would be able to stake tokens to support the motion.
When at least 10% of the motion is staked, it will be visible inside the Colony
When the motion is fully staked, it has the possibilty to pass if no one object during the windows period (usually 48 hours)
If someone objects and the objection is fully staked using the native tokens, we will go to voting.
The reputation weights the voting power.
When users having collectively 70% of the reputation vote, the voting session close
Then there is the reveal phase of the voting. The votes are not anonymous anymore.
Finally, the DAO can finalize the motion, and the participants can claim back the tokens that might have been staked during the process
For more information about how to create a motion and how to object please refer to the official documentation of Colony
https://colony.gitbook.io/colony/extensions/motions-and-disputes/creating-a-motion
Different types of Motions and templates
Before launching our last official Colony, we had several pilots to determine and perfect our internal processes. Here we will provide Motions examples that should be used as templates to create proposals and achieve consensus in our official Colony.
Take a look at one of our Pilot Colony for more information
Check our Motion templates with examples nested under this page.
Last updated
