> 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/introduction/roadmap-2025.md). # Roadmap 2025
## Mimir V2 Mimir v2 shifts control to **node operators**, letting them adjust permissions and halt chains when needed. It boosts **decentralization** and empowers the community to propose and vote on upgrades, ensuring Maya evolves with transparency. ## Aztec Enables users to access Smart Contracts and build advanced DeFi tools like derivatives and algorithmic stablecoins within the Maya ecosystem. ## Zcash Integration Zcash $ZEC is depositable into Maya for Swaps & Liquidity actions. ## Taproot Maya integrates Taproot+, bringing enhanced privacy and scalability to Bitcoin transactions. This unlocks exciting new DeFi use cases for BTC, making it more versatile and efficient in the Maya ecosystem. ## Kaspa Kaspa $KAS is depositable into Maya for Swaps & Liquidity actions. ## Swapper Clout ## THORChain Dex Aggregation Enabling swaps between THORChain & MAYAChain assets. ## Cardano Integration Cardano $ADA is depositable into Maya for Swaps & Liquidity actions. ## More Chains Will be announced accordingly. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.mayaprotocol.com/introduction/roadmap-2025.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.