Liquidity management hook on Robinhood Chain

Uniswap v4 Hook Contract 0xb6ed17b6a7ae2b2a52706b27b689e495fd2ba800 on Robinhood Chain · Liquidity management

Volume (24h)
$0.02
Value locked (TVL)
<$0.01
All-time volume
$1.00
Pools using this hook
21
Swaps (24h)
4 (3 traders)
Total swaps
301

What it does

A pool factory and liquidity wrapper that issues LP share tokens, charges traders only the pool's bounded static fee, and splits collected fees between pool creators and the protocol, with no swap callbacks or withdrawal blocking.

How it works step by step

  • Acts as a pool factory and liquidity router: creates pools that use this hook and records them in a registry.
  • Only lets liquidity be added through its own addLiquidity function, which issues LP share tokens (wrapper ERC-20s) for a fixed full-range-style position.
  • LPs can redeem shares through its removeLiquidity function; the hook has no callbacks on withdrawals.
  • Collects accrued LP fees from positions and splits them between pool creators and a protocol fee recipient, claimable later.
Swap behaviour
No swap callbacks. Swaps run at the pool's LP fee, which appears to be limited to a hard-coded minimum and maximum set at pool creation.
Liquidity behaviour
The before-add-liquidity check likely restricts deposits to the hook's own router, so LPs deposit through it and receive share tokens. Remove-liquidity callbacks are disabled, so the hook cannot block withdrawals at the PoolManager level, though LPs with hook-managed positions withdraw by redeeming shares via the hook.
Fee behaviour
Uses the pool's static LP fee, which must fall between hard-coded MIN_LP_FEE and MAX_LP_FEE values whose exact numbers are not visible from bytecode. Collected fees are credited to the pool creator and the protocol fee recipient; the exact split is unknown.
Owner & admin controls
The owner can change the protocol fee recipient and transfer or renounce ownership. No functions for pausing, changing fees, or moving LP funds were found.

Enabled Uniswap v4 callbacks

beforeInitialize, beforeAddLiquidity

beforeInitialize: validates pool setup such as fee bounds and tick spacing and that the hook created it; beforeAddLiquidity: restricts liquidity additions to the hook's own deposit path.

Security & trust assessment

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

Who controls it: An owner key can only redirect the protocol's share of collected fees to a new address. It cannot pause pools or change pool fees based on visible functions.

Risk to user funds: The hook holds LP positions on behalf of share holders and handles fee collection; no swap deductions are possible. No admin path to drain LP principal was found, and withdrawals go through the share-burning removeLiquidity function.

Security findings

  • [info] Hook custodies LP position: Liquidity is owned by the hook and represented by share tokens, so LPs rely on the hook's removeLiquidity logic to exit; no admin gating of withdrawals was observed.
  • [info] Owner limited to fee recipient: The only owner-specific setter found updates the protocol fee recipient address.
  • [info] Unverified source: Fee bounds and the creator/protocol split cannot be confirmed without verified source.

Contract details

Verified source
No
Bytecode size
19,659 bytes
Upgradeable proxy
No
Detected patterns
erc20, erc6909-claims, fee-sharing, moves-currency, ownable, self-unlock

Pools using Liquidity management hook