What Happens When a Liquidity Lock Expires?

You checked a token's lock, and the expiry date is close — now what? Two errors are available: panic (expiry is not a rug) and complacency (an expired lock protects nothing). The honest rule this page unpacks: expiry is not an event, it's a reversion — from that date, treat the liquidity as unlocked until the team extends, because what you knew for certain before, you now merely hope.

What mechanically happens at expiry?

Less than people imagine. When a Team Finance lock reaches its unlock date, the locked assets — LP tokens or a position NFT — become withdrawable by the lock's owner. Nothing withdraws automatically: the pool doesn't drain, the tokens don't move, no alarm fires. The liquidity typically sits exactly where it was, in the same pool, doing the same job. What changed is one word in the trust model: the owner could not remove the liquidity yesterday, and can today. On Arc, both the expiry and anything the owner subsequently does are public — the lock page shows the state, and any withdrawal would print on Arcscan in real time with sub-second finality.

Is an expiring lock a red flag?

By itself, no — every lock ever created has an expiry date, because locks are time commitments, not perpetuities. The signal isn't the expiry; it's what the team does around it. The strong pattern: extending well before the date, unprompted, treating the lock as live infrastructure (why good teams extend early). The neutral-to-weak pattern: expiry arrives, nothing happens, questions get vague answers — not proof of bad intent (teams forget; multisigs are slow), but from your side indistinguishable from pre-exit positioning, which is why the operating rule is reversion: unlocked until re-proven. The genuinely bad patterns: a quiet ownership transfer to a fresh wallet as expiry nears, or expiry followed by partial "rebalancing" withdrawals explained after the fact. Those belong in rug-pattern territory and deserve to be treated as such.

What should you do as a holder?

Turn the date into a diary entry, not a dread. When you first verify a token's lock (the 2-minute check), record the expiry; it's the one scheduled event in your holding that's known months ahead. As it approaches, watch for the extension — a team that extends a quarter out has answered the question before you asked. If expiry arrives un-extended: reassess your position as if the pool were unlocked, because functionally it is — that may mean exiting, trimming, or consciously accepting team risk you previously didn't have to take, but it should be a decision, not a drift. And ask in public — a direct "will the lock be extended?" in the project's channels is a fair question whose answer (or silence) is itself information. The safety checklist treats a near-expiry lock as a conditional pass for exactly this reason.

What should you do as a team?

Never let holders reach this page because of you. The playbook is short: extend early — a quarter before expiry, routinely, so the question never opens (the extension flow takes minutes and a flat USDC fee); announce the extension with the lock-page link, converting maintenance into a trust event; and if you have a legitimate reason to let a lock lapse — migrating liquidity to a new pool, restructuring, winding down — say so before expiry, with the plan and the on-chain steps, because on a chain whose culture is verification (that's Arc's whole audience), silence around an unlock date costs more than almost any honest explanation. An expired lock with an unexplained gap is how solid projects acquire rug rumors they never earned.

FAQ

Does liquidity automatically leave the pool when a lock expires? No — expiry makes withdrawal possible for the lock owner; it doesn't perform one. The liquidity stays put unless the owner acts, and any action is publicly visible on-chain.

Is an expired lock the same as no lock? Functionally, for your risk model, yes: the anti-rug guarantee is gone until the team re-locks or extends. The team's history of honoring locks is context, but context isn't a contract.

Can a team extend a lock after it has expired? The reliable pattern is extending before expiry. Once expired, the honest equivalent is re-locking — creating a fresh lock on the assets — which holders should verify like any new lock.

How do I find a lock's exact expiry date? On the project's public Team Finance lock page, or on-chain via Arcscan. The verification guide walks through both.

A token I hold has its lock expiring next week and the team is silent. What now? Treat the pool as unlocked from the expiry date and size your risk accordingly. Ask publicly about extension plans — and weigh the silence as part of the answer.