> 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-wall.md).
# The Wall
USDG buy orders beneath the market, built from fees and moved by rules anyone can run.
The Mason
The USDG Wall is a block of buy orders beneath the market: one-sided concentrated USDG liquidity in the canonical pool, placed below the HOARD price and managed by deterministic rules that anyone can execute.
## What feeds it
* 1.5% of every canonical trade.
* 20% of interest actually paid at the Bank, and the Stock Vault's share too whenever no Hoardling is nested.
## The upward cycle
1. Buyers move the HOARD price up.
2. The higher price holds long enough to satisfy the rebalance rule, read from the time-weighted oracle, never a single block.
3. Anyone calls `rebalance()`. The wall's range moves up beneath the new price, and the caller earns a bounded bounty.
4. New fees keep adding USDG depth.
## The downward cycle
1. If the price falls into the wall's range, the wall buys HOARD with its USDG.
2. As sellers consume the USDG, the position turns into HOARD inventory.
3. That HOARD is placed above the market as recovery liquidity.
4. A rebound sells the inventory back into USDG, refilling the wall and capturing fees.
## Rules
* Rebalance conditions are deterministic and visible on-chain. No operator picks ranges.
* The wall's USDG is never lent, and it is never an input to the price oracle.
* The wall is as deep as the fees that built it. Its live depth and active range are on the Mason's page and in the HUD.
## Keeper actions
Both buttons on the Wall page are permissionless: **Deploy idle USDG** moves fee USDG that has arrived at the wall manager into the position, and **Rebalance** runs when the contract reports it would accept the call. A scheduled keeper runs the same two calls every ten minutes.
---
# 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-wall.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.
