Launchpad hook on Ethereum
Uniswap v4 Hook Contract 0x6143bb338cbf03cfdabeb31abd9af54a91cd40cc on Ethereum · Launchpad
- Volume (24h)
- $0
- Value locked (TVL)
- $0
- All-time volume
- $0
- Pools using this hook
- 1
- Swaps (24h)
- 14 (9 traders)
- Total swaps
- 14
What it does
A launchpad hook that burns a capped but unverified fee from swaps and lets an admin lock trading or gate specific traders, while LPs can always withdraw freely.
How it works step by step
- Runs a token launch pool that pairs a launched token with a pair token and can create and seed the pool itself.
- Charges a burn-style fee on swaps through return deltas and tracks a running total of tokens burned (a MAX_BURN_FEE_BPS constant exists, but its value is not readable from bytecode).
- Keeps several admin-set lists and switches (exemptions, a lock or unlock flag, allow or deny style mappings, a tracking toggle) that are checked on every swap.
- Includes owner-style helpers such as withdrawToken and generic execute, multicall and relay entry points whose access rules cannot be confirmed without source.
- Swap behaviour
- Before and after each swap the hook checks several flags and address lists, so swaps may be blocked for some traders or until a launch is unlocked. It can deduct a fee from swap amounts and burn it.
- Liquidity behaviour
- No liquidity callbacks are enabled, so LPs can add and withdraw freely. The hook may add its own launch liquidity through the pool manager.
- Fee behaviour
- Takes a burn fee on swaps capped by a MAX_BURN_FEE_BPS constant whose exact value is unknown from bytecode. Fee tokens are burned and counted in a total-burned figure, and exempt addresses may skip the fee.
- Owner & admin controls
- A privileged account appears able to toggle swap locks, edit several allow or deny style address lists, set referral-style mappings and withdraw tokens held by the hook. Exact caps and roles are not verifiable from bytecode.
Enabled Uniswap v4 callbacks
beforeSwap, afterSwap, beforeSwapReturnDelta, afterSwapReturnDelta
beforeSwap: checks locks, lists and exemptions and can take a fee from the input; afterSwap: can take a fee from the output and record burns; beforeSwapReturnDelta and afterSwapReturnDelta: let the hook change swap amounts to collect the fee.
Security & trust assessment
Risk level: medium, estimated (decoded bytecode, low confidence).
Who controls it: An admin key appears to control swap locks, trader lists, exemptions and hook-held token withdrawals. The worst case is pausing or selectively blocking trading, but LP withdrawals cannot be stopped.
Risk to user funds: The hook can take a burn fee from swap amounts, up to an unverified maximum, and can move tokens it holds itself. LP principal in the pool cannot be locked or drained by this hook.
Security findings
- [medium] Swap gating by admin lists and lock flags: beforeSwap reads multiple admin-written flags and address mappings, so an admin can likely pause swaps or block specific traders.
- [medium] Burn fee via return deltas, cap unverified: The hook can deduct swap tokens through return deltas. A maximum burn fee constant exists, but its value cannot be confirmed from bytecode.
- [low] Token withdrawal function: withdrawToken can move tokens held by the hook contract itself. It cannot reach LP reserves held in the PoolManager.
- [info] LP withdrawals unrestricted: Remove-liquidity callbacks are disabled, so the hook can never block LP withdrawals.
Contract details
- Verified source
- No
- Bytecode size
- 21,430 bytes
- Upgradeable proxy
- No
- Detected patterns
- erc20, erc6909-claims, launchpad, moves-currency, return-delta, rewards, self-unlock