Proposals
Standardised proposal structure across contracts
In order to allow decentralised voting to take hold in DAOs, Aetos uses an asynchronous voting method via "proposals". Proposals are objects stored on chain that contain specific data to a proposition made by DAO members.
Each proposal created goes through 3 stages, the creation stage, the voting stage and the processing stage.
Creation Stage (Propose): A member can choose from a list of existing proposal templates to put forward to their DAO. They set the parameters and an event gets emitted upon submitted the proposal to the chain.
The proposal is then visible in the dashboard view of the DAO. Based on the config specified during DAO creation, proposals have a specific time limit in which member are able to vote.
Voting Stage: Once a proposal has been created, members can choose to vote on the proposal. Currently, each DAO member is allocated 1 vote per proposal. They can vote to pass or fail the proposal.
Processing Stage: Once a proposal either reaches its voting end date or the voting quorum has been met, the proposal can be processed. Processing calculates whether a proposal will pass, fail or is still pending.
A passed proposal will immediately process in the same transaction.
Proposal List
| Aetos | Capital Vault | Returns Vault | Operations Vault | Sub-Vault |
|---|---|---|---|---|
0: Text Vote | 0: AMM Swap | 0: AMM Swap | 0: AMM Swap | 0: Token Whitelist |
1: Replace a single council member | 1: Token Whitelist | 1: Token Whitelist | 1: Token Whitelist | 1: Custom Transaction |
2: Existing member kick | 2: Funding | 2: Contributor | 2: Close Sub Vault | |
3: Stop signups | 3: Add Manager | |||
4: Stop DAO | 4: Remove Manager | |||
5: New Member | 5: Replace Manager | |||
6: Slash member | 6: Issue returns to returns vault | |||
7: Pardon member | ||||
8: Issue bonus shares | ||||
9: Nominate new council | ||||
10: Assume role and withdraw | ||||
11. Change DAO Metadata |
Last updated