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

# The treasury

The treasury holds the tax in HYPE and deposits it into Papertrade accounts, one after the other.

The treasury is a contract on HyperEVM. It receives HYPE from the trading tax and deposits it into Papertrade accounts.

## The accounts

The treasury holds a list of Papertrade accounts, each with a **cap of $10,000**, so that no account runs into Papertrade's per-account limits. It fills them **one after the other**: every lot goes to the first account in the list that still has room. When an account is full, the next one starts receiving. The team adds accounts as needed; about ten are registered at launch.

## A lot

* Anyone can trigger a lot once one is due; nobody chooses where it goes.
* Lots have a minimum, a maximum and a minimum interval, so the treasury cannot be emptied in one call.
* Each lot is swapped from HYPE to USDC with a minimum output taken from HyperCore's own HYPE price, then deposited to the account's HyperCore address. If the pool price is away from HyperCore's price, the lot waits.

## What the treasury cannot do

Send money to an address that is not a registered account, or anywhere else. There is no withdrawal function. The team can add, cap or deactivate accounts; it cannot redirect the treasury.

The HYPE waiting in the treasury and the total deployed to each account are readable on-chain at any time.


---

# 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.paperstrategy.xyz/the-loop/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.
