Launchpad hook on Robinhood Chain

Uniswap v4 Hook Contract 0xb1f141ed0872b60782d598fab455a83b7ee368cc on Robinhood Chain · Launchpad

Volume (24h)
$8.46K
Value locked (TVL)
$1.99K
All-time volume
$8.46K
Pools using this hook
1
Swaps (24h)
111 (58 traders)
Total swaps
111

What it does

A token launchpad hook that creates coin pools and takes a capped trading fee on every swap, split between creators and a treasury, while never blocking liquidity withdrawals.

How it works step by step

  • Launches new tokens (coins) with a fixed supply and creates a Uniswap v4 pool for each one using owner-set launch terms (tick range and fee settings).
  • Takes part in swaps on its launched pools and can adjust swap amounts through return deltas, likely to collect trading fees.
  • Records fees owed to recipients, who can withdraw them with claim or claimTo; a treasury address receives a protocol share.
  • Appears to support a price floor, redemption (redeem), deposits and graduation of coins, so the token's lifecycle is managed by the hook.
  • Checks liquidity additions and pool creation, likely so only the hook itself can set up or add liquidity to its pools.
Swap behaviour
On swaps in launched pools, the hook runs before and after the trade and can take part of the input or output as a fee, crediting it to tracked balances and the treasury. Exact fee rates are not visible in bytecode, but a MAX_FEE_BPS constant suggests a hard-coded cap.
Liquidity behaviour
Adding liquidity is checked by the hook and may be limited to the hook's own launch process. Remove-liquidity callbacks are disabled, so the hook can never block or charge LPs on withdrawals.
Fee behaviour
Swap fees are taken through return deltas and split between owed recipients, likely coin creators, and a treasury. The exact percentages are set per launch terms and bounded by a MAX_FEE_BPS constant whose value cannot be read from bytecode.
Owner & admin controls
The owner can set the treasury address, set the router, and change launch terms (tick bounds and three fee or split parameters) used for future launches. Ownership uses a two-step transfer and can be renounced.

Enabled Uniswap v4 callbacks

beforeInitialize, beforeAddLiquidity, beforeSwap, afterSwap, beforeSwapReturnDelta, afterSwapReturnDelta

beforeInitialize: restricts pool creation to hook-launched coins; beforeAddLiquidity: gates who can add liquidity; beforeSwap: applies fee or price logic and can adjust amounts; afterSwap: records fees and updates coin state; beforeSwapReturnDelta/afterSwapReturnDelta: let the hook take fees from swap amounts.

Security & trust assessment

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

Who controls it: A single owner controls the treasury address, router, and launch terms for future coins. They cannot change the hook code.

Risk to user funds: The hook can take a fee from swaps on its pools, up to an unverified MAX_FEE_BPS cap, and holds fees owed to recipients until they are claimed. LP principal cannot be locked through withdrawal callbacks.

Security findings

  • [low] Swap fees via return deltas: The hook can deduct part of swap amounts on its pools. The cap comes from MAX_FEE_BPS, which cannot be confirmed from bytecode.
  • [low] Owner-set launch terms: The owner can change tick bounds and fee parameters for new launches, presumably within MAX_FEE_BPS.
  • [info] LP withdrawals unaffected: Remove-liquidity callbacks are disabled, so the hook cannot block or tax withdrawals.

Contract details

Verified source
No
Bytecode size
22,403 bytes
Upgradeable proxy
No
Detected patterns
erc20, launchpad, ownable, return-delta, self-unlock

Pools using Launchpad hook