Likely dynamic fee hook on Robinhood Chain

Uniswap v4 Hook Contract 0xd29470f5456c6e4a3977a89940752084d3942080 on Robinhood Chain · Dynamic fee

Volume (24h)
$0
Value locked (TVL)
$20.61K
All-time volume
$205.54K
Pools using this hook
1
Swaps (24h)
0 (0 traders)
Total swaps
1,827

What it does

A Uniswap v4 hook on chain 4663 that runs before pool initialization and before swaps, most likely to apply a custom or dynamic fee, though its exact behaviour is unverified.

How it works step by step

  • Runs logic when a pool using this hook is initialized (beforeInitialize)
  • Runs custom logic before every swap (beforeSwap), possibly setting a dynamic fee
  • Exposes liquidity add and remove callbacks (before and after), with unknown logic
  • Exposes donate callbacks (before and after) with unknown logic
  • Exposes BASE_FEE_PIPS, consistent with fee-related behaviour
  • Exposes 'authorized' and 'loot' functions of unknown purpose
Swap behaviour
Runs beforeSwap logic on every swap; the specific adjustment (likely fee override) cannot be determined from decoded bytecode.
Liquidity behaviour
Implements beforeAddLiquidity, afterAddLiquidity, beforeRemoveLiquidity and afterRemoveLiquidity selectors; their logic cannot be determined without source.
Fee behaviour
Exposes BASE_FEE_PIPS and beforeSwap, suggesting the hook may return a dynamic fee override for swaps; exact fee logic cannot be determined from decoded bytecode alone.
Owner & admin controls
No admin controls found.

Enabled Uniswap v4 callbacks

beforeInitialize, beforeSwap

beforeInitialize: runs when the pool is initialized. beforeSwap: runs before each swap and is likely used to set a dynamic fee or adjust swap behaviour.

Security & trust assessment

Risk level: medium, estimated (decoded bytecode, low confidence).

Who controls it: An 'authorized()' function and a 'loot()' function are present but their access control and effect cannot be confirmed from bytecode; a privileged key could possibly alter behaviour if these are admin-gated.

Risk to user funds: Unknown. The hook implements swap and liquidity callbacks and may influence fees, but without source it cannot be determined whether it can hold, move or block user funds.

Security findings

  • [medium] Unverified privileged-looking functions: The hook exposes 'authorized()' and 'loot()' selectors with no verifiable source, so their purpose and whether they move or withdraw value cannot be confirmed.
  • [info] External state reads and initializer checks: The bytecode references an extsload selector and InvalidInitializer error, indicating interaction with pool manager state and initializer checks; the exact flow is unclear from decoding alone.
  • [info] No verified source: Source is not verified, so the full behaviour of the swap and liquidity callbacks cannot be audited.

Contract details

Verified source
No
Bytecode size
4,499 bytes
Upgradeable proxy
No

Pools using Likely dynamic fee hook