Lock Liquidity vs Burn: Which One Actually Protects Buyers
Lock liquidity vs burn: locking keeps a defined exit for you and a verifiable commitment for buyers, burning gives up the LP forever. Which to choose, and when.
Lock liquidity vs burn is the choice between a dated commitment and a permanent one. Locking keeps your LP tokens in a contract that refuses to release them before a public unlock date; burning destroys the LP tokens so the pool can never be withdrawn. Both answer the same question — "can the deployer take the pool?" — but locking gives you a defined exit and burning removes the question permanently. For a first launch the common middle ground is a lock of twelve months on a majority of the LP, with the remainder kept liquid and disclosed.
The distinction that matters to a buyer is not the word you use. It is whether the claim can be verified onchain, and whether the mechanism has a back door.
What locking liquidity actually does
The Arc Liquidity Locker holds your LP tokens in a contract that exposes four values for every lock: the LP token address, the locked amount, the beneficiary and the unlock timestamp. Properties worth understanding:
- No owner override, no emergency function. Nobody — including Arctools — can release LP tokens before the unlock timestamp. A locker with an emergency withdrawal is not a locker; the same key that rescues the pool can empty it.
- The unlock date is public and fixed once set. A trader does not have to take your word for the duration; they read the timestamp from the contract on the Arc Explorer.
- Fees keep accruing while locked. Swap fees belong to the pool's reserves, which belong to the LP tokens. When you claim after expiry, you receive the LP tokens and every fee they earned in the meantime. Locking delays access; it does not forfeit yield.
- One lock per position, with a separate beneficiary. You can lock from the wallet that holds the LP but name a treasury or vesting address as beneficiary, which is how you commit liquidity on behalf of a project rather than a person.
- Expiry is passive. Nothing happens automatically at the unlock date. The contract simply stops refusing withdrawal, and the beneficiary claims whenever convenient, with no penalty for claiming late.
What burning liquidity actually does
Burning LP tokens means destroying them so that no address can ever redeem the underlying reserves. Two mechanics are used in practice, and they are not equivalent:
- Transfer to an unspendable address. LP tokens are sent to an address nobody controls. The pool's reserves stay in the pair forever and can never be withdrawn. Note that on Arc, value transfers to
address(0)revert, and most ERC-20 implementations rejecttransferto the zero address outright — so this is done with a designated dead address, not0x0. - Call
burn()on the LP token, where the pair implements it, which reduces the LP token's total supply.
Either way there is one genuine advantage: there is no date at which the pool becomes withdrawable. A reader does not have to reason about your intentions at a future date, because the capability no longer exists.
The cost is that you cannot ever migrate the liquidity to a new pool, and you cannot recover the assets. If you burn the LP on a pool that turns out to have a mispriced or unbalanced composition, that USDC is gone.
Lock liquidity vs burn: side-by-side comparison
| Lock liquidity | Burn liquidity | |
|---|---|---|
| Can the pool be withdrawn today? | No, until the unlock date | No, ever |
| Buyer verification effort | Read lock contract + timestamp | Check LP token supply and holder |
| Reversibility | Yes, after expiry | None |
| Swap fees | Accrued to you, claimable at expiry | Accrued into a pool nobody can withdraw from |
| Migration to a new pool | Possible after expiry | Impossible |
| Signal strength | Strong, time-bounded | Strongest, permanent |
| Typical use | First launch, pre-listing credibility | Final commitment, token with no plan to migrate |
| Cost with Arctools | 50 USDC flat per lock | Token transfer gas only |
The last row is worth noting: burning is cheaper, because it is a single LP transfer rather than a locker interaction. If your only goal is strength of signal and you never intend to migrate, burning is both stronger and cheaper.
Which one buyers actually verify
Buyers do not read your announcement copy; they read the chain. What they check, in order of usefulness:
- Who holds the LP tokens? If it is an ordinary wallet, the pool can be pulled at any moment, regardless of what any post says. This is the single check that separates safe from unsafe.
- If it is a locker: what is the unlock timestamp, and does the locker have an admin path? A locker that you deployed and control is not a lock — you can upgrade or pause it. The locker must be immutable for the commitment to mean anything.
- If it is burned: is the LP balance genuinely unreachable? Look at the LP token's holders and total supply. A "burn" to a wallet you control is not a burn, and it is trivially detectable.
- How much of the LP is covered? Locking 3% of supply while calling the pool "locked" is a common and deliberate misdirection. Lock what you say you locked, and disclose the unlocked remainder.
The point that follows from this is uncomfortable but true: an honest partial lock beats a dishonest full one. If you need liquidity for operational reasons, lock 70% and say so — traders can verify 70% as easily as 100%, and the disclosure builds more trust than a vague claim of full commitment.
The unlock date is a promise with an expiry
A lock converts an unbounded risk into a dated one. The pool cannot be pulled before the date — and can be pulled after it. That means the unlock date itself becomes a market event, and traders should treat it as one.
Practical guidance for choosing a term:
| Term | Reads as | Appropriate when |
|---|---|---|
| 30 days | Minimal commitment, fine for a test pool | You are still iterating on the design |
| 3–6 months | Serious, still short-term | Token has a near-term roadmap milestone |
| 12 months | The standard "we are not going anywhere" lock | Almost every first launch |
| 2–4 years | Long-horizon commitment | Project with a multi-year thesis, or a preset allocation |
Two refinements that cost nothing:
- Stagger your locks. Locking in three tranches that expire at different dates means there is no single cliff where the entire pool becomes withdrawable on one day.
- Match the lock to a real event. A lock that expires right before a roadmap milestone you will announce anyway turns a liability into a narrative hook.
What happens to the LP after the unlock date
Teams that plan the lock rarely plan the day after. The options are: claim and hold, claim and remove part of the liquidity to fund operations, claim and burn, or leave it locked by rolling into a new lock. All are legitimate — with one requirement: say which one you intend, in advance. A pool that is "locked for 12 months with an intention to roll over subject to a vote" is a plan. A pool that silently unlocks while holders are not watching is a trap, even if the deployer had no bad intent.
If you are the one holding the position and you want to exit partially, removing liquidity returns your share of both sides plus accrued fees without closing the position entirely. Do not confuse that with the LP token burn mechanic on the Burn Tokens on Arc page — burning a token and burning LP are different actions with different consequences, and only one of them reduces the circulating supply you are trying to influence.
Mistakes to avoid
- Locking in a contract you control. A purpose-built locker with no admin path is the point. A self-deployed "locker" with an owner role is theatre.
- Locking only the token side. Locks apply to LP tokens, which represent both sides. Locking a token balance is not locking liquidity.
- Burning LP on a pool you still need to rebalance. Burning is irreversible; if the initial price was wrong, you cannot fix it. Create the pool carefully — Arc Liquidity Pool Creator shows the opening price before you sign — and lock rather than burn if there is any doubt.
- Framing a lock as protection against price decline. A locked pool still moves with the market. What locking protects against is withdrawal, not impermanent loss.
- Leaving the LP in a wallet until after launch. A bundle launch can forward LP tokens into a locker inside the launch transaction itself, which removes the window in which the pool is unlockable. If you are launching with Arc Bundle Launch, use it.
The short version
Lock if you want a verifiable, dated commitment and the option to migrate later — twelve months on the majority of the LP, stated publicly, with the unlocked remainder disclosed. Burn if you want the strongest possible signal and genuinely will never move the pool. Either way, make sure the claim a buyer checks is the claim you made. To see how it is checked in practice, read how to avoid rug pulls on Arc Mainnet, which walks the verification from the buyer's side.
Locking costs a flat 50 USDC with the Arc Liquidity Locker; there is no percentage and no recurring fee. Arctools is not affiliated with Circle or the Arc Foundation.