# Why MAYZ? With MAYZ, any user can get exposure to a wide range of different investment alternatives. Currently, web3 users can only get exposure to the Web3 ecosystems by managing their own portfolios. Most of them only hold native tokens like Bitcoin, Ether, ADA, etc. Getting into the utility tokens within these ecosystems can be challenging. Our vision is to leverage the power of blockchain technology to create a permissionless, decentralized financial ecosystem on Web3. We aim to empower people around the world by democratizing access to financial services, making it easier and more secure to diversify portfolios of assets, and simplifying the challenges of managing a well-diversified portfolio in a fast-evolving ecosystem. Our mission is to remove barriers to financial freedom and create a future where anyone can easily manage different financial products, regardless of their background or experience. We believe we can create a more inclusive and equitable global economy by building a decentralized and transparent platform that puts users in control of their financial future. ### MAYZ Protocol Goals 1. Provide a protocol that makes it easier and more secure to diversify portfolios of assets representing the process of wealth creation on Web3. 2. Democratize access to financial services like funds. 3. Simplify the challenges of managing a well-diversified portfolio in a fast-evolving ecosystem. 4. Investing only in ADA is missing out on an excellent opportunity for everything built in Cardano. --- # Agent Instructions: 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://mayz.gitbook.io/mayz-whitepaper-v2/introduction/why-mayz.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.