Hello everyone, at 1Hive I’ve been working with many different AragonOS DAOs, and I would be glad to help with my knowledge and experience to the constitution of this new stage of Aragon if you decide to go the Aragon Client path.
The first proposal I can do in regards to implementing a DAO that is controlled by delegated-ANT would be to create a new custom AragonOS DAO with the following apps:
- Token Wrapper
- Tao Voting
It is an audited AragonOne application that allows wrapping an ERC20 into a MiniMe token, making it compatible with the rest of AragonOS ecosystem. ANTv1 already was a MiniMe token, but it was simplified in the migration to ANTv2, making it not compatible with the
ERC20Snapshot interface. Although we may find alternative better solutions, wrapping ANTv2 would make it compatible again with Tao Voting without much hassle.
It is a finished and renamed version of Aragon’s Disputable Voting used by 1hive in their Gardens framework.
It has three main differences from the normal AragonOS voting:
It is disputable. This means that if a vote does not comply with the Agreement (DAO Manifesto, Charter, Covenant…), anybody can dispute the vote and freeze it until Aragon Court / Celeste decides if the vote is compliant with the Agreement or not.
It ends quietly. So if the direction of the vote changes right before the voting ends, there is an extension of the voting time, so whales can’t change the direction of any vote with unintended consequences when the participation is low. See a better explanation here.
It can be delegated. Token holders can set a delegate who will use their voting power for them.
Not all of these extra features need to be used. We could make votes non-disputable, or set the quiet ending to zero, and still use the vote delegation capabilities of Tao Voting.
This app offers a frontend to do payments from the Vault/Agent to other addresses. It is mostly used to create immediate payments (because the user interface is only offering this option), but it can be also used to set up budgets for specific amounts of time and to create recurrent payments. You can refer to the EVMcrispr documentation page to see the full functionality of this app.
It is the core of the DAO, the place where the funds are going to be held, and the one that can be used to interact with external contracts. As an example, you can see how NFTX uses its agent to do all kinds of operations to its protocol here.
This is the most simple way to proceed into an token-delegated Aragon DAO that I can imagine. If you decide to go this path, we may be able to propose some modifications, so the DAO design is more convenient and resilient to attacks, but this is a good functional first approach to the migration.