Likely oracle hook on Avalanche

Uniswap v4 Hook Contract 0xd84cb2fdb6f3d0ba24ab6fb0b773ec07cd5d0040 on Avalanche · Oracle

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

What it does

A hook that runs after swaps and appears to manage its own positions and currency flows, but its exact purpose cannot be confirmed without verified source.

How it works step by step

  • Enables afterSwap callback
  • Tracks positions via getPositions-related storage
  • Self-unlocks the pool manager and calls unlockCallback
  • Moves currency using take and transfer selectors
  • Exposes an owner() getter suggesting admin control
Swap behaviour
Runs logic after each swap via afterSwap; details of what it does cannot be determined from decoded bytecode.
Liquidity behaviour
No liquidity callbacks are enabled, though the bytecode contains position-related selectors (getPositions) and the ability to move currency via take and transfer.
Fee behaviour
Hook declares only afterSwap permission; fee handling not determinable from decoded functions.
Owner & admin controls
Not stated.

Enabled Uniswap v4 callbacks

afterSwap

afterSwap: runs after each swap and can update internal state or move currency through the pool manager.

Security & trust assessment

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

Who controls it: An owner() function exists, suggesting a privileged key, but its exact powers cannot be confirmed from bytecode alone.

Risk to user funds: The hook can invoke take and transfer on currencies, so it may move pool funds; the scope of user exposure cannot be determined without source.

Security findings

  • [medium] Privileged currency movement: Bytecode includes owner(), unlock and unlockCallback, plus take and transfer selectors, indicating the hook can move pool currency and may be operated by an owner key.
  • [low] Post-swap balance changes: Hook is in afterSwap-only configuration and can influence pool balances after each trade, which may affect LP accounting.
  • [info] Unverified source: Storage layout and selectors suggest position tracking and self-initiated unlock flows, but no verified source is available to confirm correctness.

Contract details

Verified source
No
Bytecode size
14,969 bytes
Upgradeable proxy
No
Detected patterns
moves-currency, self-unlock

Pools using Likely oracle hook