Can You Lock Uniswap V4 Liquidity? V4 Position Locking Explained
Uniswap V4 liquidity can be locked: a V4 position is an ERC-721 NFT, and Titan Locker holds it until a public unlock date while the owner keeps collecting trading fees. How V4 locking works, what hooks change, and where it's available.
3 min readUpdated First published By Titan Locker
Uniswap V4 changed how pools are built - a single PoolManager contract holds every pool, and each pool can attach a hook, a contract that customizes its behavior - but it did not change the thing liquidity locking depends on: a V4 position is still an ERC-721 NFT owned by an address. That means V4 liquidity locks the same way V3 liquidity does. The position NFT moves into a lock contract with a public unlock date, trading in the pool continues untouched, and the certificate proves to anyone that the liquidity can't be pulled before that date.
What exactly gets locked in a V4 lock
When a liquidity provider mints a V4 position, the V4 position manager issues an ERC-721 NFT bound to that specific position - its pool, price range, and liquidity. Locking the position means transferring that NFT into a dedicated lock contract, which refuses to release it until the unlock date passes. The pool itself, which lives inside the singleton PoolManager, isn't involved in the lock at all - the lock controls who can eventually withdraw the position, nothing else.
Fees keep flowing to the owner
A locked position remains active liquidity: swaps route through it and it keeps accruing its share of trading fees. The lock owner can collect those accrued fees at any time without waiting for the unlock - collection pays out only earned fees and cannot move the position itself. Projects that lock their launch liquidity therefore don't give up the revenue it generates.
What hooks do - and don't - change
Hooks are V4's biggest new surface: per-pool contracts that can adjust fees, gate actions, or add custom logic on every swap or liquidity event. A lock is orthogonal to all of that - it holds the NFT regardless of what the pool's hook does. The practical consequence for traders evaluating a V4-pool token: verify the lock as usual, and separately review the pool's hook, because a lock cannot make a malicious hook safe. The lock removes the liquidity-pull risk; the hook is its own audit surface.
Where V4 locking is available
Titan Locker supports V4 position locking on Robinhood Chain (chain ID 4663), alongside V3 positions and V2-style LP tokens. The allowlisted position manager addresses are in the contract registry. Titan Locker is no longer offered on Stable Chain (chain ID 988). Existing locks there are unaffected: the contracts are immutable and every lock remains verifiable on Stablescan.
Frequently asked questions
Can you lock Uniswap V4 liquidity?
Yes. A Uniswap V4 position is represented as an ERC-721 NFT minted by the V4 position manager, and that NFT can be locked exactly like a V3 position: the lock contract holds it until a publicly visible unlock date, and nobody - including the owner - can withdraw the position early. Titan Locker supports V4 position locking on Robinhood Chain (chain ID 4663).
Can I collect trading fees while a V4 position is locked?
Yes. A locked V4 position keeps earning its share of the pool's trading fees, and the lock owner can collect accrued fees at any time. Collecting moves only the earned fees - the locked position itself cannot be touched until the unlock date.
Do Uniswap V4 hooks affect a liquidity lock?
The lock itself works the same regardless of the pool's hook: it simply holds the position NFT. But hooks are per-pool code that can change how the pool behaves (fees, limits, custom logic), so when evaluating a V4-pool token, review what the pool's hook can do in addition to whether the position is locked - the lock secures the position, not the hook's behavior.
Where can I lock a Uniswap V4 position?
On Titan Locker, V4 position locking is live on Robinhood Chain (chain ID 4663), alongside V3 positions and V2-style LP tokens. Titan Locker is no longer offered on Stable Chain (chain ID 988); existing locks there are unaffected and remain verifiable on Stablescan.
Something unclear or out of date? Tell us in Telegram support