Launchpad hook on Base

Volume (24h)

$0

Value locked (TVL)

$0

All-time volume

$0

Pools using this hook

1

Swaps (24h)

6 (5 traders)

Total swaps

6

What it does

A token-sale hook that seeds its own liquidity range, tracks tokens sold after each swap, and later closes the sale to the beneficiary, while traders pay only the pool's normal fee and other LPs can withdraw freely.

This read was written for the hook 0xfb26…0040 on Base and reused here: the two run the same code.

How it works step by step

• Appears to run a token sale or launch on a Uniswap v4 pool, seeding a single concentrated liquidity position for a sale token within a set tick range.
• Tracks how many tokens have been sold after each swap and records sale progress (tokens sold, allocation, snapshot).
• Has a close function that ends the sale and likely pulls the hook's liquidity and proceeds out of the pool to a beneficiary address.
• Exposes view data such as the pool key, tick range, swap fee, beneficiary and whether the sale is active or seeded.

Swap behaviour

After each swap the hook updates its sale accounting (tokens sold and related counters) and may mark the sale as finished. It cannot take tokens from swaps because swap return deltas are disabled.

Liquidity behaviour

The hook itself appears to seed and later remove its own liquidity position through the pool manager. It has no liquidity callbacks, so other LPs can add and withdraw freely.

Fee behaviour

Uses the pool's fee, which the hook exposes as a swapFee value; the exact percentage cannot be confirmed from bytecode. The hook takes no extra cut from swaps.

Owner & admin controls

A seeding function and a close function exist. They likely let the deployer or beneficiary start the sale and later end it, withdrawing the hook's own position and proceeds. Exact access restrictions cannot be verified from bytecode.

Enabled Uniswap v4 callbacks

afterSwap

afterSwap: records sale progress and updates state after each trade.

Security & trust assessment

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

Who controls it: The deployer or beneficiary likely controls seeding and closing of the sale position. They can only manage the hook's own liquidity, not traders' funds or other LPs' positions.

Risk to user funds: The hook only moves its own seeded tokens and sale proceeds and takes no fee from swaps. Other LPs' principal cannot be locked or drained.

Security findings

• [info] No swap deductions possible: Swap return-delta permissions are disabled, so the hook cannot take tokens from traders' swaps.
• [info] LP withdrawals unrestricted: Remove-liquidity callbacks are disabled, so the hook can never block other LPs from withdrawing.
• [low] Sale proceeds handled by hook: The close and unlock flow moves the hook's own liquidity and proceeds, likely to the beneficiary. Who can call close is unverified.

Contract details

Verified source

No

Bytecode size

8,405 bytes

Upgradeable proxy

No

Detected patterns

erc20, moves-currency, self-unlock

Pools using Launchpad hook