The DAO model / framework
As of mid-December 2022 there were 11K+ spaces/DAOs in Snapshot. Most are protocol DAOs. As already been said models/frameworks are very different. A few notable examples of a workable framework for various purposes are: LAO, Moloch DAO and its clones like Metacartel, Hydra Ventures (doesn’t have tradable tokens). The biggest investment DAO in the world is BitDao with $1.8 bln in treasury.
While designing the JMC DAO we took the best of what we currently know about modern DAOs. However, there are no direct analogues to JMC DAO. Here are three key differences between every popular modern DAO and JMC DAO model:
A typical modern DAO
JMC DAO model
(1) Voting flow / mechanics
One mechanism (type) for each DAO to vote on all issues possible: proposal approval requires either minimal support quorum of votes, or “lazy consensus”, etc.
Problem: voter apathy, too complex concepts for wider adoption
Proposals are being split in two types:
- Day-to-day issues resolved by the voting of Experts in a particular area under Protector’s supervision and “lazy consensus”-style further on-chain DAO approval.
- Bigger DAO governance issues – minimal supporting quorum of votes.
Solution: This helps decrease DAO competitiveness dependence on voter apathy, doesn’t give ground to another problem of the lack of control & resembles widespread decision-making practice thus making it easier to comprehend.
(2) Treasury management
Treasuries are usually managed by only a few members of the community (no decentralization).
Problem: trust
Funds are released from the treasury automatically by the smart-contract based on the on-chain DAO voting decision.
Solution: trustless
(3) Customization need devs
DAO voting results have no direct influence upon the DAO smart-contract code, i.e. they are public opinion polls and are advisory to the DAO developers who may or may not adjust the DAO smart-contract accordingly.
Problem: trust, high customization costs
JMC DAO code will have a lot of parameters which are adjustable automatically by the smart-contract itself according to the on-chain DAO voting decision.
Solution: trustless, no devs needed, low cost.
Last updated