Release Lockup (token symbol LKUP) on Sepolia as a univ4_hook launch.

Token: Lockup (LKUP), total supply 1,000,000,000 LKUP with 18 decimals, minted once to the deployer (a separate zero-argument ERC-20, no mint, owner or admin).

Hook: LiquidityLockupHook, a Uniswap v4 hook on the token's native-ETH pool that locks each liquidity position for 30 days after its last add.

Position key: exactly the PoolManager's, keccak256(owner, tickLower, tickUpper, salt), where owner is the sender argument of the liquidity callbacks (the router or PositionManager that called modifyLiquidity; PositionManager uses the NFT tokenId as salt, so each NFT is its own position). afterAddLiquidity with liquidityDelta > 0 sets unlockAt[poolId][positionKey] = block.timestamp + 30 days (every top-up restarts the full 30 days) and emits Locked(poolId, positionKey, sender, tickLower, tickUpper, salt, liquidityDelta, unlockAt). beforeRemoveLiquidity reverts with StillLocked(unlockAt) when liquidityDelta < 0 and block.timestamp < unlockAt; liquidityDelta == 0 (fee collection, which v4 routes through beforeRemoveLiquidity) always passes, as does any removal at or after unlockAt.

The factory's own seed position is locked like any other; the launch never needs to remove it. No deltas, no fee, no funds held, no admin; nothing can extend or shorten a lock except a new add to the same key. Known limit to document: on a shared router such as PoolModifyLiquidityTest, anyone adding to the same (router, range, salt) key restarts that key's lock, so the README and site send LPs to PositionManager.

The symbol is LKUP because LOCK is already a live launch token on this factory (launch 113).

Deploy shape, matching the live Sepolia hook launches 170, 183 and 186 (launch 168 passed the mainnet PoolManager and is not a model): LiquidityLockupHook's only constructor argument is the Sepolia PoolManager 0xE03A1074c86CFeDd5C142C4F04F1a1536e203543; every rate, window and threshold here is a source constant; there is no owner, admin, setter, pause, upgrade or sweep, and no $owner or $token argument.

Permissions are exactly afterAddLiquidity, beforeRemoveLiquidity (low address bits 0x0600), all others false; the constructor calls Hooks.validateHookPermissions and the CREATE2 salt is mined for those bits.

The factory initializes the pool (currency0 native ETH, currency1 LKUP, fee 3000, tickSpacing 60) and seeds one-sided LKUP liquidity, so nothing in the hook may revert that initialize or that liquidity add (launch 138 was parked when a beforeInitialize gate reverted the factory), and the first buy lands in a pool that holds no ETH. All state is keyed by PoolId; a pool on this hook whose currency0 is not native ETH gets zero deltas and no other effect.

Every callback requires msg.sender == PoolManager.

Tests (Foundry, a real v4-core PoolManager deployed in the test, hook at a mined address): a launch rehearsal that initializes at the manifest price, seeds one-sided LKUP liquidity like the factory and makes the first buy into the ETH-less pool; exact-in and exact-out in both directions; dust amounts; a pool whose currency0 is not ETH; direct callback calls from a non-PoolManager address revert; fuzzed sizes; and specifically: removal at unlockAt minus 1 second reverts and at exactly unlockAt passes; a top-up restarts the lock; fee collection (delta 0) works while locked; two PositionManager NFTs on the same range lock independently; the factory-style seed add succeeds; swaps and donations are unaffected.

An independent adversarial review (read-only) must attack: every path that removes liquidity (PositionManager decrease and burn, multicall, delta 0), whether any path can lock liquidity forever or lock someone else's position, the shared-router grief, position-key derivation, and that afterAddLiquidity can never revert the factory's seed add. It reports each finding with the exact call sequence that triggers it.

Website: one static page (dist/index.html) that reads the hook's views and events and pool and position state through Uniswap's Sepolia StateView 0xe1dd9c3fa50edb962e442f60dfbc432e24537e4c, and sends every liquidity action through Uniswap's published Sepolia PositionManager 0x429ba70129df741b2ca2a85bc3a2a3328e5c09b4 (has code, poolManager() is the PoolManager above; never the unguarded PoolModifyLiquidityTest, whose positions anyone can remove).

It shows each position's unlock date and time left (from Locked events, with current liquidity read through StateView), the pool's total liquidity still locked, a lookup by PositionManager tokenId, and for the connected wallet's own PositionManager positions (Locked events whose sender is the PositionManager and whose salt, read as a tokenId, has ownerOf equal to the wallet) a remove button that shows the unlock time and is disabled until then (adding liquidity is left to any v4 PositionManager client and explained in the README, keeping the site small).