Hey everyone! It’s Sam from the Comms team sharing an update from the last Aragon DAO discussion on November 11.
Here’s what we talked about:
What are rules? In our Governance Framework, Rules are enforced by the on-chain deployment and applicable laws, which establish the default governance model of the organization.
Lightweight structure: The technical design that follows will be the default governance model of the Aragon DAO. The default governance model is intentionally minimal to foster experimentation on the social layer and to give teams as much autonomy as possible to deliver impact. Some elements may be protected by legal wrapper(s), which may create additional rules within the ecosystem and towards the local laws of a jurisdiction.
Due diligence: The Rules are still a work in progress with decisions to be made regarding the scope of the initial deployment, as well as legal wrapper(s) that may be incorporated to protect one or more aspects of the organization. These decisions are currently in due diligence and being weighed by key stakeholders. The Aragon DAO will be deployed gradually and carefully, allowing us to test and iterate on the model before transferring a significant portion of the Treasury.
Work in progress: Please note that the diagrams below are a work in progress Names and numbers are for illustration/example purposes only. The delay periods and parameters have not yet been set. We will be careful with parameter settings, as they greatly impact security.
At a high level, the Aragon DAO deployment will have the following components:
- Token Wrapping: ANT Holders must wrap their tokens to participate in governance.
- Delegation: ANT Holders may delegate or undelegate their voting power at any time. They may also vote directly on proposals to override the votes of their Delegates.
- Proposals: ANT Holders may submit proposals as long as they hold above the specified amount to prevent spamming attacks.
- Delay Period: There is a delay period between the proposal and voting stage. A delay period was chosen before the voting stage, in order to preserve the integrity of on-chain execution once a vote is passed. It also creates a window for ANT Holders to wrap their tokens or update their delegation.
- Proposal Veto: A group of Guardians appointed by Delegates may veto proposals under specific circumstances. This is a necessary safeguard against malicious proposals.
- Guardian Appointment/Discharge: Guardians are appointed or discharged by Delegates. A trusted group of stakeholders may veto the appointment or discharge of Guardians, as a security measure in the event Guardians get compromised.
- Vote Period: A snapshot is taken at the beginning of the vote period, capturing the voting power of ANT Holders and Delegates. Delegates may vote on proposals on behalf of ANT Holders. ANT Holders may vote directly to override the vote of their Delegate.
- Vaults: The funds will be distributed among different vaults granting different permissions.
- Wallet Address: Successful proposals may trigger a transfer of funds from a Vault to the wallet address designated in the proposal.
Submit: ANT Holders with a certain threshold of tokens may submit proposals. Proposals enter a delay period, where Guardians may veto the proposal.
Veto (security option): Guardians will have a clearly defined mandate (ie. stopping malicious proposals). If proposals are not vetoed during the delay period, they can proceed to the voting stage.
Vote: A snapshot is taken when the proposal is opened for the voting stage. Delegates may vote on proposals on behalf of the ANT Holder(s) they represent. ANT Holders may override the vote of their Delegate by voting directly on the proposal. ANT holders don’t have to delegate—they can choose to vote without delegation. If the proposal passes, anyone can execute the transaction.
ANT Holders who hold a certain threshold of tokens can create a proposal to have Guardians appointed or discharged. Guardian proposals may be vetoed by a trusted group of stakeholders (yet to be defined), who have a long history and commitment to the Aragon project. If the Guardian proposal isn’t vetoed, voting proceeds as described above.
The Rules will be described in the Charter. The Charter will be as concise and accessible as possible (1-2 pages). It is meant to be a plain English translation of the deployment, prioritizing technical accuracy and accessibility. It will follow the governance flow step-by-step and directly link to addresses, parameters and legal documents for ease of reference.
The draft Charter will be shared once the scope of the initial deployment and legal wrapper(s) have been agreed upon by advisors and key stakeholders.
If you have questions related specifically to Rules, comment them below and I will answer them or find someone who can. Thank you!