Likely custom pricing hook on Ethereum

Uniswap v4 Hook Contract 0x52bf1a8075581c2e40854d3ece7181e1fb41258b on Ethereum · Custom pricing

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

What it does

This hook enables swap and liquidity return-delta callbacks, but its 23-byte bytecode decodes to no functions, so what it does to trader or LP funds cannot be determined from the input.

How it works step by step

  • Bytecode is only 23 bytes, too small to contain meaningful logic, dispatch table, or storage access
  • No dispatched functions or external selectors were decoded
  • Hook permissions indicate return-delta callbacks are enabled, but the code that would implement them is absent or not decodable
  • Behaviour cannot be determined from the provided input
Swap behaviour
Cannot be determined from the decoded bytecode; beforeSwap and beforeSwapReturnDelta are flagged in the address permissions but no implementing logic was decoded.
Liquidity behaviour
Cannot be determined from the decoded bytecode; afterAddLiquidity, afterRemoveLiquidity and their return-delta variants are flagged in the address permissions but no implementing logic was decoded.
Fee behaviour
Cannot be determined from the decoded bytecode; no fee logic was decoded.
Owner & admin controls
No admin controls found.

Enabled Uniswap v4 callbacks

beforeInitialize, afterAddLiquidity, afterRemoveLiquidity, beforeSwap, beforeSwapReturnDelta, afterAddLiquidityReturnDelta, afterRemoveLiquidityReturnDelta

beforeInitialize, afterAddLiquidity, afterRemoveLiquidity, beforeSwap, beforeSwapReturnDelta, afterAddLiquidityReturnDelta and afterRemoveLiquidityReturnDelta are enabled in the address, but their intended purpose cannot be confirmed from the 23-byte bytecode.

Security & trust assessment

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

Who controls it: No owner, admin or upgrade functions were decoded, so no privileged key could be identified from the input; this is not proof that none exists.

Risk to user funds: Return-delta callbacks can take or add value to swaps and liquidity operations, so the hook could in principle hold or redirect user or pool funds, but the decoded bytecode does not show how.

Security findings

  • [high] Return-delta permissions enabled without decodable logic: The address enables beforeSwapReturnDelta and liquidity return-delta callbacks, which allow a hook to alter balances flowing in and out of the pool. The bytecode is only 23 bytes with no decoded functions, so the actual behaviour and any fund-moving logic cannot be verified.
  • [medium] Unverifiable bytecode: No verified source is available and the decoded output is empty, so no review of the contract's logic is possible from the provided input.

Contract details

Verified source
No
Bytecode size
23 bytes
Upgradeable proxy
No
Detected patterns
return-delta

Pools using Likely custom pricing hook