Hook 0x0614…ca40 on Ethereum

Uniswap v4 Hook Contract 0x0614765b9a31003f4f18a65a36d97e851b20ca40 on Ethereum · Other

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

Adds state-tracking logic around liquidity additions, removals and swaps for a Uniswap v4 pool, but its exact purpose cannot be confirmed without verified source.

How it works step by step

  • Runs beforeAddLiquidity to check or record state before liquidity is added.
  • Runs beforeRemoveLiquidity to check or record state before liquidity is removed.
  • Runs afterSwap to update hook state once a swap completes.
  • Stores data in a uint256-keyed mapping at storage slot 0.
  • Exposes view functions for hook permissions, the pool manager address and PPM_DEN.
Swap behaviour
afterSwap runs after each swap to update hook state; it does not alter swap amounts or fees.
Liquidity behaviour
beforeAddLiquidity and beforeRemoveLiquidity are implemented and write a mapping stored at slot 0 keyed by uint256, which appears to track per-call or per-position liquidity state; the exact logic cannot be confirmed without source.
Fee behaviour
Uses the pool's static fee.
Owner & admin controls
No admin controls found.

Enabled Uniswap v4 callbacks

beforeAddLiquidity, beforeRemoveLiquidity, afterSwap

beforeAddLiquidity: runs a check or bookkeeping step before liquidity is added to the pool. beforeRemoveLiquidity: runs a check or bookkeeping step before liquidity is removed. afterSwap: runs logic after each swap executes, with no return delta requested.

Security & trust assessment

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

Who controls it: No owner, admin or upgrade selector was decoded, so no privileged key was identified. Storage is only written by the liquidity callbacks.

Risk to user funds: The afterSwap permission is enabled but no return delta flag is set, so the hook does not take or move swap tokens. Liquidity callbacks can revert and block add or remove operations, but no token transfer by the hook was identified in the decoded selectors.

Security findings

  • [info] Liquidity callbacks update hook state: Hook writes a mapping at slot 0 from both the add and remove liquidity callbacks, so a bug in that accounting could affect LP entry and exit.
  • [info] Standard unimplemented-hook error present: Contract emits or reverts with HookNotImplemented, which is the standard response for unimplemented hook callbacks and is not a risk signal by itself.
  • [low] Limited analysis without source: No verified source, so the purpose of the afterSwap logic and the mapping updates cannot be confirmed from the decoded data alone.

Contract details

Verified source
No
Bytecode size
2,373 bytes
Upgradeable proxy
No

Pools using Hook 0x0614…ca40