> 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-hatchery.md).
# The Hatchery
Launch a token on Pons from Hoard World, with your own opening buy locked on a schedule you choose.
The Hatchmaster
The Hatchery is Hoard World's front door to **Pons**, Robinhood Chain's launchpad. Pons deploys the token and its bonding curve; the curve graduates into a permanently locked Uniswap v4 pool. The Hatchery adds the one thing a launch on its own cannot prove: the creator's own opening buy is locked on chain, released by a schedule the creator fixed before launching, and nobody can change it afterwards.
{% hint style="info" %}
Live on Robinhood Chain since 3 September 2026. The lock contract and the reward distributor are in the [address table](/protocol/addresses.md), verified with their sources on the explorer.
{% endhint %}
## What you choose
Three choices, in this order, all shown before you hatch:
1. **The mode.** By market cap, or by time.
2. **The step.** A market-cap increment (a multiple of $50,000) or a time step (a week, two weeks, thirty days).
3. **The share.** How much of your locked buy each step releases: 5%, 10%, 12.5%, 20%, 25%, a third or half.
The number of steps follows: enough of them to reach 100%, the last one topping up whatever rounding leaves. Two bounds apply:
* A **time** schedule runs between **30 days** and **365 days** in total.
* A **market-cap** schedule's last threshold is at most **$10 million**.
## What happens when you hatch
One transaction. The Hatchery calls Pons's own launch-and-buy router, which deploys your fixed-supply token (one billion units) and its bonding curve and buys your opening allocation in the same block, straight into the Hatchery. Pons exempts that buy from its launch-window snipe tax. The Hatchery records the lock and the schedule.
You remain the creator where it matters: Pons credits **your** wallet with the creator share of trading fees from the first trade (claimable from the Hatchery's "My eggs" tab or from Pons directly). The Hatchery's only role in your launch is holding what you chose to lock.
Two fees leave with the launch:
| Fee | Amount | Where it goes |
| ---------------------- | --------------------------------- | ------------------------------------------------------------------------------------------------- |
| Pons launch fee | 0.0005 ETH | Pons |
| Hoard World launch fee | $20, paid in ETH at the live rate | Sold for USDG and handed to the [Stock Vault](/the-world/the-nest.md): SPY for nesting Hoardlings |
## Pair assets
A launch trades against one quote asset from its first block, the way Pons allows: **ETH**, **USDG**, or a **Robinhood Stock Token** the Hatchery lists. Pons accepts forty of them as pair tokens (SPY, QQQ, GLD, AAPL, NVDA, TSLA, LLY, MSFT, AMZN, META, GOOGL, PLTR, COST and the rest); the Hatchery lists every one that has a Uniswap v3 pool against USDG holding liquidity, and the form shows the live list. Pair with LLY and your token's pair on Pons reads `TICKER/LLY`: the opening buy is made in LLY, the bonding curve's reserve is LLY, and the graduated pool is token/LLY.
Pons sets the curve's terms per pair asset, in that asset's own units: the phantom reserve the curve opens with and the buys it takes to graduate (4.2 ETH, 8,090 USDG, 10.9 SPY, 26 TSLA, 8.7 LLY …). The form reads both from Pons for the asset you pick.
Every pair asset is priced in dollars the same way, because the lock's value for the reward window and a market-cap schedule need dollars:
* ETH by the 30-minute average of the canonical Uniswap v3 WETH/USDG pool;
* a stock by the 30-minute average of its own Uniswap v3 USDG pool, the deepest one when it was listed;
* USDG by itself.
The pool a stock is priced from is written into the launch at hatch time. Listing a stock, or pointing it at another pool, is an owner action that reaches only launches made afterwards; a hatched token keeps the source it hatched with. A pool whose observation history is shorter than 30 minutes prices from its current tick until the history builds; the deployment grows every listed pool's observation ring so the average is available.
## How the lock releases
**By time.** Every step, the chosen share unlocks. Claim whenever you like; what has unlocked waits for you.
**By market cap.** Every time the token's market cap crosses another threshold, the chosen share unlocks. Thresholds **ratchet**: once reached, a step stays unlocked whatever the price does next, and anyone may record a high on chain so it counts even if it falls back before the creator claims. There is no clock in this mode. If the price never gets there, the lock never opens.
Market cap is the full supply at the live price, converted to dollars:
* on the bonding curve, from the curve's own reserves;
* once graduated, from the token's Uniswap v4 pool;
* the pair asset converted as above: ETH by the WETH/USDG average, a stock by its own USDG pool's average.
The market-cap reading is the pool's price, so it can be moved by trading. That is by design: the thresholds are meant as milestones the market reaches, and moving a pool to a threshold costs real money in fees and slippage.
## The certificate
The moment a token hatches, its creator gets a certificate: a stamped document with the token, the share of supply locked, the schedule and its progress, and the proof anyone can check without trusting the picture: the hatching wallet, the token contract, the lock contract, the launch transaction and a QR code that opens that transaction on the explorer. It can be posted, downloaded as an image or sent as a link to the egg's live page here. Every egg's certificate stays available in the Hatchery's nursery, which lists every launch newest first with each lock's progress.
The image a creator uploads for the token is shrunk in the browser and pinned to IPFS through Hoard World's own endpoint, so Pons and the certificate show the same picture.
## Rewards for launchers
The launchpad's tranche of the feature-user reserve (8/3% of the supply, about 59 HOARD) streams to launchers over a **three-day window** once the Hatchery opens. Each day of the window holds a third of the tranche; every launch made that day commits the dollar value of its opening buy, and when the day closes its bucket is shared by value, no single launch taking more than a quarter of it. Value, not launch count, so spamming launches earns nothing without real ETH locked behind them. Claim after each day closes; whatever is unclaimed 30 days after the window returns to the reserve.
## What the Hatchery cannot do
* Nobody, including Hoard World, can change a schedule, release a lock early, or move a locked token anywhere but to its launcher as the schedule allows.
* The owner's powers are the one-time wiring of the reward distributor and the list of stock pair assets with the pool each is priced from. Listing and delisting reach future launches only; a hatched token keeps its price source.
* Fee routing is permissionless and refuses to sell the fee ETH for more than 1% under the market average.
A launcher can always buy their own token from another wallet outside the Hatchery. The lock is a statement about the wallet that hatched, verifiable on chain, not a claim about every wallet the creator owns.
## Numbers
| Parameter | Value |
| ---------------------------- | ----------------------------------------------------------------------- |
| Hoard World launch fee | $20 in ETH |
| Time schedule, total | 30 to 365 days |
| Market-cap step | multiples of $50,000 |
| Market-cap ceiling | $10,000,000 |
| Supply per launch (Pons) | 1,000,000,000 |
| Pair assets | ETH, USDG, or a listed Robinhood Stock Token |
| Pons curve graduation | 4.2 ETH, 8,090 USDG, or the stock's own threshold (10.9 SPY, 26 TSLA …) |
| Pair-asset price | 30-minute average of its Uniswap v3 USDG pool, fixed per launch |
| Reward window | 3 days, three equal daily buckets |
| Share cap per launch per day | 25% of that day's bucket |
---
# 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-hatchery.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.
