Likely access control hook on Robinhood Chain

Uniswap v4 Hook Contract 0xce580fff858e5618ac6caadf9ebaf2e78e6aa880 on Robinhood Chain · Access control

Volume (24h)
$0
Value locked (TVL)
$40
All-time volume
$381.02K
Pools using this hook
81
Swaps (24h)
0 (0 traders)
Total swaps
20,141

What it does

Restricts who can add liquidity to owner-approved LPs and enforces owner-set price/liquidity checks that can block swaps, while charging no extra fee beyond the pool's static fee and leaving withdrawals unrestricted.

How it works step by step

  • Only owner-approved liquidity providers can add liquidity, checked through owner-approved routers that report the real sender.
  • On every swap, it reads the pool's current price and liquidity and applies a per-pool policy that can reject swaps (for example when there is not enough liquidity or price math is out of range).
  • Records a policy for each pool when the pool is created; the owner can set per-pool policy parameters through an unnamed admin function.
  • Never runs on withdrawals, so LPs can always remove their liquidity.
Swap behaviour
Before each swap, the hook checks a per-pool policy against the pool's live price and liquidity and may revert the swap (errors such as not enough liquidity or invalid price). It cannot take any tokens from the swap.
Liquidity behaviour
Adding liquidity is restricted to owner-allowlisted LPs, routed through allowlisted routers. Removing liquidity is never touched by the hook, so LPs can always withdraw freely.
Fee behaviour
Uses the pool's static fee; the hook takes no fees. The policy setter takes two fee-sized values, but their effect and bounds cannot be confirmed from bytecode.
Owner & admin controls
The owner can allow or block LP addresses and routers, and set per-pool policy parameters whose exact limits are not verifiable from bytecode. Ownership can be transferred or renounced.

Enabled Uniswap v4 callbacks

beforeInitialize, beforeAddLiquidity, beforeSwap

beforeInitialize: registers the pool's policy at creation; beforeAddLiquidity: blocks LPs not on the allowlist; beforeSwap: enforces price/liquidity policy checks and can revert swaps.

Security & trust assessment

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

Who controls it: A single owner controls the LP and router allowlists and per-pool swap policies. At worst they can block new liquidity and make swaps revert, but cannot take funds.

Risk to user funds: The hook holds no funds and cannot deduct tokens from swaps or liquidity since return deltas are disabled. LP principal cannot be locked or drained.

Security findings

  • [medium] Gated liquidity provision: Only owner-allowlisted LPs via allowlisted routers can add liquidity; others are rejected.
  • [medium] Swaps can be restricted by owner-set policy: The owner sets per-pool parameters that beforeSwap enforces and that can cause swaps to revert; exact bounds are unknown from bytecode.
  • [info] Withdrawals unrestricted: Remove-liquidity callbacks are disabled, so LPs can always withdraw their principal.

Contract details

Verified source
No
Bytecode size
6,526 bytes
Upgradeable proxy
No
Detected patterns
ownable

Pools using Likely access control hook