Launchpad hook on Ethereum

Uniswap v4 Hook Contract 0xa4a707987a5d09337d00daf12809a96bbce928cc on Ethereum · Launchpad

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

What it does

This is a launchpad-style hook that gates liquidity and swaps around a timed open phase and settles accumulated pot funds to claimants, but the exact fee rates and which trades pay more or less cannot be determined without verified source.

How it works step by step

  • Initialises a Uniswap v4 pool at a fixed opening tick (OPEN_TICK) and tracks an open/closed lifecycle with an openedAt timestamp and an arm() step
  • Blocks liquidity additions and removals through beforeAddLiquidity and beforeRemoveLiquidity, and limits swaps to the open phase via beforeSwap and afterSwap
  • Runs a time-windowed outcome mechanism (WINDOW, outcome, books, pots, potOf) and lets participants stake and claim owed amounts per outcome through claim, stakes, claimed and owed
  • Uses afterSwap and beforeSwap return deltas, so the hook can take or give currency during swaps to settle the launch mechanics
  • Stores launch parameters in a poolKey and exposes TOKEN, LAUNCH, JAM, PUSH, CLEAR, BENCH and SQRT_OPEN constants, suggesting a token launch or price-discovery flow
Swap behaviour
Swaps are gated by beforeSwap and afterSwap while the hook is open; the hook can adjust deltas during swaps via return-delta permissions, so exact fill and fee treatment depend on the phase and on internal constants that cannot be resolved without source.
Liquidity behaviour
beforeAddLiquidity and beforeRemoveLiquidity are implemented and gate liquidity changes, and afterAddLiquidity and afterRemoveLiquidity selectors exist as views; the hook appears to restrict or track LP activity during the launch rather than letting it be freely added or removed.
Fee behaviour
Fees are not fully determined from decoded bytecode; the presence of LP_FEE, HOOK_FEE_BPS and pots/potOf indicates a hook-level fee that is accumulated into per-outcome pots and distributed to claimants, but the exact fee rate and direction are unresolved.
Owner & admin controls
No owner or admin selectors were decoded; arm() is a nonpayable state-changing function that opens the launch, and its caller restrictions cannot be determined from bytecode alone.

Enabled Uniswap v4 callbacks

beforeInitialize, beforeAddLiquidity, beforeSwap, afterSwap, beforeSwapReturnDelta, afterSwapReturnDelta

beforeInitialize sets up the launch state and pool key; beforeAddLiquidity and beforeRemoveLiquidity restrict liquidity changes; beforeSwap and afterSwap gate and settle swaps; beforeSwapReturnDelta and afterSwapReturnDelta let the hook take or return currency during swaps.

Security & trust assessment

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

Who controls it: arm() appears to be the only state-changing control and its access control is not visible; if it is callable by a privileged key, that key controls when the launch opens.

Risk to user funds: The hook can hold and settle user currency through pots and claim balances and can alter swap deltas, so user funds are exposed to its accounting logic.

Security findings

  • [high] Return deltas let the hook move pool currency: beforeSwapReturnDelta and afterSwapReturnDelta are enabled, so the hook can alter the amounts settled in each swap and take or give tokens, which is a direct mechanism for moving user funds.
  • [medium] Unverified source: No verified source is available, so the outcome, claim and fee logic is inferred from selectors and storage slots and may not match intended behaviour.
  • [medium] Possible gating by launch state: Liquidity and swap callbacks check an open/closed flag and a NotLaunch error, so a bug or unexpected state could block trading or liquidity changes.

Contract details

Verified source
No
Bytecode size
6,739 bytes
Upgradeable proxy
No
Detected patterns
launchpad, return-delta

Pools using Launchpad hook