Please describe your proposed solution.
We are creating an open-source governance-suite of contracts for DAOs to use to more effectively govern themselves. Our governance suite is based on OpenZeppelin, targeting the Milkomeda chain, allowing us to leverage cross-chain compatibility being built into the design of the platform. (Read more at <https://www.milkomeda.com>)
This protocol will include proposing, voting, and staking mechanisms that any collective can use to steer the direction of their organizations. Our contracts' information architecture is crafted to support DAO members in interaction with Done Collectively-based organizations, with a goal of supporting DAOs on other EVM chains to transition into Cardano and get running on the Done Collectively platform.
For context, the Done Collectively manageability framework provides DAO members with essential tools focused first on the practices used by effective organizations of all kinds. Those most effective organizations have culture (which provides stabilizing social influences and is largely decentralized by nature), shared vision, and clear objectives. In these organizations, specific groups focus on more specific objectives, and the organizational hierarchy facilitates them to be clearly aligned with the overall objectives.
Done Collectively provides workflows that add cultural and explicit mission-orientation capabilities for use by decentralized organizations, enabling them to adopt and retain high-value processes without imposed hierarchy. Thus, leadership is free to emerge from aptitude, ability, and desire - not by divine right of Seniority.
DAOs adopting our EVM-based DAO Management Contracts on Milkomeda within Done Collectively will be able to use on-chain mechanisms together with in-app workflows to collaboratively…
- propose and commission working groups
- propose and adopt cultural norms and organizational values
- propose and adopt organizational objectives and target metrics
- commission projects with specific objectives and documented plans
- propose to iterate project and working-group commissions
- propose to create or modify protocol parameters
- administer a general treasury, and fund and defund treasuries for working groups
- administer working-group treasuries in alignment to working group commissions, and fund and defund project treasuries
- administer project-level treasuries in alignment with project-level objectives, and fund bounties
- create revenue generating opportunities for nascent decentralized autonomous organizations.
A likely question is "why not use sub-DAOs?" … working groups in Done Collectively are very similar to autonomous sub-DAOs, in that they can have their own treasuries and act autonomously to serve their specific missions, within the scope of their commission, yet they remain connected by culture, general mission, values and objectives to the overall organization. Also, likely by a light degree of oversight, using the "double linkages" pattern from Sociocracy.
This "integrated sub-DAO" approach enables organizations to retain continuity and alignment by default for their projects and working groups, ensuring that sub-DAOs don't centralize their own autonomy against the mission of the DAO at large. Members remain free to spin out separate DAOs where relevant, while the entire organization can retain decentralized oversight over working groups and help those working groups stay on-mission and in service to the DAO in general.
Please describe how your proposed solution will address the Challenge that you have submitted it in.
The Great (Ethereum) Migration
Our proposal provides a clear path for people comfortable on EVM blockchains to operate on Milkomeda, transferring their ETH / native coins into Milkomeda and use them in the Done Collectively DAO management ecosystem. They'll also be able to start transacting value using (wrapped) ADA and get onboarded to Cardano.
We also expect to impact the number of users of these smart contracts once migrated to the Cardano ecosystem.
What are the main risks that could prevent you from delivering the project successfully and please explain how you will mitigate each risk?
Technical risks are naturally at top of mind in a heavily technical project such as this. We are expanding the information architecture of DAOs beyond what is typical and ordinary. The technical team has existing experience with Solidity, EVM-chain indexing and software development in general and will be supported by Done Collectively technical staff, many of whom are highly experienced software developers in their own right. Additionally, the Done Collectively product team will be at hand to help ensure that the technical progress integrates and aligns well with the product experience in the application platform.
This EVM DAO integration project will largely be staffed by our partners in Kodex Data Systems, thus augmenting our existing team with others in Kodex who are known and trusted. Our other F9 proposal will not be overlapping, staffing-wise, with this project, except for Randall's advisory role for this work-stream.
If we get multiple F9 proposals funded, the team at Kodex Data Systems will still be focused on delivery of this proposal.