Check you are on the real Hooking
The domain, the house coin, every contract and who controls what. Check them here before you sign anything.
the official site
Hooking is at https://hookingdotfun.com. Its API is at api.hookingdotfun.com. Any other domain that says it is Hooking is not us.
No official social accounts are published yet. Until one is listed on this page, an account that says it speaks for Hooking does not.
$HOOKING
$HOOKING is the Kitchen's own coin, made once by the factory's genesis. Its address: reading
Any $HOOKING sold before launch, or at another address, is not ours.
the contracts
On Robinhood Chain, chain id 4663. These are the addresses this site is built with; each opens on the explorer. A coin page shows its coin's own address.
What each one does and whether it is live: What's live. Their events and reads: Contracts. For agents: llms.txt and the agent skill.
who controls what
No owner on the core. The hook, the coins, the factory, the LiquidityLocker, the FeeRouter and the KitchenRouter have no owner, no setter, no pause and no upgrade. Every split, fee and window is a constant compiled into them. Nobody can change them or take funds from them, us included. A bug in them is fixed only by deploying new contracts.
The menu. The IngredientRegistry's owner, one key the team keeps offline, proposes an ingredient (Flambé, Parachute, Slow cook, Heat, Limit orders). It becomes active 72 hours after the proposal, never sooner. A guardian, a separate key, can pause an ingredient at once, even during its timelock; only the owner unpauses. A pause stops new activity, never what is already open. Neither can touch the core, a coin or a Parachute position.
Blocks. The BlockRegistry's owner approves the block modules and extensions a new coin may name; the guardian can pause one. An approval only gates new launches: a coin keeps the blocks it launched with, and nothing in the registry can change or stop them.
Cashback and referrals. KitchenRewards pays against a Merkle root the owner (or a poster key it sets) posts once a week. A root can be claimed only 24 hours after it is posted, the guardian can veto it until then, and it can never pay out more than KitchenRewards received. Nobody can withdraw from it.
Flambé's house commits the seed chains and reveals; a late reveal costs the vault, never the trader. The keeper holds no special right: every job it runs is open to anyone, for the same reward.
The keys that hold these roles, read from the contracts now. Each owner is one plain key made for this project, kept offline once the deploy is done; there is no multisig.
| Role | Held by, read from the chain now |
|---|---|
| IngredientRegistry owner | reading |
| IngredientRegistry guardian | reading |
| BlockRegistry owner | reading |
| BlockRegistry guardian | reading |
| KitchenRewards owner | reading |
| KitchenRewards guardian | reading |
| KitchenRewards poster key | reading |
| FeeRouter team address | reading |
The owner and the guardian are fixed in each registry when it is deployed: the registry never changes hands, and a lost owner key means nothing new can ever be added, never that funds move. The chain itself, its sequencer and its owners, is trusted as the chain.
audit status
There is no external audit yet. The contracts are tested on a fork of the chain and every static analysis finding has a written verdict. An external audit, a legal read and fresh keys for every role come before mainnet.
impersonation
Copies of launchpads appear with the same name and look. Before you connect a wallet, check the address bar says hookingdotfun.com. This site never asks for your seed phrase or a private key, and nobody needs them to help you: anyone who asks is stealing. A real trade here is one transaction your wallet shows you, to the contracts listed above.
A coin's name, picture and links are what its creator typed. Anyone can launch a coin called $HOOKING; only the address above is it.
report a bug
The security contact is published here with the domain, before launch. Until then, do not post an exploitable bug in public.
Please do not test against other people's funds, and do not post a bug in public before it is fixed. A bug in a contract with no owner cannot be patched in place, so the fix is a new deployment.
