Likely dynamic fee hook on Polygon

Uniswap v4 Hook Contract 0x9550e2601081c8ccaef3a998ba3daeaf07a540c0 on Polygon · Dynamic fee

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 Uniswap v4 hook on Polygon that runs custom logic around swaps, but without verified source its specific behaviour for traders and LPs cannot be confirmed.

How it works step by step

  • Enables beforeSwap and afterSwap callbacks invoked by the pool manager around each swap
  • Exposes a standard v4 hook interface including initialize, liquidity, and donate selectors that are mostly unimplemented
  • Reverts with HookNotImplemented for callbacks it does not support
  • Storage layout could not be inferred, so state handling is unknown
Swap behaviour
beforeSwap and afterSwap run custom logic on each swap; the exact mechanism is not determinable from the decoded bytecode.
Liquidity behaviour
No liquidity callbacks enabled; the hook exposes view-level liquidity hook selectors that are not active per the permissions.
Fee behaviour
Uses the pool's static fee; no fee-setting function was identified in the decoded selectors.
Owner & admin controls
No admin controls found.

Enabled Uniswap v4 callbacks

beforeSwap, afterSwap

beforeSwap: runs before each swap and is the only swap-side logic the decoded selectors indicate. afterSwap: runs after each swap, likely for accounting or event emission on the swap result.

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 no specific centralized key capability can be confirmed from this input.

Risk to user funds: Unknown. The swap callbacks are nonpayable and could in principle affect swap accounting or take tokens, but the decoded bytecode does not reveal the mechanism, so exposure cannot be determined from this input.

Security findings

  • [info] Limited decodable logic without source: The bytecode dispatches beforeSwap and afterSwap but the decoded functions carry no storage layout and no identifiable owner or admin selectors, so the logic cannot be fully reconstructed.
  • [info] Most callbacks appear unimplemented: The hook references HookNotImplemented, which is a standard revert used for unimplemented callbacks, suggesting most lifecycle callbacks are intentionally stubbed.
  • [medium] Unverified swap-side state changes: The swap callbacks are nonpayable and may modify state or move funds via return deltas, but without source it is unknown whether they do so.

Contract details

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

Pools using Likely dynamic fee hook