Custom Uniswap v4 Hooks: Architecture and Development
We develop custom Uniswap v4 hooks turnkey — from idea to deployment and audit. Uniswap v4 radically changed the architecture: a single singleton contract PoolManager manages all pools, and extensions come via hooks. These are not mere callbacks. Hooks gain control over critical points in a pool's lifecycle: before and after initialization, before and after swaps, before and after adding/removing liquidity. A correctly written hook can implement limit orders, dynamic pricing, fee rebates, MEV capture — without forking the protocol. An incorrect one can lock the pool or become an attack vector. Contact us to evaluate your task — we'll prepare a proposal within 1 day.
How to Properly Configure Hook Flags
Flags and Permissions
The hook address encodes permissions in bits 0–7. For example, BEFORE_SWAP_FLAG (bit 0) and AFTER_SWAP_FLAG (bit 1). If a hook declares getHookPermissions() with afterSwap: true, but the deployment address lacks the corresponding bit — PoolManager reverts on pool initialization. This means the hook contract address is not arbitrary. You need CREATE2 deployment, picking salt until the required bits appear. For a complex hook with 4–5 flags, salt mining is a separate task solved via an off-chain script. We use HookMiner and typically find a valid salt within 10 minutes.
PoolKey and Pool Isolation
Each pool is identified by PoolKey: {currency0, currency1, fee, tickSpacing, hooks}. The hook address is part of the identifier. Two pools with the same tokens and fee but different hooks are separate pools with different liquidity positions. Liquidity cannot be "migrated" between hooks without a full withdrawal and deposit — a key design consideration for multi-hook strategies.
Transient Storage and EIP-1153
V4 heavily uses EIP-1153 transient storage — storage cleared at transaction end. It costs ~100 gas per operation vs. 20,000 gas for SSTORE. Hooks can use transient storage for reentrancy protection without persistent overhead. In our projects, using transient storage saves 15–20% on gas per swap.
Typical Hook Use Cases and Their Challenges
Dynamic Fee Hook
The most popular request: a fee that changes based on volatility. Logic in afterSwap: compute deviation from TWAP, if >threshold — increase fee for the next swap via poolManager.updateDynamicLPFee(). Problem: TWAP needs storage. Using Uniswap v3 TWAP oracle adds 3,000–5,000 gas per swap. Alternative: own rolling TWAP in hook storage, updated in afterSwap. Cheaper (800–1,200 gas) but requires a bootstrap period (7 days for reliable TWAP) and handling first-swap edge cases. A dynamic fee hook is a typical starting project, with costs from $5,000.
Limit Order Hook
beforeSwap checks pending limit orders in the current tick range. Implementation: mapping tick => orders[], traversal when crossing a tick. Main risk: unbounded loop over orders on a single tick — if 500 orders accumulate, one swap crossing that tick may exceed 1 million gas and hit the block gas limit. Mitigation: limit orders per tick to 20, plus a keeper function to batch execute orders (batchExecuteOrders(tick, limit=20)). The keeper runs every 10 blocks, processing up to 20 orders each call. This keeps gas costs under 500,000 per transaction.
MEV Capture via afterSwap Fee Redistribution
Idea: redirect part of the fee from a swap that caused significant price movement (suspected MEV) to a compensation pool for LPs. afterSwap computes price impact; if above 5% threshold, sends additional payment to a vault. Technical challenge: afterSwap receives delta — the balance change. Price impact must be computed from delta and the pool's initial state. The initial state is captured in beforeSwap and stored in transient storage — so afterSwap can compare. This is the classic pattern for paired beforeX/afterX hooks. We implement this with a transient lock to avoid reentrancy.
Development Tools
Foundry is the only sane choice for v4 hooks. The v4-core repository is built for Foundry, and tests follow suit. forge test --fork-url <mainnet> allows testing hooks against the real PoolManager state. The v4-template from Uniswap is the starting point. It includes a proper HookMiner setup for CREATE2 deployment, a base BaseHook with abstractions, and example tests. Slither with custom detectors for v4 — we verify flag correctness, absence of storage collision with PoolManager slots.
Why Transient Storage Matters for Performance
Using SSTORE in a hot path adds +20,000 gas per swap. Transient storage (EIP-1153) costs ~100 gas per operation, saving up to 20% of transaction gas budget. We guarantee your hook will be designed with this optimization — our experience includes over 10 v4 projects, achieving average gas overhead under 9,000 per swap.
Common Hook Development Mistakes
| Mistake | Consequence | Solution |
|---|---|---|
| Incorrect bits in address | Pool fails to initialize | CREATE2 + HookMiner before deployment |
External call in beforeSwap without reentrancy guard |
Possible reentrancy via hook | nonReentrant + transient storage lock |
| Unbounded loop in order book | DoS via gas limit | Limit orders per tick (max 20) + keeper |
Using SSTORE in hot path |
+20,000 gas per swap | Transient storage (EIP-1153) |
Mutating PoolKey in hook |
Impossible — PoolKey immutable | Design logic without changing key |
Development Process
Specification (2–3 days). Formalize hook behavior at each lifecycle point. Which invariants must hold? Example: "Sum of fees always ≥ base fee", "limit order never executed at price worse than stated".
Development (5–7 days). Foundry + v4-template. CREATE2 deployment script with HookMiner. Property-based tests via Echidna on key invariants (10+ properties per hook).
Fork Testing (2–3 days). Tests against real mainnet state: pool initialization, 50 swap scenarios, edge cases (empty pool, single-sided liquidity, 1,000x price impact).
Audit and Gas Profile. Slither + manual review. Gas snapshot via forge snapshot — compare swap gas with and without hook. Acceptable overhead: <10,000 gas per swap for 90% of use cases.
What's Included
- Hook specification and architecture (PDF)
- Source code with tests (Foundry, 90%+ coverage)
- CREATE2 deployment script with salt mining
- Gas profile (forge snapshot)
- Automated audit report (Slither + Mythril)
- Operations guide (Markdown)
- 30 days post-deployment support
Timeline and Pricing
Simple hook (dynamic fee or whitelist) — 1 week, from $5,000. Medium-complexity hook (limit orders, MEV capture) — 2–3 weeks, $10,000–$20,000. Complex multi-hook system — from 4 weeks, $30,000+. Cost is calculated individually after discussing required mechanics. Get a consultation and preliminary estimate within 1 day — write to us.
Quote from official documentation: Uniswap v4 hooks provide a powerful way to customize pool behavior without forking the core protocol.