> For the complete documentation index, see [llms.txt](https://docs.mayaprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mayaprotocol.com/white-paper/readme-1-1/roadmap.-maya-3.0.md). # Roadmap. Maya 3.0 Not all stablecoins are created equal The search for a decentralized stablecoin has been a tough one, and unfortunately, many attempts have failed to this date. In Maya, we believe that there is no such thing as an optimal universal model for stablecoins, one that rules them all… we believe that diversification of risks is key for stability, and we are building with this idea in mind. We have named this Roadmap: Maya 3.0 since everything in this Whitepaper after this section will not be available at launch since it requires further work, design, code, and economic audits, among other things. In other words, everything before Maya 3.0 will be available at launch after the Liquidity Auction takes place. Turning Maya 3.0 on or leaving it off forever will be decided by community discourse and Nodes when the time comes if the proposed design makes sense and has gone through the necessary audit and community review processes. ### ELI5 1\. Decentralized stablecoins have been called one of the “Holy Grails” of crypto, and our industry has experimented with different approaches and models to work them out. Today, Algorithmic Stablecoins are still risky, and Overcollateralized Stablecoins are still tough to scale and capital-inefficient. 2\. By looking at previous experiments, we believe that stablecoin models have always assumed they would succeed. Instead, we believe in iterative design and have approached the issue with a “fail-safe” attitude, where the risks of depeg always exist and need to be balanced and offset in more than one way. 3\. Maya will have 5 different stablecoins in its suite. Each one will be best suited for a specific type of user/investor since all of them have their own strengths and weaknesses, which will be clearly laid out at all times to everybody. --- # 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, and the optional `goal` query parameter: ``` GET https://docs.mayaprotocol.com/white-paper/readme-1-1/roadmap.-maya-3.0.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.