Running live on Pons · Robinhood Chain 4663Markets you can program · Uniswap v4 · Pons
Assemble the hook.Open the market on Pons.
Put together as many as five swap rules, all of them visible, then open a Pons pool straight away or run a bonding curve to find the price first. Either route leaves the rules fixed.
Hooks put out last good read, through block 33971443.
Hooks put out
- Five rules you can composeEvery behaviour can be seen before launch.
- LP locked by the way it is builtThe Pons launchpad keeps the position, and has no function to remove it.
- Set at launch, for goodOnce a launch graduates on Pons, its pool rules cannot be rewritten.
All five blocks
What the hook really does
Every block executes within the swap itself, through the pool's own callbacks — nothing is driven by a keeper, an off-chain trigger or an oracle. The cuts land on exact-input buys; a sell owes the LP fee and nothing more. Each figure below is a parameter you fix before launch, and no one can change it once it is set. Every one of these blocks runs on the Pons launchpad.
Limits early buying and charges an added LP fee in the first blocks.
~160K gas per swapThe fee grows with trade size.
~120K gas per swapBurns part of what a buy actually returns.
~140K gas per swapA share of the fee flows to LPs.
~150K gas per swapA public counter pays out on every Nth buy.
~180K gas per swapThe builder for hooks
Choose the blocks.
See what it costs.
A single block per behaviour, five in total. Move the guard window, the pot cadence or the burn share and the builder works out afresh what a buy really costs — the LP fee, the ETH-side cuts and the output burn combined the way the contract combines them, rather than simply summed. Keep the stack as a blueprint for others to launch with on Pons, or launch it yourself.
- Five blocks, not a line of Solidity
- Overhead on a buy worked out again with every change, well before you sign
- How the creator fee splits and How LP is distributed belong to a launch, never to the blueprint
- Every parameter shown openly on the token page
The LP / pot ETH cut and Auto Burn touch only exact-input buys and nothing else. Auto Burn consumes its share of the tokens a buy actually returns and never builds up an ETH vault. Sells and exact-output buys owe the LP fee and nothing further.
The Nth-buy pot stays deterministic: the public counter moves forward no more than once per pool per block, and the advertised Nth qualifying slot collects the pot. Once funded, a pot stays claim-backed for whoever is scheduled next; nothing can flush it permissionlessly. A qualifying buy has to bind a canonical nonzero recipient, and the production router does that on its own.
See the way it works →For HOOKPs
Put a blueprint out.
Keep a cut.
Assemble a stack, publish it as a blueprint, and collect a royalty from the eligible ETH hook fees each time someone launches behind it on Pons. The LP and pot ETH cuts are what pay that royalty; a stack carrying only Auto Burn earns no ETH share, so there is nothing to pay it from.
Put a hook together- 10x5a52…4aA223 launches · 0–5% royalty
- 20xA181…D60e7 launches · 1% royalty
- 30x8997…6C4F3 launches · 1–3% royalty
- 40x6FBA…7BAb1 launch · 5% royalty
- 50x0053…CFf91 launch · 1% royalty
Questions
Asked often
What exactly is hookp.xyz?
A token launchpad on Pons with its own Uniswap v4 hook builder, running on Robinhood Chain (chain id 4663). Stack as many as five blocks into one hook, launch a fixed-supply token behind it, and every rule can be read on chain before a single trade happens.
Which five hook blocks are there?
Anti-Snipe limits and taxes buying for a fixed number of blocks once a launch graduates. Surge Fees raises the LP fee in step with how much of the pool a trade eats. Auto Burn routes part of the tokens a buy actually returns to the dead address. LP Rewards hands an ETH-side slice of each buy to LPs currently in range. The Nth-buy Pot builds a deterministic pot and pays it to the Nth qualifying buy.
Does the Nth-buy Pot draw at random?
No — nothing about the pot is random. A public counter moves forward no more than once per pool per block, and the Nth qualifying slot takes it: arithmetic anyone can verify on chain. There is a minimum buy, and whoever claims can send the payout elsewhere.
Where does a HOOKP token trade?
A new launch sells down a bonding curve of ten tranches, every one priced 70% over the last. The moment the final tranche clears, that same transaction graduates the launch into a Uniswap v4 pool on Pons, hook already attached and frozen from that point on.
Will HOOKP add leverage?
This is a design on paper, not code in production. Leveraged Hooks would have the hooked market itself extend the credit, instead of a lending vault sitting next to it: a single pool, a single liquidity base, spot and leverage sharing one balance sheet. The trader puts up equity, the market funds the remainder and records the debt against itself, and opening, closing and liquidating all run through that same pool. The credit a market may write is whichever is smallest — its liquidity, the depth a liquidation could genuinely sell into, the $HOOKP bonded behind it, or a protocol limit — so bonding further $HOOKP lifts the ceiling only as far as those other limits already permit and never beyond, which behind a thin market buys nothing at all. It would ship through a bonded module marketplace rather than as a sixth built-in block. Supplying liquidity to such a market means underwriting its credit: once the module's reserve is exhausted, bad debt falls to the pool. Leverage can cost you every bit of the equity you post. Not financial advice.
Which X (Twitter) account is the official HOOKP one?
@userivet — https://x.com/userivet. Verify links before connecting a wallet; an address plus its chain, not a ticker or a handle, is a token's identity.
Which address is the $HOOKP contract?
The source-listed $HOOKP project token is 0x18E674231A58c239Dc7DaeDcffE15Ec3A24cff5c on Robinhood Chain 4663. Always verify the full address before trading. Its listed market is a hookless Uniswap v4 pool. The app verifies the token's launchpad relation at a pinned block before showing project-token market or trade UI; an unavailable result is never inferred as either outcome.
Put a token out behind a hook of your own.
Four steps: name the token, choose the hook, take an instant pool or a bonding curve, set the fee split, deploy. The hook goes onto the pool on Pons and stays as it is.