> For the complete documentation index, see [llms.txt](https://docs.bigindie.games/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bigindie.games/our-treasury-and-dashboard.md).

# Our Treasury and Dashboard

The BIG Treasury is a core part of our transparency model.

The treasury is where project-owned assets can be tracked, including tokens, stablecoins, liquidity-related assets, and other ecosystem funds. Our goal is to make the treasury easy to understand for the community, players, holders, and partners.

We believe trust is built through visibility. That is why BIG Indie Games will provide a public treasury dashboard showing key treasury activity, balances, and relevant transactions.

The treasury dashboard is intended to provide transparency around:

·    Treasury balances

·    Buy-back activity

·    Ecosystem funds

·    Wallet movements

·    Revenue-supported Web3 actions

·    Long-term project reserves

Transparency is not an extra feature for us. It is part of how BIG Indie Games should operate.\
\
Launching soon.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bigindie.games/our-treasury-and-dashboard.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.