> For the complete documentation index, see [llms.txt](https://monoprotocol.gitbook.io/monoprotocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://monoprotocol.gitbook.io/monoprotocol/introduction/whos-behind-the-mono-protocol.md).

# Who's behind the Mono Protocol?

Mono Protocol is built by a team of experienced blockchain engineers, cryptographers, and product designers who have been at the forefront of Web3 infrastructure development. Our team combines deep technical expertise with a passion for solving the fundamental challenges that prevent mainstream Web3 adoption.

**Core Team Expertise:**

* Protocol Engineering: Extensive experience in building secure, scalable blockchain infrastructure
* Cryptography: Advanced knowledge in zero-knowledge proofs, consensus mechanisms, and security protocols
* Product Design: Deep understanding of user experience challenges in multi-chain environments
* Business Development: Strong relationships across the Web3 ecosystem with major wallets, exchanges, and applications

**Advisory Network**: Our advisory network includes leading figures from major blockchain protocols, prominent DeFi projects, and successful Web3 infrastructure companies, providing strategic guidance and industry connections.

<br>


---

# 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://monoprotocol.gitbook.io/monoprotocol/introduction/whos-behind-the-mono-protocol.md?ask=<question>&goal=<endgoal>
```

`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.