How it works

When you launch, HookPad calls HookPadLaunchFactory.createToken. That function deploys your ERC-20, initializes a Uniswap v4 pool at a fixed starting price, deposits the entire token supply as a single sided concentrated position, and mints the resulting position NFT straight to the burn address. A shared hook contract, HookPadHook, is attached to every pool at initialization and handles two jobs on every swap: computing the dynamic trading tax from a per token trade counter, and routing the collected ETH to either the creator's balance in HookPadFeeLocker or the protocol treasury.

Creator first by default

The protocol takes no cut of ordinary buy or sell tax. Creators set their own base rate between 1% and 10% and keep every position in the dynamic schedule except two sell cycle tiers (positions four and five, which route 7% and 5% to the treasury). Accrued tax is held in ETH only, never in the launched token, and is withdrawable through claimFees at any time.

The only tax that does not go to the creator is the flat 60% anti-snipe charge on non-whitelisted buys in the first five seconds after launch. That flow exists as a bot deterrent and is routed entirely to the protocol treasury. It is documented in full on the fee structure page, including how it connects to the planned $HOOKP buyback mechanism.

On chain indexing and metadata

After a successful launch transaction, the frontend registers the token against the indexer database by re-verifying the TokenLaunched event from the receipt. Logo and social metadata are pinned to IPFS through Pinata and mirrored to Supabase Storage as a secondary copy. Market cap and all time high are refreshed from DexScreener on a schedule and written to the database so every open frontend tab receives consistent pricing without waiting for a new swap event.