> For the complete documentation index, see [llms.txt](https://docs.vispx.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vispx.io/whitepaper/revenue-model/treasury.md).

# Treasury

The treasury will be the holy grail of all revenue streams. To show transparency, we will be funneling all revenue supported by the VispX model into 3 wallets which will then be discussed and managed with the DAO.

It is important to note that the wallets will show as gross income to the company which includes; 

* **`marketing expenses,`** 
* **`development expenses,`**
* **`core team headcosts,`** 
* **`events,`** 
* **`and all other spendings related to VispX ecosystem operations and growth.`**

Once the above company costs are deducted, we are good to go in terms of the DAO treasury Strategy. Blockchain is a great start for transparency with our DAO community members. 


---

# 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.vispx.io/whitepaper/revenue-model/treasury.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.