Documentation

Overview

Every HOODZ in circulation is supported by reserves held in the Hoodz treasury. The protocol never promises a peg. What it defends is backing: the reserve value attributable to each token. Policy expands supply only when the market pays more than backing, and buys HOODZ back when it pays less.

The three tokens

gHOODZ is sHOODZ with the rebase folded into an index instead of the balance: gHOODZ = sHOODZ × 1e9 / index. That makes it safe to use inside contracts that would otherwise be confused by a balance that changes underneath them.

Staking & rebases

Staking locks HOODZ in the staking contract and mints sHOODZ 1:1. Once per epoch the staking contract calls rebase(), which:

1. asks the Distributor to mint the epoch's reward into the staking contract;
2. computes distribute = contractBalance − circulatingStaked;
3. calls sHOODZ.rebase(distribute, epochNumber), which raises total supply and re-prices every gon;
4. advances epoch.end and epoch.number.

New stakes pass through a warmup so that a deposit landing one second before a rebase cannot capture a full epoch of rewards.

The reward rate, and where the APY comes from

The Distributor mints a fixed percentage of supply every epoch. Because an epoch is 8 hours, that percentage compounds 1,095 times a year — which is the only reason the headline numbers look the way they do.

This is Olympus's OIP-18 framework: the rate steps down as supply grows, so early stakers are paid most and the emission slows as the protocol matures.

Treasury & backing

The treasury is the only contract allowed to mint HOODZ, and it only does so against value received. deposit(amount, token, profit) takes in a reserve asset, values it in 9-decimal HOODZ terms, and mints value − profit; the profit slice is what accrues to backing.

Excess reserves — the buffer available for policy and loans — is totalReserves − (baseSupply − totalDebt). Every privileged role (depositor, spender, manager, debtor, reward manager) is registered behind a queue with a block timelock.

Bond markets

A bond market sells HOODZ at a discount in exchange for a reserve asset, vesting over a fixed term. Price is driven by a control variable that decays with time and is retuned toward a target debt level, so the discount widens when demand is weak and narrows when it is strong.

Payouts are recorded as notes denominated in gHOODZ, so a bonder keeps earning the staking rebase while their bond vests.

Hoodz Loans

Hoodz Loans let a holder escrow gHOODZ and borrow the reserve asset against the liquid backing underneath it.

If a loan expires unpaid, the lender claims the escrowed gHOODZ. That is the only way a position closes against the borrower's will — and it depends on time, never on price.

Automated monetary policy

Emissions Manager

Once a day the manager measures the premium of market price over backing. If the premium clears a floor, it mints and sells:

premium  = price / backing − 1
emission = supply × (premium − minimumPremium) / (1 + premium) × baseEmissionRate

Below the floor it emits nothing, so supply never expands into weakness.

Yield Repurchase Facility

Reserves earn yield. Each week the YRF opens a market that spends that yield buying HOODZ back, which raises backing per token for everyone who did not sell.

Convertible Deposits

Depositors hand over reserves for a right to convert into HOODZ at a strike before an expiry. If they do not convert, the reserves come back. The DAO gets a cheap option on permanent capital; the depositor gets upside without dilution risk.

Governance

gHOODZ is an ERC20Votes token, so voting power is checkpointed and delegable. Proposals run through an OpenZeppelin Governor into a TimelockController.

The PONS launch

HOODZ was distributed through PONS, the non-custodial launchpad native to Robinhood Chain. Under the V2 model every token starts on a bonding curve rather than an instant liquidity pool, and graduation migrates the curve reserves into a permanently locked Uniswap v4 position.

The protocol cannot mint a single HOODZ until that has demonstrably happened. HoodzLaunchGuard holds the vault role and will only hand it to the treasury when all three conditions hold simultaneously:

1. IPonsLaunchpad.isGraduated(HOODZ) is true;
2. the graduated LP position is verified locked with no unlock path;
3. a governor-signed arm() happened at least 48 hours earlier.

The guardian can abort() during that window, which resets the clock. The release is one-way and one-shot, and the treasury address is immutable — governance chooses when, never where.

The protocol's share of PONS trading fees flows into FeeRouterBuyback, which buys HOODZ on the graduated pool and burns it.

Contracts

Gas is paid in ETH. Deployed addresses are written to contracts/deployments/<chainid>.json by the deploy script and mirrored in the app's ADDRESSES map.

Risks

• Price risk. HOODZ is not a stablecoin. Backing sets a floor in theory, not a guarantee in practice.
• Dilution. Emissions increase supply. If the premium assumption is wrong, stakers are paid in tokens rather than value.
• Oracle risk. The Emissions Manager reads a price feed. A stale or manipulated feed mis-sizes emissions.
• Governance risk. A sufficiently large gHOODZ holder can pass a proposal. The timelock is the only delay between a decision and its execution.
• Launch risk. A bonding-curve distribution is open to anyone, including a well-capitalised buyer taking a large share of the curve.