A token launchpad is a product that creates new tokens together with their initial market: it standardizes supply, distribution, pricing, and opening trading rules so a launch follows known mechanics instead of ad-hoc arrangements made fresh for every project.
Every launch answers the same questions: how many tokens exist, who gets them at what price, where trading opens, and what rules the market enforces afterwards. A launchpad answers them once, in code, for everyone — which is safer than trusting each project's private arrangement, provided the answers are actually readable rather than merely claimed.
A token's riskiest window is its first blocks after trading opens, when bots race humans to buy ahead of everyone else. Mechanics like launch-window buy caps, extra opening fees, or staged price discovery exist to slow that race down. Hookr's Anti-Snipe block caps each buy at a share of supply for a set number of blocks after the pool opens and adds an extra LP fee during the window; exact-output buys are blocked inside it so the cap cannot be routed around.
Related: Anti-Snipe block reference — Guard-window caps and fees, with the guard's known conflicts documented.
The meaningful difference between launchpads is verifiability: whether the claimed rules are the enforced ones. Hookr pins every release to a manifest verified against live RPC — ordered deployments, runtime contract identities, hook permission flags — and renders each token's per-swap rules next to its chart. Once a pool opens, no owner function can retune its hook: not the creator's, not Hookr's.
Two cautions travel with any launchpad: display metadata like names and tickers is permissionless, so identity is the contract address plus its chain, never the ticker alone; and this protocol is not independently audited.
Related: Data & safety methodology — How Hookr sources and degrades every figure it shows.