Start here
The Hood — documentation
What The Hood is, which chain it runs on, and which of its data is public and how to reach it.
What The Hood is#
The Hood is a token launchpad on Robinhood Chain. A creator sends one transaction and gets a fixed-supply token on a bonding curve; when the curve raises its target it graduates into a Uniswap V4 pool whose liquidity nobody can withdraw. Creators earn a share of every trade, on the curve and in the pool afterwards. A second surface, parimutuel prediction markets, sits beside it and settles by reading those same launch contracts on the same chain. A third — the platform token, THD, and the reward mechanics it funds — is written and is not deployed.
Everything the platform does is on chain as an event. There is no lifetime volume accumulator, no off-chain database behind a published figure, and no metric that only an API could answer — so every figure in the metrics reference can be re-derived by anyone with an RPC endpoint and the addresses below.
| Surface | Contracts | What it produces | Deployed? |
|---|---|---|---|
| Launchpad | contracts/src/launchpad/ | Launches, curve trades, graduations, locked pools, trade fees, launch fees, referral and KOL allocations | Yes |
| Prediction markets | contracts/src/predict/ | Markets on a launch’s own outcome, stakes, settlements, voids, the holder census and pool samples | Yes |
| The THD reward layer | contracts/src/thd/ | The eleven allocations and the fee meter that unlocks them; Spoils, the Fortune Wheel, the battlepass, the item mall, quests, bands, seasons, and the burn/recycle holder vote | Partly. The token, the unlock contract and the liquidity manager are deployed in a superseded generation. Every mechanic listed here is written and deployed nowhere. |
What is public today#
Two things are served from this origin today and neither needs an account, a key or a conversation with us. The third is not built yet and this documentation does not describe it.
| Surface | Where | Status |
|---|---|---|
| Addresses, per chain | /addresses/index.json, /addresses/<chainId>.json | Available |
| ABIs | /abis/<Contract>.json | Available |
| Metric definitions | /docs/metrics | Available |
| Chain data | The chain itself, over its public RPC | Available |
| Public Data API | /api/v1 | Available |
Conventions every figure obeys#
| Kind | Encoding | Why |
|---|---|---|
| Amounts | Decimal strings of wei or token base units | A wei value that round-trips through a JSON number has been silently rounded. Never Number(), never parseFloat. |
| Block numbers | Decimal strings | One parsing path rather than two, and no day on which this chain’s height needs more than 53 bits. |
| Addresses | Lowercase hex | Comparable without a checksum step. |
| Times | { unix: string, iso: string } | Unix seconds as a decimal string; ISO-8601 in UTC beside it. |
| Currencies | Never summed across currencies | A market stakes in whatever currency it was created with. Adding two of them produces a number that is not any amount of anything. |
A consumer that treats an amount as a number will be wrong by less than a wei until it is wrong by a great deal. In TypeScript the fix is one line:
// Correct — the string survives JSON intact, BigInt parses all of it.
const volume = BigInt(response.curveVolumeWei);
// Wrong — silently rounded above 2^53, and irrecoverably.
const volume = Number(response.curveVolumeWei);Where to go next#
Platform#
Developers & API#
- Public Data APITwenty read-only endpoints under /api/v1: the response envelope, the versioning contract, and the two conventions — base-unit strings and block-denominated freshness — a consumer gets wrong first.
- Chains and environmentsThe two chains The Hood deploys to, their RPC endpoints, explorers and index floors, and why a testnet figure is not comparable with a production one.
- The addresses fileOne generated JSON file per chain naming every contract, treasury, prior factory and index floor an integrator needs, served from this origin.
- How to read a metric definitionThe seven fields every figure carries, the five rules that bind all of them, and the accumulators that exist on chain.
- VolumeBonding-curve volume, post-graduation pool volume and refunds — what each is summed from and why one of them is always partial.
- Valuation and priceCurve FDV until graduation, the seven-day pool floor afterwards, and the coverage test that decides whether the floor may be published at all.
- HoldersThe on-chain census, what it excludes, why an uncounted token is unknown rather than zero, and the log-derived fallback.
- Prediction marketsPer-currency volume and open interest, the three end states a market can reach, and the predicate that makes a question machine-readable.
- Launches and graduationLaunch counts net of dev launches, the graduation-rate denominator as a published choice, net raised, and the three burn sites.
- Fees, by legThe five revenue lines, which are protocol fees, the event carrying the wei of every hop from a trade to the treasury, and the two flat creation fees.
- Value lockedFour components published separately: live curve reserves, locked launch pools, the THD pool and open market stakes.
- THD and the fee meterThe protocol fee meter, the unlock it drives, the eleven buckets, and why an unlock percentage is meaningless without its denominator.
- Creators, KOLs and referrersThe creator tier ladder and its four caveats, the two competing authorities for KOL earnings, and what is never published about a referral.
- Figures we do not publishFifteen figures that are derivable and wrong, with the reason each one is refused.