This is an early stage document, a work in progress, and we expect this document to change.

All comments welcome

Decision Engine Parameters

• Proposal Threshold Is there a minimal amount of voting power you need to create a proposal?
• Quorum What is the minimal amount of votes needed to pass a proposal?
• Support What is the percentage of yes-votes need to pass the proposal?
• Optimistic Execution are proposals executed by default (i.e. the quorum is set to 0)?
• Dynamic or static quorum Is the quorum fixed, does it depend on the type of proposal, can it change during the proposals life-time?
• Quiet ending period? accepted decisions need to go through a period in which members can change the vote before being executed
• Vote Duration How long does the
• Parametrized parameters. Is each proposal decided on with the same rules, or can this be different depending external properties, for example as in DAOstack's Holographic Consensus, where proposals get fast-tracked on the basis of the outcome of a staking mechanism.

Voting Power Mechanics

• Delegation Is it possible to delegate voting power, and under what conditions?
• Representation Is it possible to delegate executive power (say to a team that gets to spend a certain budget)?
• Voting power schemes voting power can be derived from a simple ERC20 or from complex token locking schemes. Whether the voting power is liquid or based non-transferable "reputation token" makes a difference when design the decision protocol
• Identity systems some voting systems benefit from sybil resistance, and so protocols like BrightID or Democracy Earth's proof of humanity could be integrated.
• Alternative ways of weighing votes most DAOs use simple all-votes-are-equal schemes, but there are alternatives in use as well, like quadratic voting

Security

• Time-lock there is a time between acceptance and execition of proposals
• Vetos Do special groups or individuals have veto power over decisions (say when a bug is found in a proposal)