PrysmHook on Robinhood Chain

Uniswap v4 Hook Contract 0x622d4a429715a38e45ae18dffd98d6e5c5b468cc on Robinhood Chain · Launchpad · Verified contract

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 Uniswap v4 launch hook where each pool carries fixed rules: a fee that decays after launch, up to three fee cuts, a share of fees used to buy back and burn the launched token, and a launch buy cap, with all fees paid in ETH.

How it works step by step

  • Charges a launch fee that falls linearly from startFeeBps to feeBps over decaySecs, with the steady fee capped at 10%.
  • Splits each fee into a protocol share (up to 30%), up to three cut recipients, and a burn pot, with rounding dust going to the pot.
  • Lets anyone run a buyback that spends the pot buying the token from the pool, burns it, and pays the caller a bounty in ETH.
  • Enforces a launch guard that caps per-swap buys as a share of supply for a limited window after launch.
  • Restricts pool initialization and liquidity addition to the launchpad, with no liquidity removal hook.
Swap behaviour
On swaps the hook takes a dynamic fee in ETH: when ETH is the specified side it is taken in beforeSwap, otherwise in afterSwap, minted as PoolManager claims and split between the protocol, cut recipients and the buyback pot. During the launch guard, buys above the per-swap cap revert. Swaps by the launchpad itself are exempt from fees.
Liquidity behaviour
Only the launchpad can add liquidity (beforeAddLiquidity reverts for any other sender). Liquidity removal is not hooked and the curve is intended to be locked, so LPs are the launchpad alone.
Fee behaviour
Fees are charged on the ETH side only: a dynamic fee falls linearly from startFeeBps to feeBps over decaySecs (max 50% start, 10% steady). The fee is minted as ERC-6909 claims inside the PoolManager and split into protocol share (protocolBps, max 30%), up to three cut recipients, and a burn pot. Pool LP fee is fixed at zero.
Owner & admin controls
Owner (set at deploy, transferable via transferOwnership) can: set the launchpad once, set the vault address (which redirects future protocol share), set protocolBps up to 30% of fees for pools launched afterward, and adjust buyback parameters (bounty, caps, interval) within hard-coded bounds. Owner cannot change per-pool Rules after registration, cannot pause swaps, and cannot upgrade the contract.

Enabled Uniswap v4 callbacks

beforeInitialize, beforeAddLiquidity, beforeSwap, afterSwap, beforeSwapReturnDelta, afterSwapReturnDelta

beforeInitialize restricts pool initialization to the launchpad. beforeAddLiquidity restricts liquidity addition to the launchpad. beforeSwap takes the fee on the ETH-specified side and sets the swap delta. afterSwap enforces the launch buy cap and takes the fee on the unspecified side. beforeSwapReturnDelta and afterSwapReturnDelta are enabled so the hook can take fees as deltas.

Security & trust assessment

Risk level: medium (verified source, high confidence).

Who controls it: The owner cannot alter an existing pool's fee, cuts or burn share, nor pause trading. Its real levers are redirecting the protocol share via setVault (future accruals only, plus a flush of existing accruals to the old vault) and raising protocolBps for new launches up to 30%. Buyback parameters are bounded by constants. The launchpad address is set once and is a trusted caller that can register pools.

Risk to user funds: The hook holds ETH claims for fees and pending payouts in the PoolManager and can take fees via return deltas on each swap; it does not hold the token supply beyond what the launchpad sends. Owner cannot seize or freeze user balances or block swaps, but can redirect protocol share and raise its size for new pools. Cut recipients pull their ETH via claim functions, and unclaimed amounts remain in the contract's accounting.

Security findings

  • [medium] Owner controls protocol revenue destination: setVault flushes accrued protocol ETH to the previous vault, and the owner controls where future protocol share goes; a malicious or compromised owner could redirect protocol revenue.
  • [low] Owner can increase protocol share for new pools: Owner can raise protocolBps up to 3000 (30% of fee) for pools launched afterward, reducing fees paid to cut recipients and the burn pot.
  • [medium] Fee accounting relies on PoolManager claims and return deltas: The hook takes ETH-denominated fees via return deltas and holds them as ERC-6909 claims in the PoolManager, and redeemable claims are settled by permissionless functions claim, claimTo, flushProtocol and buybackAndBurn; a bug in the unlockCallback accounting would affect these balances.
  • [info] Permissionless buyback with MEV-aware impact cap: Buyback price-impact limit (fee-based, capped at 5%) and minimum pot size are designed to make sandwiching unprofitable; the bounty is paid from the pot to any caller.
  • [info] Immutable per-pool rules and launch guard: Launch guard blocks buys above maxBuyBps of supply during guardSecs, and no per-pool Rules can change after registration.

Contract details

Verified source
Yes (PrysmHook)
Compiler
solc 0.8.26+commit.8a97fa7a
Bytecode size
16,487 bytes
Upgradeable proxy
No
Detected patterns
launchpad, liquidity-management, ownable, return-delta

Pools using PrysmHook