MEV protection hook on Robinhood Chain

Uniswap v4 Hook Contract 0xc56af11f0172c0f11ab92d2c3964880182c04ac0 on Robinhood Chain · MEV protection

Volume (24h)
$1.71K
Value locked (TVL)
$829
All-time volume
$1.71K
Pools using this hook
1
Swaps (24h)
7 (6 traders)
Total swaps
7

What it does

A Uniswap v4 hook that appears designed to gate trading and liquidity for a token launch, using an owner-controlled trading switch and an address blocklist to limit bots.

How it works step by step

  • Gates swaps on a one-time owner-controlled trading-open flag
  • Checks an address blocklist (bot protection) before swaps and in isBots
  • Tracks liquidity positions by id in a mapping during add and remove liquidity
  • Records post-swap state in afterSwap
  • Exposes an owner-tunable gas limit parameter
Swap behaviour
beforeSwap checks a trading-open flag and blocklist status before allowing a swap; afterSwap performs bookkeeping.
Liquidity behaviour
beforeAddLiquidity and beforeRemoveLiquidity are enabled; the hook appears to track positions by id in a mapping (slot 3) and may gate liquidity provision, possibly tied to the trading-open state. afterAddLiquidity and afterRemoveLiquidity selectors exist in the dispatch table but their permissions are not enabled in the address flags.
Fee behaviour
Uses the pool's static fee. No fee-setting logic is decoded.
Owner & admin controls
Owner (Ownable) can call transferOwnership and renounceOwnership, openTrading (one-way switch enabling trading), setGasLimit (uint256 storage slot 1), and 83c378c3 which sets a boolean mapping of addresses (likely the bot blocklist, read by isBots). The owner is an address stored in slot 0.

Enabled Uniswap v4 callbacks

beforeAddLiquidity, beforeRemoveLiquidity, beforeSwap, afterSwap

beforeAddLiquidity: records or checks position ids in a mapping on liquidity addition. beforeRemoveLiquidity: checks tracked position state on removal. beforeSwap: enforces trading gate and bot checks before swaps. afterSwap: post-swap bookkeeping, possibly observing the token and tracking swaps.

Security & trust assessment

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

Who controls it: The owner can add or remove addresses from the blocklist, control the gas limit used by the hook, and transfer ownership. Ownership can be renounced, which would lock the current settings permanently.

Risk to user funds: The hook does not appear to take custody of tokens or use return deltas. Its main impact is on whether specific addresses can swap or add and remove liquidity, which could prevent users from exiting or trading if the owner blocks them. Exact flows are not confirmed without source.

Security findings

  • [medium] Swap gating by owner-controlled trading flag and blocklist: beforeSwap reads a trading-open flag, so swaps can be blocked until the owner calls openTrading, and the owner can take control of who may trade via the blocklist.
  • [medium] Owner-managed address blocklist: The address-to-bool mapping written by selector 83c378c3 and read in beforeSwap and isBots can block specific addresses from swapping.
  • [low] Owner-tunable gas limit: Owner can set a gas limit parameter that the hook uses, which may affect execution of hook logic.
  • [info] Single owner key controls privileged functions: The contract is Ownable with transferOwnership and renounceOwnership; no timelock or multisig is evident from the bytecode.

Contract details

Verified source
No
Bytecode size
7,388 bytes
Upgradeable proxy
No
Detected patterns
ownable

Pools using MEV protection hook