> For the complete documentation index, see [llms.txt](https://meta-dao.gitbook.io/meta-dao-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://meta-dao.gitbook.io/meta-dao-docs/introducing-meta-dao/introducing-meta-dao.md). # Introducing Meta DAO {% embed url="" %} Meta DAO was born out of respect for what the team at Olympus DAO pioneered. We are a community project built by a team of engineers, researchers, and marketing professionals who have participated in Olympus and other OHM forks. By combining the best traits of these DAOs and our team’s past experience, **we aim higher and plan to build something even bigger.** Olympus DAO pioneered the model that Meta DAO and many others have followed, yet none have been able to surpass $1B in total value locked *(as of the time of this writing)*. **Meta DAO’s ambitions are much higher. Our goal is to grow the TVL for the Meta DAO community to $100B TVL.** The thesis behind launching Meta DAO is to take the principles of OHM, but expand to all EVM chains to reduce transactional fees. This approach will be combined with new bond types specifically targeted at the Metaverse. The bond pair we will support at launch is MIM/META. This will be followed by MIM/META LP and wFTM/META. Once the treasury is stable it will expand further. --- # 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://meta-dao.gitbook.io/meta-dao-docs/introducing-meta-dao/introducing-meta-dao.md?ask= ``` 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.