Yes — since December 2024 every Clanker token’s pool is locked for good, in Clanker’s own locker. Why it can’t be pulled, where the risk sits instead, and how to check a Clanker token.
Short answer: yes. Since 12 December 2024, Clanker puts every new token’s pool position straight into its own locker contract, and that contract has no function to take a position out or remove its liquidity — only to collect trading fees. There is no unlock date because there is no unlock. Tokens from Clanker’s first months are locked too, until 12 December 2100. What the lock does not cover is the creator’s own tokens: a dev buy at launch and a vault that opens after a set date can both be sold into the pool. Paste a Clanker token’s address to see the pool lock and the largest holders:
Every Clanker token is created by Clanker’s factory contract, with a fixed supply of 100 billion. Part of the supply can go to the creator — a vault, an airdrop — and the rest goes into a Uniswap pool. In the current version, v4, the creator’s parts together can take up to 90% of the supply; in v3.1 the vault could take up to 30%.
The pool starts with the token alone. Clanker places it in a price range above the launch price, so at the start there is no ETH in the pool — not from the creator, not from anyone. Every ETH in a Clanker pool (or whatever the token is paired with) was paid in by buyers.
The position that holds the pool goes into Clanker’s locker in the same transaction that creates the token. The creator never holds it, so there is nothing for the creator to withdraw.
We read the code of every Clanker locker in use since 12 December 2024 on the chains our check covers — the table is below. None of them can transfer a pool position out or remove liquidity from it. What they can do:
Only the owner of a position can remove its liquidity, the owner is the locker, and the locker only ever “decreases” a position by zero — which is how Uniswap v4 collects fees. On v4 pools a hook runs too, and people often ask whether the hook’s beforeRemoveLiquidity is what keeps the pool in place. It isn’t: Clanker’s hooks don’t implement it at all — more in the section on the hook below.
The exception is Clanker’s first two versions, used from September to 12 December 2024. Each of those tokens got a locker of its own, with an end date: 12 December 2100. After that date the locker’s owner can take the position back. Our check doesn’t recognise these per-token lockers yet and may show “No” for such tokens.
If a pool position sits at one of these addresses, it is locked for good. Addresses are from Clanker’s own SDK; we checked each one’s code.
| Version | Chain | Locker |
|---|---|---|
| v4 | Base, Arbitrum | 0xffa37784d619f228d8b379d287a4d7282e500762 |
| v4 | Ethereum | 0x7d7e4c38899e9b01bf08f3335dd29b1730c25cec |
| v4 | BNB Chain | 0x6aa835e24cd194fb68d2a2b50f8c506e9cca4288 |
| v3.1 | Base | 0x33e2eda238edcf470309b8c6d228986a1204c8f9 |
| v3 | Base | 0x5ec4f99f342038c67a312a166ff56e6d70383d86 |
| v2 | Base | 0x618a9840691334ee8d24445a4ada4284bf42417d |
| CLANKER’s own pool | Base | 0xce0b18f82aa5a1bb67e30aa7c2aba46d21f662cc0x29946cb02829d02af493803e4f8c842ecfc438df |
Every v4 Clanker pool runs through a Clanker hook — a contract Uniswap v4 calls at set moments in a pool’s life. Tokens launched today use ClankerHookStaticFeeV2 or ClankerHookDynamicFeeV2, both built on ClankerHookV2. The first v4 launches, from June 2025, used the same two hooks without “V2”, built on ClankerHook. On 6 October 2026, all 13 Clanker launches on Base in the preceding 100 minutes went to ClankerHookStaticFeeV2.
None of these hooks implements beforeRemoveLiquidity, or afterRemoveLiquidity. Uniswap v4 calls a hook only for what the hook signed up for, and the sign-up is written into the hook’s address: its last 14 bits are a permission mask. Clanker’s hook addresses end in 28cc, 68cc, a8cc or e8cc — four spellings of one mask, in which the bit for beforeRemoveLiquidity is off. When liquidity is removed from a Clanker pool, Uniswap doesn’t call the hook at all. That can’t be switched on later: a hook with other permissions would need another address, and a pool’s hook is fixed when the pool is created.
So the hook isn’t what locks the pool, and it couldn’t unlock it either. The lock is ownership: the position belongs to the locker, which has no way to give it up.
What the hook does do:
beforeInitialize — refuses any pool not created through Clanker’s factory.beforeAddLiquidity — refuses new liquidity while the anti-sniper module is running, at most two minutes after launch.beforeSwap and afterSwap — set the pool fee for the trade and add Clanker’s own fee, a fifth of the pool fee, on top; trigger the locker’s fee collection; in the first two minutes, run the anti-sniper module, which on the V2 hooks can push the fee up to 80%; and run an optional pool extension after the trade. An extension that fails doesn’t stop the trade: the hook catches the error.The pool fee is capped in the hook itself: 10% on the V2 hooks, 30% on the first ones. A static-fee pool has one fee for buys and one for sells, written at launch, and the hook has no function to change them.
| Hook on Base | Since | Fee cap | Address |
|---|---|---|---|
| ClankerHook | Sep 2025 | 10% | 0xb429d62f8f3bffb98cdb9569533ea23bf0ba28cc |
| ClankerHook | Sep 2025 | 10% | 0xd60d6b218116cfd801e28f78d011a203d2b068cc |
| ClankerHook | Jun 2025 | 30% | 0xdd5eeaff7bd481ad55db083062b13a3cdf0a68cc |
| ClankerHook | Jun 2025 | 30% | 0x34a45c6b61876d739400bd71228cbcbd4f53e8cc |
To check it yourself: on Basescan, open the hook’s address → Read Contract → getHookPermissions. For each of the four, beforeRemoveLiquidity and afterRemoveLiquidity come back false. Which hook a token uses is in the factory’s tokenDeploymentInfo, the same call as in the first step of the check below.
A Clanker token is a plain ERC-20 with a fixed supply. Its admin can change the image and the description, and nothing else: no minting, no pausing, no blacklist, no tax. That is why the contract part of a check usually comes out clean for Clanker tokens — the risk sits in who holds the supply, not in the code.
One thing confuses scanners. v4 tokens have a crosschainMint function, but only the Superchain token bridge can call it, and only to recreate tokens that were burned on another Superchain chain — the total stays 100 billion. Scanners that flag any mint function report these tokens as “mintable”. Our check doesn’t, once Clanker’s factory confirms the token is its own.
b07, but anyone can generate an address like that. The reliable test: on Basescan, open Clanker’s v4 factory 0xe85a59c628f7d27878aceb4bf3b35733630083a9, Read Contract → tokenDeploymentInfo, and paste the token address. A real v4 token returns its own address and its locker; anything else returns zeros. Our check asks the same question.0x8e845ead15737bf71904a30bddd3aee76d6adf6c, Read Contract → allocation, paste the token address. You get the amount, the lockup end and the vesting end; the dates are unix timestamps.₸USD (TurboUSD) on Base is a v3.1 Clanker token with about 195,000 holders. On 1 October 2026, 99.998% of its pool position sat in Clanker’s v3.1 locker, and our check reads it as “Liquidity locked: 100% permanently”. Until that day it said “No”: like most scanners, the check knew only the usual lockers. That is the most common way a Clanker token gets a false “liquidity not locked”.
Can a Clanker creator rug pull? Not by pulling the pool — that is impossible. But a creator can sell a dev buy at once and the vault once it opens, and both take ETH out of the pool just as surely, in steps. Look at the holders and the vault date.
Is Clanker liquidity locked forever? For tokens launched since 12 December 2024, yes: the lockers have no unlock date and no unlock function. Older Clanker tokens are locked until 12 December 2100.
Who gets the trading fees? The reward addresses set at launch — usually the creator. Clanker’s share is 20%: in v3.1 the locker keeps it out of the pool fee; in v4 the hook charges it on top, as a fifth of the pool fee. Fees don’t touch the pool’s liquidity; they are taken from trades.
Does the Clanker hook block liquidity removal? No, and it couldn’t. ClankerHookV2 and the first v4 hook, ClankerHook, don’t implement beforeRemoveLiquidity, so Uniswap v4 never calls them when liquidity is removed. The pool stays because the locker owns the position — not because of the hook.
Why does a scanner say “liquidity not locked” for my Clanker token? Most scanners recognise a fixed list of lockers — UNCX, Team Finance, PinkLock — and Clanker’s aren’t on it. For v4 tokens they often can’t see the pool at all and show no data. Our check reads Clanker’s lockers and asks its factory.
Is Clanker only on Base? No. v4 also runs on Ethereum, Arbitrum and BNB Chain, which our check covers, and on a few chains it doesn’t.
Does a locked pool make a Clanker token safe? No. It means the pool can’t vanish in one transaction. Who holds the supply, when the vault opens and whether anyone keeps buying decide the rest.