Launch protection
Hooks can slow down bots and large buyers in the first minutes or hours of a new token's pool.
Ask for it
Make a hook that caps how much a single wallet can buy in the first hour after my pool launches.
For the first 10 minutes, charge a 20% fee on buys that drops linearly to 1%.
Only wallets I allowlist can add liquidity. Anyone can swap.
Let me pause and unpause swaps in my pool.
What to specify
| Idea | Say |
|---|---|
| Wallet cap | The cap, the window, and whether it counts per transaction or in total. |
| Decaying launch fee | The starting fee, the ending fee, and how long the decay takes. |
| Allowlist | Who manages the list, and whether it applies to liquidity, swaps or both. |
| Pause | Who can pause, and whether liquidity can still be removed while paused. |
Know the limits
- A hook sees the caller, not the person. Swaps usually arrive through a router contract, so "per wallet" rules are approximate. Someone can also split a buy across many wallets. SuperHooks will explain how the hook identifies the buyer; read that part of its summary.
- Never trap liquidity. If a hook can block removing liquidity, liquidity providers can be locked in. Ask for removal to stay open even when the pool is paused.
- Blocking swaps blocks everyone, including people trying to sell. Use short windows.