Initially, when we were planning to launch in December, the design for the Commons was to use the same Conviction Voting set up that 1hive has been using up until now, with just a change in the issuance model.
The upside here was that, despite never receiving a formal audit, this version of CV has been tested with millions of dollars in it for many months. This is surely more than we expect to have in our Funding Pool a very safe move.
The down side was there were many lessons learned in its use and desired improvements to the code base that were currently in the works, especially around certain points of centralization. The biggest point of centralization that is being addressed is the multisig that holds the role of removing proposals from CV that do not align with the mission of the project.
Our intention was to start with the current version and have Gravity maintain this multisig and upgrade to the new version when it was ready, if the Commons approved.
Things have changed. Our timeline to launch the Hatch is now targeted at March and we can assume we won’t be upgrading the TEC Hatch DAO into a Commons with Conviction Voting until April.
Celeste, the solution to all of our centralizing Multisig needs (in one way or another) is going to be ready at the end of the month, and will be implemented by 1hive well before our Hatch.
Given these two facts, there is a positive sum opportunity, to combine the Gardens Swarm’s development efforts with the 1hive team’s roadmap and focus our efforts on getting the new disputable version of Conviction Voting right.
The proposed approach would have a few results:
- Alignment of interests of both 1hive and TEC around a shared codebase as opposed to spending efforts on an old codebase. Specifically, we would help them with the new front end for Disputable CV, and Adrià would do a code review of the new code base.
- Political alignment with the 1hive community, who has mostly funded the development work so far.
- Integrate 1hive’s HNY token into the TE Commons system. HNY would be used to dispute proposals that do not follow the TEC’s Conviction Voting Terms.
- Potentially integrate Celeste in other places as needed.
- It doesn’t add any extra work for the Gardens Swarm, and doesn’t slow down the Hatch.
- We as a community, learn about using Celeste. There are great resources here:
We gather questions from this thread, please write here the questions you have after reading the previous resources.
We prepare an AMA with the Celeste swarm to answer these questions.
We vote on whether to use Disputable Conviction Voting or not. Pros and cons can also be detailed and discussed in this thread (This is a blocker to the Hatch).
If we decide to go the Celeste route, we prepare a TEC Community Covenant with the Soft Gov, Legal & Gravity WGs and propose it as another vote (This is not a blocker to the Hatch).