# Treasury Allocation

### **Treasury Allocation**

The treasury is the lifeblood of our protocol. Our investment policy involves protecting the treasury at all costs, even if at the cost of unrealized gains. At no point in our investments would we risk more than 20% of our investment.

| Allocation          | Percentage |
| ------------------- | ---------- |
| Big Ticket Fund/NFT | 30%        |
| Degen Capitalism    | 30%        |
| GameFi Investments  | 30%        |
| Business Expenses   | 10%        |

### **Business Expenses**

Each month, a certain allocation of the treasury will be extracted to fill up the following wallets.

| Wallet                | Allocation (10% Total) |
| --------------------- | ---------------------- |
| Savings               | 1%                     |
| Marketing Fund        | 5%                     |
| Team Salary           | 3%                     |
| Council/Advisory Fund | 1%                     |

**Savings Wallet:**

This will be put forth on a stable coin staking pool which will generate passive yield. This will be used for emergency purposes in cases of exploits, market crashes, or massive liquidation events. This will be the first line of defense against such events, further supplemented by the reserve fund if need be.

**Marketing Fund:**

This will be used to refill the marketing wallet. 

**Team Salary:**

This will be used to pay the salaries of all employees of the protocol from the community moderators to the development team.

*Take note: employees may have their own private stake in the protocol. We are requiring all employees to state their wallet addresses. What they do with their stake is theirs to own up to.*

**Council/Advisory Fund:**

This will be used to pay the salaries of contributing members of the protocol. We will hire part-time researchers and analysts to fill in the gaps in our ranks.


---

# Agent Instructions: 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:

```
GET https://apeinto.gitbook.io/docs/usdhares-tokenomics/overview-and-allocation/treasury-allocation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.