> 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-nest.md).

# The Nest

Where a nested Hoardling's hoard grows into SPY.

<div align="left"><figure><img src="https://625424341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8KaGkSrEXERc4n5jJ81O%2Fuploads%2Fgit-blob-50a11dc563e9c9dab92b9c26a67b22c207d454dd%2Fkeeper.png?alt=media" alt="The Nest Keeper" width="150"><figcaption><p>The Nest Keeper</p></figcaption></figure></div>

The Nest is where a Hoardling's hoard grows. Deposit a whole Hoardling and, from that moment, it earns a share of everything the **Stock Vault** receives.

## What feeds the Stock Vault

* **1.5% of every canonical trade.** Half of the 3% fee on the HOARD/USDG pool.
* **40% of interest actually paid** by borrowers at the Bank.
* **The East District's fees**, once it opens: the launch fee at the Hatchery and the builder fees from the Seer's Tent and the Arena.

The vault holds USDG until a keeper batch-buys **SPY**, the tokenized stock, through a Uniswap v4 USDG/SPY pool with a slippage bound. Batching keeps execution cheap and market impact small.

## How rewards are counted

* The vault keeps a cumulative per-Hoardling index. A Hoardling entering the Nest starts earning from that point; it never receives fees that arrived before it.
* Entitlement is recorded when the fee USDG reaches the vault, not when a later SPY purchase executes, so nobody can slip in ahead of a batch to capture older fees.
* If no Hoardling is nested when a fee arrives, that fee's vault share goes to the wall instead.
* Accrued entitlement belongs to the depositor account. It becomes SPY you own when the vault transfers it to you at claim.
* Unnesting settles what is pending. A Hoardling bound to a loan keeps earning for as long as it stays bound.

## Claiming

Press **Claim SPY** in the Nest. The app settles every nested Hoardling that still has accrual pending, then claims the settled balance as SPY, paid pro-rata to the SPY the vault has actually bought.

Claims are gated by the **EligibilityGate**: an on-chain allowlist written by attestors, the accounts the verification provider signs with, under an owner that can add or remove attestors. The vault asks the gate before every claim. Nothing in the gate moves funds; an entry can only let a claim through or hold it. At launch the gate is open: every account may claim. The owner can close it, which returns claims to the attestor list.

## What the Stock Vault is

The vault is a reward pool for nested Hoardlings. It is never lent, it is not part of the wall, and it is not an input to the HOARD price oracle. SPY here is a tokenized stock: economic exposure to the share price, reflected through the token's own multiplier for dividends and splits.


---

# 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-nest.md?ask=<question>&goal=<user_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.
