Liquidity management hook on Robinhood Chain

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

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

What it does

A hook that manages fixed-range pool liquidity for LPs through share tokens and splits earned LP fees between pool creators and the protocol, while swaps pay only the pool's normal static fee.

How it works step by step

  • Creates and registers pools that use a fixed full-range or preset tick range (fixed lower/upper ticks and tick spacing).
  • Gates liquidity: the beforeAddLiquidity check appears to only allow deposits routed through the hook's own addLiquidity function, which issues share tokens to LPs.
  • Lets LPs withdraw through the hook's removeLiquidity function by burning their shares.
  • Collects LP fees earned by the hook-owned position and splits them between a pool creator and a protocol fee recipient, who can claim them later.
  • Checks at pool creation that the LP fee sits between hard-coded minimum and maximum values.
Swap behaviour
No swap callbacks. Swaps run as normal Uniswap v4 swaps at the pool's static fee.
Liquidity behaviour
Direct liquidity adds are likely blocked unless they come through the hook, which holds the position and mints share tokens to depositors. The hook has no remove-liquidity callbacks, and LPs withdraw by burning their shares via the hook's removeLiquidity function.
Fee behaviour
Uses the pool's static LP fee, which must fall between hard-coded minimum and maximum bounds whose exact values are not visible in the bytecode. Fees collected by the hook's position appear to be split between the pool creator and the protocol fee recipient, with the exact split unknown.
Owner & admin controls
The owner can change the protocol fee recipient address and transfer or renounce ownership. No owner functions to pause swaps, change fees after launch, or move LP funds were found.

Enabled Uniswap v4 callbacks

beforeInitialize, beforeAddLiquidity

beforeInitialize: validates pool setup such as fee bounds and that the pool is created by the hook; beforeAddLiquidity: restricts liquidity adds to the hook's own managed flow.

Security & trust assessment

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

Who controls it: Not stated.

Risk to user funds: LP deposits are held in a hook-owned pool position and withdrawn through the hook's share-burning function, so withdrawals depend on that unverified code. Only accrued LP fees go to the creator and protocol recipients, and swap amounts are never deducted.

Security findings

  • [medium] LP funds held via hook-managed position: Liquidity sits in a position owned by the hook, and LPs rely on the hook's removeLiquidity logic to get their funds back. Because the code is unverified, this logic cannot be fully checked.
  • [info] Owner limited to fee recipient: The only visible admin setter changes the protocol fee recipient. There is no pause or fee-change function.
  • [info] No swap interception: Swap callbacks and return deltas are disabled, so the hook cannot take tokens from swaps.

Contract details

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

Pools using Liquidity management hook