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.
DeFi Protocol Development
We design modular DeFi protocols where the math of stablecoins, liquidity, and oracles works flawlessly. Mango Markets is a stress test: the attacker manipulated the spot price through a single account, took a loan against inflated collateral, and withdrew $114 million. The oracle took the price from a single source without TWAP. Not a code bug—it was an architectural decision that became a vulnerability. Our experience shows: any DeFi protocol is a system of bets that all components, from calculations to economic incentives, are correctly aligned simultaneously.
We don't write code under the 'if it works, don't touch it' mindset. We model stress scenarios: cascading liquidations, depegs, flash loans. Only then do we build events that won't break the protocol.
Why are oracles a critical component of DeFi?
Most major DeFi hacks started with oracle manipulation. Let's break down the three layers we use in every project.
Spot price as oracle—not an option. Uniswap v2 spot price can be shifted by a flash loan in one transaction. The price at the end of the block is the only one that enters the state, and the oracle reads it. Attack scheme: borrow via flash loan → buy asset into the pool → price rises → take a loan against inflated collateral → sell asset → repay flash loan. One transaction.
TWAP as protection. Uniswap v3 observe() averages the price over a period (30 minutes). Manipulation requires maintaining the price for several blocks—this is expensive. But TWAP reacts slowly to legitimate changes, opening a window for arbitrage on liquidation during sharp movements.
Chainlink Price Feeds are an aggregation from multiple data providers with a median. Standard for lending. Problem: heartbeat 1–24 hours and deviation threshold 0.5%. If the price doesn't move, the feed may not update for a day. In volatile markets—lag.
| Oracle |
Mechanism |
Manipulation Protection |
Latency |
| Chainlink |
Median from independent providers |
High (decentralization) |
Up to 24h at 0% movement |
| Uniswap v3 TWAP |
Average price over N blocks |
High (hard to maintain) |
30 min – 1 h |
| Pyth Network |
Cross-chain low-latency |
Medium (dependent on publisher) |
Seconds |
In production, we use a two-tier check: Chainlink aggregator + Uniswap v3 TWAP as a verifier. If the discrepancy exceeds N%, the transaction is rejected and the system is paused.
How to protect a DeFi protocol from flash loan attacks?
Flash loans turn any user into an owner of unlimited capital for one transaction. Therefore, when designing contracts, we assume: everyone has access to unlimited capital. This completely changes the threat model.
Legitimate uses of flash loans are arbitrage, liquidation, and self-liquidation. But the protocol must verify that the loan is not used for manipulation: the oracle must not read the price from a pool that can be shifted in one transaction. We add checks on block.timestamp and minimum liquidity depth.
Key Components of DeFi Architecture
| Protocol Type |
Core Mechanism |
Main Risk |
| DEX (AMM) |
x*y=k or concentrated liquidity |
impermanent loss, oracle manipulation |
| Lending |
collateral ratio, liquidation |
bad debt during cascading liquidations |
| Yield aggregator |
auto-compounding strategies |
rug via strategy upgrade |
| Derivatives / Perps |
funding rate, mark price |
liquidation cascades, socialized losses |
| Liquid staking |
stETH-style rebasing |
depegging on mass unstake |
AMM: From x*y=k to Concentrated Liquidity
Uniswap v2 uses x * y = k. LP tokens are ERC-20—each pool issues its own token proportional to the share. Problem: liquidity is spread across the entire curve, most of it unused.
Uniswap v3 and ERC-721 positions: concentrated liquidity—LPs provide liquidity in a range [priceLow, priceHigh]. Capital efficiency up to 4000x for stable pairs. But ERC-721 breaks vault strategies built for ERC-20. Range management is a separate engineering challenge: a position falls out of range when the price moves, stops earning fees, and becomes single-asset. Protocols like Arrakis Finance automatically rebalance. If you build a vault on top of v3, you need your own range manager or integration with an existing one.
Slippage in v3 is calculated via sqrtPriceX96—96-bit fixed-point math. Errors on the frontend lead to discrepancies between visible and actual slippage.
Curve for pairs with close prices (stablecoin/stablecoin, stETH/ETH) uses an invariant combining constant product and constant sum. Lower slippage within the peg range. Contracts are in Vyper, code is mathematically dense, auditing is difficult.
Lending Protocols: Collateral, Liquidation, Bad Debt
LTV defines the maximum loan against collateral. Liquidation threshold is the level for liquidation. The difference is the buffer for the liquidator. Typical example: LTV 75%, liquidation threshold 80%, bonus 5%. If the price drops 20%+, the position is open for liquidation.
Cascading liquidations: many positions are liquidated simultaneously → liquidators sell collateral → price drops → next wave. LUNA/UST 2022 is a classic cascade.
If collateral devalues faster than liquidation, the protocol incurs bad debt. Aave uses a Safety Module (staked AAVE), Compound uses reserves. Without a backstop, bad debt is socialized via dilution of the supply token or netting.
Designing a liquidation system requires modeling stress scenarios: a single liquidation bot failure, high gas, collateral delisting.
Yield Farming and Incentive Mechanics
Liquidity mining distributes governance tokens to LP providers. Problem: mercenary capital—farmers come, sell tokens, leave. TVL is illusory.
Sustainable mechanics: protocol-owned liquidity (Olympus bonding), veToken (CRV locked → boost + governance), locked staking with penalty. The ve-model, if implemented incorrectly, creates governance concentration. A timelock on gauge weight changes and limits on voting power are needed.
What Our DeFi Protocol Development Includes
- Architectural documentation: contract interaction diagrams, liquidation stress tests, oracle calculations.
- Implementation in Solidity 0.8.x with OpenZeppelin 5.x (AccessControl, ReentrancyGuard, Pausable, TimelockController) and Solmate for gas-optimized base contracts.
- Foundry fork tests on real mainnet (Uniswap, Chainlink, Aave) — pre-deployment tests cover all scenarios.
- Audit: at least two independent auditors for TVL over $1M. Code4rena or Sherlock for bug bounty.
- Deployment with Gnosis Safe 3/5 multisig + timelock 48–72 hours.
- Monitoring via Tenderly (alerts, simulations), OpenZeppelin Defender (automation), Forta (on-chain threat detection).
- Post-launch support: updates, patches, upgrades via proxy.
Our Expertise and Experience
We have been developing DeFi protocols since 2020, delivering 30+ projects with a combined TVL of over $150 million. Our clients include protocols in the top 20 by TVL on Ethereum, Arbitrum, and Base. The team consists of certified Solidity developers who have completed ConsenSys Diligence audit tracks.
DeFi basic principles that we apply in practice.
Timelines
- DEX with AMM (Uniswap v2 fork): 6–10 weeks
- Lending protocol (Aave-style, single collateral): 3–5 months
- Yield aggregator with multiple strategies: 2–4 months
- Full-fledged DeFi protocol with governance: 5–8 months including audit
Cost is calculated individually—contact us for a project estimate.
Get a consultation on DeFi protocol architecture—we will analyze the risks and propose an optimal solution.
