Hook 0x0d0b…8044 on Ethereum

Uniswap v4 Hook Contract 0x0d0b16c56171368922d583ba9e2a4833b5f88044 on Ethereum · Other

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

What it does

An afterSwap hook that can adjust swap settlement and appears to apply a whitelist and per-address sell limit to swappers.

How it works step by step

  • Runs logic in afterSwap for every swap in its pool
  • Reads a whitelist mapping keyed by address
  • Reads and updates a per-address uint256 mapping during afterSwap, consistent with a sell cap
  • Returns an afterSwap delta that can adjust settled token amounts
  • Exposes maxSellTokens() and poolManager() views
Swap behaviour
After each swap, afterSwap runs, reads the whitelist and per-address state, and returns a delta that can change the amounts settled for the swap.
Liquidity behaviour
No liquidity callbacks.
Fee behaviour
Uses the pool's static fee. The hook returns a positive afterSwap delta but no fee-setting function was decoded.
Owner & admin controls
No admin controls found. The whitelist mapping (slot 4) is read in afterSwap but no setter selector was decoded, so whitelist management cannot be confirmed from the bytecode.

Enabled Uniswap v4 callbacks

afterSwap, afterSwapReturnDelta

afterSwap: runs logic after each swap, including reading a per-address whitelist and a per-address uint256 mapping updated during the call. afterSwapReturnDelta: lets the hook return a delta that adjusts the swap's settled amounts, so the hook can take or give tokens after a swap.

Security & trust assessment

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

Who controls it: Unclear from the bytecode. No owner or setter was decoded, so privileged-key impact cannot be determined.

Risk to user funds: The hook can alter settled token amounts after swaps through its return delta, so it can take value from swappers or the pool. It does not appear to hold a standing balance of funds from the bytecode alone.

Security findings

  • [medium] Hook can take tokens via return delta: afterSwapReturnDelta is enabled, so the hook can return a delta that changes amounts settled at the end of a swap, meaning it can take tokens from swappers or the pool.
  • [info] Caller-dependent swap logic: afterSwap reads a whitelist mapping and a uint256 mapping (written in afterSwap) keyed by address, suggesting swap outcomes depend on caller status and accumulated state.
  • [info] Possible sell cap: A maxSellTokens() view and a 0xd1ce-slot mapping suggest a sell cap; the cap appears to limit amounts but its enforcement path is only partly visible.
  • [low] Unverified source: No verified source is available, and several selectors are undecoded, so the exact logic of the return delta and the cap cannot be fully confirmed.

Contract details

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

Pools using Hook 0x0d0b…8044