Likely custom pricing hook on Ethereum

Uniswap v4 Hook Contract 0x43dceb0002c1fd312a0cf105b3169c173b2f0503 on Ethereum · Liquidity management

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

What it does

A hook that runs custom logic after liquidity is added or removed from a pool, with the ability to adjust settled token amounts, though its exact purpose cannot be confirmed without source.

How it works step by step

  • Runs logic after liquidity is added to a pool (afterAddLiquidity)
  • Runs logic after liquidity is removed from a pool (afterRemoveLiquidity)
  • Has return-delta permissions that can alter the token amounts settled in those operations
  • Contains an outgoing call with a swap selector, possibly to route or rebalance through the pool
Swap behaviour
No swap callbacks.
Liquidity behaviour
afterAddLiquidity and afterRemoveLiquidity callbacks are dispatched and return a delta, so the hook can alter the balances settled after liquidity changes. The exact computation cannot be confirmed without source.
Fee behaviour
Uses the pool's static fee; no fee logic is visible in the decoded functions.
Owner & admin controls
No admin controls found.

Enabled Uniswap v4 callbacks

afterAddLiquidity, afterRemoveLiquidity, afterAddLiquidityReturnDelta, afterRemoveLiquidityReturnDelta

afterAddLiquidity and afterRemoveLiquidity run after liquidity is modified; afterAddLiquidityReturnDelta and afterRemoveLiquidityReturnDelta allow the hook to take or give tokens as part of those operations.

Security & trust assessment

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

Who controls it: No owner or privileged role was identified in the decoded functions, so centralization risk cannot be assessed from the bytecode alone.

Risk to user funds: With return-delta permissions enabled, the hook could in principle take or add tokens during liquidity changes. Whether it does so, and how much, cannot be determined from the decoded bytecode.

Security findings

  • [medium] Return-delta permissions without visible state changes: Both liquidity callbacks are declared view, yet the hook has return-delta permissions. The decoded selectors do not show the delta logic, so the actual behaviour cannot be verified.
  • [info] Outgoing swap call present: The bytecode contains a swap selector, which suggests the hook may call back into the pool manager or a router. The purpose of this call is not clear from the decoded input.
  • [info] Source not verified: No verified source is available and the storage layout is empty, so the hook's logic could not be fully reviewed.

Contract details

Verified source
No
Bytecode size
2,887 bytes
Upgradeable proxy
No
Detected patterns
return-delta

Pools using Likely custom pricing hook