> For the complete documentation index, see [llms.txt](https://docs.hoard.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hoard.world/the-world/the-vault.md).
# The Vault
The seed-liquidity lock and the team vesting, verifiable on the explorer.
The Warden
The Warden keeps the two promises anyone can check on the explorer.
## Seed liquidity
80% of the supply seeds the canonical pool, and that position is held by the **LiquidityLock**, a contract that holds the full-range HOARD/USDG position directly in the Uniswap v4 PoolManager.
* `withdraw` reverts until `unlockAt`, and the date can only move **forward**.
* `lockForever` is a one-way switch that makes the position unwithdrawable while its liquidity stays live in the pool.
* Adding liquidity is always allowed. Only removal is time-gated.
* Nothing in the lock collects fees: the pool's native LP fee is zero and every fee flows through the hook.
Everything a holder wants to verify is a public view on the verified contract: `unlockAt`, `liquidity`, `lockedAmounts`, `isLocked`, `permanent`. The launch lock is 365 days.
## Team vesting
The team's 5% is 0.5% liquid at launch and 4.5% in the **TeamVesting** contract, OpenZeppelin's VestingWallet with a step function: nine equal tranches, one every 30 days.
* `release` is permissionless and only ever pays the beneficiary. Nobody can accelerate the schedule.
* HOARD held in the vesting contract has no Hoardlings and cannot be nested or earn SPY. Units become Hoardlings in the team wallet as tranches release.
## Rewards reserve
8% of the supply waits in an OpenZeppelin **TimelockController** with a six-hour delay, as three equal tranches for the users of the Hatchery, the Seer's Tent and the Arena. Each feature's own distributor pays its tranche out when the feature ships, streamed over three days.
## In the app
The Vault page reads the lock date, the locked amounts, the vesting released so far and the next unlock straight from the chain, with a link to each contract on the explorer.
---
# 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.hoard.world/the-world/the-vault.md?ask=&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.
