Stack the rules.
Ship the market.
A hook is the rulebook a market runs on: up to five swap-time blocks that execute inside every trade. Stack them in the builder, publish the stack as an onchain blueprint that pays you a royalty whenever another launch runs it, then put a fixed-supply token behind it. Once the pool opens, nobody can touch the rules.
Design · not deployedNext lane on the bench: attaching a hook to a token that already trades. The launcher renders that flow end to end today, and keeps signing disabled until the factory generation behind it ships.
Blueprints registered
Live in the registry. Every launch names the stack it inherits.
Every behavior is public before the first trade clears.
The launchpad owns the position. A withdraw path does not exist.
No admin key can rewrite a pool's rules after it opens.
Publish a stack.
Get paid when strangers ship it.
Save your stack as a blueprint and it goes on the shelf. Each time another launch runs it, a share of the eligible ETH hook fees routes to you. Royalties draw from the LP and pot cuts, so a stack that only burns has no ETH stream to fund one.
Compose a hookWhat each block does
Blocks run inside the swap, on the pool's own callbacks. No keeper, no off-chain trigger, no oracle. Cuts land on exact-input buys; sells pay the LP fee and stop. Every number is set once, before launch, by you.
Caps buy size and taxes bots through the opening guard window.
~160K gas per swapSurge Fees02The LP fee climbs with how much of the pool one trade consumes.
~120K gas per swapAuto Burn03A slice of each buy's actual output goes to the dead address.
~140K gas per swapLP Rewards04An ETH-side share of buys streams to LPs holding range.
~150K gas per swapNth-buy Pot05A public counter fills a pot; the Nth qualifying buy takes it.
~180K gas per swapMarkets running right now
Pick the blocks.
Read the cost.
One block per behavior, five at most. Tune the guard window, the pot cadence or the burn share, and the builder recomputes what a buy actually costs, composed the way the contract composes it. Not added up.
- Five blocks, zero Solidity
- Buy overhead recomputed live, before anything is signed
- Creator split and LP distribution set per launch, never on the blueprint
- Every parameter printed on the token page
The next power-up:
Leveraged hooks.
Markets that lend against their own liquidity, spot and credit on a single balance sheet. The first factory, hook and router contracts are live on Robinhood Chain 4663 with receipts pinned, and opening a market is permissionless. Leverage can take everything you post as equity. Not financial advice.
Read leveraged hooksFrequently asked
What is Ozycahe?
A marketplace for Uniswap v4 hooks with a launchpad built in, on Robinhood Chain (id 4663). Stack up to 5 blocks into a hook, publish it as a royalty-paying blueprint, and launch fixed-supply tokens behind it. Every rule is readable on chain before anyone trades.
Is the Nth-buy pot random?
No. A public counter advances at most once per pool per block, and the Nth qualifying slot wins. It is arithmetic anyone can check on chain. A minimum buy applies, and claimants can redirect the payout.
Where do launches trade?
New launches sell through a bonding curve of 10 tranches, each priced 70% above the last. When the final tranche clears, the launch graduates into a Uniswap v4 pool in the same transaction, hook attached and immutable from then on.
Can rules change after launch?
No. The hook is attached at pool creation and the launchpad holds the LP position with no removal function. What you read on the token page is what runs, permanently.
Who earns the royalty?
The blueprint's author, whenever a launch runs their stack. Royalties draw from the eligible ETH hook fees and are capped at 10% by the contract.
Do I need to write Solidity?
No. The five blocks are the only building material, each exposing parameters, not code. That keeps every launch inside audited paths instead of untested custom logic.
The project token lists after the marketplace opens. Verify the address here before trading; a token's identity is its address plus its chain, never a ticker and never a handle.
Launch a token behind your own hook.
Name the token, pick the stack, choose an instant pool or the curve, set the split, deploy. The hook rides the pool from the first block and never comes off.