How it works

The lifecycle

1. 01
   Compose

   Stack up to five blocks in the builder. Parameters lock at launch time, so the builder shows the composed buy cost before anything signs.

2. 02
   Publish

   Save the stack to the onchain registry as a blueprint. Publication stamps your address as author and fixes the royalty you chose.

3. 03
   Launch

   Anyone picks a blueprint and launches a fixed-supply token behind it: instant pool, or ten-tranche bonding curve.

4. 04
   Graduate

   When the last tranche sells, the same transaction opens the v4 pool, attaches the hook, and locks the LP position in the launchpad. There is no removal function to call, ever.

5. 05
   Trade

   Every swap runs through the hook's blocks on the pool's own callbacks. No keeper, no oracle, no admin.

Block reference

Cuts land on exact-input buys only. Sells and exact-output buys pay the LP fee and nothing else. That asymmetry is deliberate: the blocks shape entry pressure without taxing exits.

Royalties

A blueprint author earns a share of the eligible ETH hook fees of every launch that runs their stack. Eligible means the ETH-side cuts: the LP stream and the pot cut. Auto Burn destroys token output and never accrues ETH, so a burn-only stack cannot fund a royalty and publishes at 0%. The cap is 10%, enforced by the registry contract, and the rate is fixed at publication so launchers always know the price of borrowing a stack.

Pot arithmetic

The Nth-buy pot is deterministic. A public counter advances at most 1 step per pool per block; when it reaches the advertised N, that buy's recipient claims the pot. A minimum buy of 0.004 ETH qualifies, every qualifying buy must bind a canonical nonzero recipient (the production router supplies one automatically), and a funded pot stays claim-backed for the next scheduled winner. There is no randomness to audit because there is no randomness at all: recompute the counter from the chain and you have the winner.

The curve

A curve launch sells 62% of the fixed 1B supply across 10 tranches, each priced 70% above the one before it. Buyers on tranche one pay the floor; buyers on tranche ten pay roughly 200× the floor, and know it going in. Selling out the final tranche triggers graduation: the raised ETH and remaining supply open the v4 pool, the hook attaches, and the LP position locks, all in the transaction that cleared the last tranche. A launch that never sells out simply keeps trading on the curve; nothing expires.

Leveraged hooks

The first power-up beyond the five blocks: markets that extend credit out of their own liquidity, spot and leverage on one balance sheet. The factory, hook and router contracts are live on Robinhood Chain 4663 with receipts pinned, and opening a market is permissionless. The bonded module marketplace they are designed to arrive through, third parties publishing power-ups behind $OZYCAH bonds, is a labeled design. Leverage can take everything you post as equity. Not financial advice.

Reading the registry

Everything the site shows is a view over public contract state. The typed client wraps the reads:

import { OzycaheRegistry } from "@ozycahe-hooks/sdk";

const registry = new OzycaheRegistry({ chainId: 4663 });

const bp = await registry.blueprint("BP-0031");
// { author, blocks, royaltyPct, launches, feesRouted }

const launch = await registry.launch("0x5eaf…");
// { blueprint, status, tranche, potBalance, params }

// verify an advertised buy overhead yourself:
const quote = await registry.quoteBuy("0x5eaf…", { ethIn: "0.1" });

The quote call runs the same composition the contract runs, as a view function, so third parties can verify any advertised number.