> For the complete documentation index, see [llms.txt](https://jmc-dao.gitbook.io/jmc-dao-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jmc-dao.gitbook.io/jmc-dao-whitepaper/competition/the-dao-model-framework.md).

# 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:

<table data-header-hidden><thead><tr><th width="192.33333333333331"></th><th width="244"></th><th></th></tr></thead><tbody><tr><td> </td><td><strong>A typical modern DAO</strong></td><td><strong>JMC DAO model</strong></td></tr><tr><td><strong>(1) Voting flow / mechanics</strong></td><td><p>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.</p><p>Problem: voter apathy, too complex concepts for wider adoption</p><p> </p></td><td><p>Proposals are being split in two types:</p><p>- 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.</p><p>- Bigger DAO governance issues – minimal supporting quorum of votes.</p><p>Solution: This helps decrease DAO competitiveness dependence on voter apathy, doesn’t give ground to another problem of the lack of control &#x26; resembles widespread decision-making practice thus making it easier to comprehend.</p></td></tr><tr><td><p><strong>(2) Treasury management</strong></p><p> </p></td><td><p>Treasuries are usually managed by only a few members of the community (no decentralization).</p><p>Problem: trust</p></td><td><p>Funds are released from the treasury automatically by the smart-contract based on the on-chain DAO voting decision.</p><p>Solution: trustless</p></td></tr><tr><td><strong>(3) Customization need devs</strong></td><td><p>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.</p><p>Problem: trust, high customization costs</p></td><td><p>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.</p><p>Solution: trustless, no devs needed, low cost.</p></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://jmc-dao.gitbook.io/jmc-dao-whitepaper/competition/the-dao-model-framework.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.