ClankerHookStaticFeeV2 on Robinhood Chain

Uniswap v4 Hook Contract 0x3f27fb70d91ad868fd6b94db67cb919b38b7e8cc on Robinhood Chain · Dynamic fee · Verified contract

Volume (24h)
$0
Value locked (TVL)
$4.53
All-time volume
$514
Pools using this hook
24
Swaps (24h)
0 (0 traders)
Total swaps
49

What it does

This hook gives each Clanker token pool a fixed trading fee of up to 10%, with one rate for buys and another for sells, and it can briefly raise that fee for a short window after launch through an MEV module.

This read was written for the hook 0x1aea…e8cc on Base and reused here: the two share a code shape, so constants such as fees, owners and addresses can differ.

How it works step by step

  • Sets a static LP fee per pool, chosen at deployment: clankerFee applies when swapping paired token for the Clanker token's counterpart direction, pairedFee applies to the other direction, both capped at 10%
  • Takes a protocol fee on swaps via beforeSwap and afterSwap return deltas and mints the fee as ERC-6909 claims held by the hook
  • Forwards accumulated hook fees to the factory on subsequent swaps through a burn and take
  • Claims LP fees from the locker contract before swaps via collectRewardsWithoutUnlock
  • Supports an optional MEV module that can raise the LP fee for a short window after pool creation (up to 80%) and blocks liquidity adds while active
  • Restricts pool creation to the factory (initializePool) or open initialization (initializePoolOpen), rejects ETH pools and direct Uniswap initialization
Swap behaviour
Every swap calls _setFee, which sets the LP fee by direction, then takes a protocol fee. For exact-input swaps paying the paired token in, the hook reduces the specified amount and mints the difference. For exact-output swaps receiving paired token, it increases the specified output. For exact-input swaps receiving paired token out and exact-output swaps paying paired token in, the protocol fee is taken from the unspecified side in afterSwap. The protocol fee is protocolFee = LP fee times protocolFeeNumerator, which is set to 0 for cc0.company deployments, so no protocol carve is expected in practice. MEV module and pool extension logic can run on swaps when enabled.
Liquidity behaviour
beforeAddLiquidity reverts with MevModuleEnabled while the MEV module is operational; otherwise adds are allowed. No callbacks on removal.
Fee behaviour
Fees are set per pool at initialization and read on each swap: clankerFee in one direction, pairedFee in the other, both at most 10% (100,000 of 1,000,000). The hook may temporarily raise the LP fee through the MEV module up to 80% for a limited time after creation. The protocol carve is protocolFeeNumerator times the LP fee and is 0 in this deployment, so the protocol fee is effectively zero.
Owner & admin controls
No owner or pause functions were found in the decoded interface. Fee rates are fixed per pool at creation by the factory. The factory is the only caller allowed to create pools with this hook and to initialize MEV modules. The MEV module is set per pool at creation and can disable itself. The hook is not behind a proxy in the decoded data.

Enabled Uniswap v4 callbacks

beforeInitialize, beforeAddLiquidity, beforeSwap, afterSwap, beforeSwapReturnDelta, afterSwapReturnDelta

beforeInitialize reverts to force creation through the factory-controlled paths. beforeAddLiquidity blocks adds during MEV module operation. beforeSwap sets the dynamic fee, claims fees and runs the MEV module. afterSwap settles the protocol fee and runs an optional pool extension. beforeSwapReturnDelta and afterSwapReturnDelta let the hook take a share of swap amounts via deltas.

Security & trust assessment

Risk level: medium (verified source, high confidence).

Who controls it: The factory is the sole authority over pool creation, MEV module setup and extension registration, but this analysis found no direct owner key that can change the fee rates of existing pools. Fee rates are immutable per pool after initialization.

Risk to user funds: The hook holds ERC-6909 claims for protocol fees and can mint them during swaps, but it does not custody LP principal. Swaps and LP positions are otherwise governed by the Uniswap v4 PoolManager. The MEV module can raise fees and temporarily block liquidity adds, which affects user economics rather than custody.

Security findings

  • [info] Hook takes swap value via return deltas: beforeSwap and afterSwap return deltas and mint ERC-6909 claims for a protocol fee, so the hook can take a share of swap amounts; the configured protocol fee is currently zero.
  • [medium] MEV module can raise swap fee up to 80%: mevModuleSetFee lets the assigned MEV module set the LP fee up to MAX_MEV_LP_FEE (800,000) for MAX_MEV_MODULE_DELAY (2 minutes) after pool creation, which can sharply increase what traders pay during that window.
  • [low] Liquidity adds blocked during MEV window: beforeAddLiquidity reverts while the MEV module is operational, so LPs cannot add liquidity to a new pool until the window expires or the module disables itself.
  • [info] Hook fees forwarded to the factory: _hookFeeClaim burns the hook's accumulated ERC-6909 balance and sends it to the factory address set at construction.

Contract details

Verified source
Yes (ClankerHookStaticFeeV2)
Compiler
solc 0.8.28+commit.7893614a
Bytecode size
12,831 bytes
Upgradeable proxy
No
Detected patterns
access-control, dynamic-fee, launchpad, mev-protection, moves-currency, return-delta

Pools using ClankerHookStaticFeeV2