> For the complete documentation index, see [llms.txt](https://mayz.gitbook.io/mayz-whitepaper-v2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mayz.gitbook.io/mayz-whitepaper-v2/mayz-protocol/technical-document/purpose-of-mayz-protocol.md).
# Purpose of MAYZ Protocol
The purpose of the MAYZ Protocol, or simply the **Protocol**, is to provide **Users** with a decentralized finance (DeFi) tool to facilitate their investments in network-native tokens.
The **Protocol** will offer the service of **decentralized investment funds** built on the Cardano network through a series of **smart contracts**, which we will also call **Contracts**. The Smart Contracts will contain the logic and rules of the investment funds, allowing for automated and transparent investment management. These Contracts will have an interface to interact with through a website, the **Protocol Portal**. Throughout this text, we will also call these investment funds simply **Funds**.
The Protocol will have an associated utility token, the **$MAYZ Token**, providing access to certain administrative functionalities.
Each investment fund will be defined by an **Investment Unit** consisting of several tokens, and the Investment Unit may be adjustable.
Each **Fund** will have a **Liquidity Provider Token** or **LP** token representing its participation. There will be as many LP tokens as Investment Units will be deposited in the **Fund**.
\
**Users** who wish to invest in the **Cardano** ecosystem quickly and securely will be able to do so by simply holding these LP tokens in their wallets. They will have different mechanisms to access the LP tokens of a Fund, and they can do so through the secondary market, the **Swap Contract**, the **Escrow Contract**, or by interacting directly with the **Fund Contract**.
---
# 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://mayz.gitbook.io/mayz-whitepaper-v2/mayz-protocol/technical-document/purpose-of-mayz-protocol.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.