Likely launchpad hook on Robinhood Chain

Uniswap v4 Hook Contract 0x9192fdde5af41a92451c9bd39293915f5d7b2888 on Robinhood Chain · Launchpad

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

What it does

A token-launch hook that sells a seeded token supply to buyers using its own range-based pricing until an authorized party closes the sale; no explicit fee rate was found, buyers pay whatever price that logic sets, and LP withdrawals are never blocked.

How it works step by step

  • Runs a single-token launch pool: the hook is tied to one pool and one token, and a beneficiary is recorded.
  • A seed function deposits the token supply and opens the sale; it brings the token into the hook using transferFrom.
  • Swaps appear to be filled by the hook's own custom pricing logic through the swap return delta, between a lower and upper tick range, instead of only by normal pool liquidity.
  • A close function ends the sale, and a withdrawExcess function lets a privileged party pull out leftover tokens.
  • Adding liquidity from outside is likely restricted through the before-add-liquidity check.
Swap behaviour
Each swap goes through the hook first. The hook can price and settle part or all of the trade itself by moving tokens with the PoolManager, and swaps likely revert once the sale is closed or before it is seeded. Exact pricing and fees cannot be confirmed from bytecode.
Liquidity behaviour
The hook checks adding liquidity and likely blocks outside LPs. Remove-liquidity callbacks are disabled, so the hook can never block or charge withdrawals.
Fee behaviour
No explicit fee rate was found. Sale proceeds appear to collect in the hook for the beneficiary, and any spread is set by the hook's tick-range pricing, which cannot be quantified from bytecode.
Owner & admin controls
A privileged party, likely the beneficiary or deployer, appears able to seed the sale, close it, and withdraw excess tokens. Who exactly is authorized and any limits cannot be verified from bytecode.

Enabled Uniswap v4 callbacks

beforeInitialize, beforeAddLiquidity, beforeSwap, beforeSwapReturnDelta

beforeInitialize: binds the hook to its single pool and sets the starting price; beforeAddLiquidity: gates who can add liquidity; beforeSwap: runs the sale pricing and state checks; beforeSwapReturnDelta: lets the hook fill swaps from its own token inventory.

Security & trust assessment

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

Who controls it: An authorized party, likely the beneficiary or deployer, controls seeding, closing the sale and withdrawing excess tokens. The worst they can do is end the sale early or remove the unsold inventory.

Risk to user funds: Traders' swap amounts pass through the hook's own pricing, and the exact rate cannot be verified from bytecode. LP principal in the PoolManager cannot be locked or taken by the hook.

Security findings

  • [medium] Hook fills swaps with custom deltas: The swap return delta lets the hook decide how much each trader receives. The pricing logic is unverified, so exact rates cannot be confirmed.
  • [low] Sale can be closed: The close function stops the hook's sale activity, and swaps may revert afterwards.
  • [low] Hook holds token inventory and proceeds: Seeded tokens and proceeds sit in the hook, and leftover tokens can be pulled out through withdrawExcess by an authorized caller.
  • [info] LP withdrawals cannot be blocked: Remove-liquidity callbacks are disabled, so any existing LP position can always be withdrawn.

Contract details

Verified source
No
Bytecode size
9,536 bytes
Upgradeable proxy
No
Detected patterns
erc20, moves-currency, return-delta, self-unlock

Pools using Likely launchpad hook