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

# Treasury

The Treasury is a central component of WagerDAO, designed to **manage protocol fees transparently and efficiently**. It ensures that funds generated by the platform are automatically allocated to support ongoing development and marketing efforts.

***

### How It Works

* **Automatic Fee Collection & Distribution**
  * Each settled bet contributes a small protocol fee.
  * Fees are automatically distributed according to the system’s rules:
    * **80%** to development wallets
    * **20%** to marketing wallets
* **On-Chain Transparency**
  * All transactions, both incoming fees and outgoing distributions, are fully visible on Binance Smart Chain.
  * Users can independently verify Treasury activity via BscScan.
* **Reliable and Trustless**
  * Payments occur automatically after each bet settlement.
  * No manual intervention is required, ensuring accuracy and consistency.

***

### Purpose and Benefits

* **Sustaining Development**
  * Treasury allocations fund platform maintenance, feature development, audits, and upgrades.
* **Supporting Marketing and Growth**
  * Marketing allocations support campaigns, partnerships, and community initiatives to increase user adoption.
* **Ensuring Transparency**
  * The automated, on-chain structure guarantees that all fund flows are publicly verifiable.

***

### FAQ

**Q: Who controls the Treasury?**\
A: The Treasury is fully automated. Funds are distributed according to pre-defined rules within the smart contract, without manual intervention.

**Q: Can users verify Treasury activity?**\
A: Yes. All transactions are recorded on-chain and accessible via BscScan.

**Q: How are fees allocated?**\
A: Currently, **80% goes to development and 20% to marketing**. Any future adjustments will be communicated transparently.

***


---

# 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://wagerdao.gitbook.io/whitepaper/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.