Likely access control hook on Monad

Uniswap v4 Hook Contract 0xc74864a1fcce7e21cdd84e61db97aebf1fc58200 on Monad · Access control

Volume (24h)
$0
Value locked (TVL)
$22.71K
All-time volume
$132.89K
Pools using this hook
3
Swaps (24h)
0 (0 traders)
Total swaps
187

What it does

A small unverified hook that runs custom logic before liquidity is removed from a Uniswap v4 pool, with its exact purpose undetermined.

How it works step by step

  • Enabled only for the beforeRemoveLiquidity callback according to the hook address permission bits
  • Receives the pool key, liquidity modify params and hook data before a position is removed
  • Bytecode exposes the full IHooks interface selectors, but only the removal path is active
  • No storage layout or external calls were decoded, so no further mechanism can be confirmed
Swap behaviour
No swap callbacks.
Liquidity behaviour
beforeRemoveLiquidity is the only enabled liquidity callback; the hook runs logic before liquidity is removed from the pool. The purpose cannot be determined from the decoded input.
Fee behaviour
Uses the pool's static fee.
Owner & admin controls
No admin controls found.

Enabled Uniswap v4 callbacks

beforeRemoveLiquidity

beforeRemoveLiquidity: runs custom logic before a liquidity position is removed, the only callback enabled by the hook address permissions.

Security & trust assessment

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

Who controls it: No privileged role or owner function was identified in the decoded selectors, so the hook does not appear to expose a clear centralization vector.

Risk to user funds: A beforeRemoveLiquidity hook can revert and block liquidity withdrawals, so LP funds could be locked if the logic reverts. Without source this cannot be ruled out.

Security findings

  • [info] Mostly unused callback surface: The hook implements the full set of IHooks selectors, but only beforeRemoveLiquidity is enabled by the address permission bits, so other callbacks are inert.
  • [medium] Unverified removal logic: No source is verified and no storage layout or external calls were decoded, so the exact logic of beforeRemoveLiquidity cannot be confirmed and it could revert or block removals.

Contract details

Verified source
No
Bytecode size
3,466 bytes
Upgradeable proxy
No

Pools using Likely access control hook