> For the complete documentation index, see [llms.txt](https://docs.wemix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wemix.com/nile-en/dao/introduction-to-neith-protocol/trust.md).

# Trust

The Trust is where the name and authority of each DAO is delegated, becomes the main agent of contracts off-chain, executes and manages DAO business.&#x20;

\
A corporate body, group or person not related to participation in DAO may be the Trust, and take the role of representing and doing business for each DAO. Information related to the Trust such as the Trust wallet address is made public to each DAO, and the Trust claims as rewards a set percentage of fees from the DAO funds used and profits.&#x20;

\
The percentage of Trust fees are decided in the DAO business registration step. The Trust may also be the main agent of off-chain and contracts, as well as the main agent of the execution of DAO projects, and also take care of the related financial, accounting and legal responses.


---

# 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.wemix.com/nile-en/dao/introduction-to-neith-protocol/trust.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.
