Lock Liquidity on Arc Mainnet and Prove It to Traders
Why locking LP tokens is the strongest trust signal on Arc Mainnet, how to choose a lock duration that reads as credible, and how traders verify it onchain.
The short version
7 steps, roughly 9 minutes of clicking. The full walkthrough is below.
- 11. Understand what a lock does and what it does notA lock removes the ability to withdraw pool liquidity before a public date. It does not fix taxes, ownership or supply, so treat it as one risk removed rather than a clean bill of health.
- 22. Choose a duration you can actually defendThirty days suits a pre-listing window, six months reads as credible, twelve months is the common middle ground. The term is fixed once set, so pick one that matches your plans.
- 33. Confirm the LP token and amount you are lockingPaste the pair and check the LP balance the tool reads from Arc Mainnet. Locking the wrong LP token, or a fraction you did not intend, is permanent for the duration.
- 44. Decide the beneficiaryName the address that will receive the LP tokens at unlock. A treasury multisig is safer than a single hot wallet, because only that address can ever claim the position.
- 55. Pay the fee and submit the lockSign the flat 50 USDC service fee and confirm the lock. The locker records the LP token, amount, beneficiary and unlock timestamp, and settles in under a second.
- 66. Publish the lock so traders can verify itShare the locker address, the LP amount and the unlock date, and show buyers how to read the timestamp themselves on the Arc Explorer.
- 77. Plan the unlock before it arrivesNothing releases automatically at expiry. Decide in advance whether the position gets re-locked, reduced or withdrawn, and announce that plan before the date.

Removing liquidity is the most common way a token hurts its holders. The pattern is depressingly simple: a pool is seeded, buyers accumulate, and the liquidity is withdrawn, converting their USDC into the deployer's exit. Because that single action is the dominant rug vector, a verifiable inability to perform it is the most legible trust signal a launch can offer.
The Arc Liquidity Locker holds LP tokens in a contract that will not release them before the unlock timestamp you set. The timestamp is public state, readable by anyone with a block explorer, which is the entire point: buyers do not have to take your word for the lock duration.
Before you start
- LP tokens in your wallet. Any Uniswap V2 pair LP token on Arc Mainnet can be locked, whether you created the pool through Arctools or elsewhere. You need to hold the LP tokens, not the underlying assets.
- A wallet on Arc Mainnet. Chain id 5042, RPC
https://rpc.mainnet.arc.io, explorerhttps://explorer.arc.io. The 50 USDC service fee and the gas are both paid in USDC. - A duration decision and a beneficiary decision. Both are painful to change afterwards, because neither can be changed at all.
- A realistic view of the trade-off. Locking gives up flexibility in exchange for credibility. Decide how much flexibility you need, then lock the rest.
1. Understand what a lock does and what it does not
A lock does exactly one thing: it makes the LP tokens unwithdrawable until the unlock time. That is a large thing. It eliminates the scenario where you, the deployer, drain the pool, and it does so without requiring anyone to trust you, your intentions or your history.
What a lock does not do is make a token safe. A locked pool with an owner that can raise the sell tax to 100%, mint supply into the pool or blacklist sellers is still a token that can hurt its buyers. Those capabilities live in the token contract, not the pool. The Arc Token Checker reports ownership, mint authority, taxes and liquidity status separately for exactly this reason — a clean result requires all of them, and making your Arc token safe walks through the full sequence.
There is also no owner override and no emergency function in the locker. That is a design requirement, not an oversight: a locker with a rescue hatch is a locker that offers no protection, because the key that could rescue a pool could also empty it. If you need flexibility, lock a smaller share and be explicit about which share remains liquid.
2. Choose a duration you can actually defend
Duration is a signalling decision, and the market has a rough convention for reading it:
| Lock duration | What it signals |
|---|---|
| 30 days | Covers a listing or an event window; short but honest |
| 3 months | Minimal commitment; enough to launch, not enough to hold |
| 6 months | Reads as credible for a small project |
| 12 months | The common middle ground for a first launch |
| 2+ years | Long-horizon commitment, usually paired with treasury discipline |
Two failure modes to avoid. The first is a lock so short that it expires while your token still needs the credibility — a lock that ends in three weeks is often read as a plan to exit in three weeks. The second is locking everything for years when you have genuine plans to migrate pools, add a V3 position or raise capital against the position.
A widely used compromise is to lock the large majority of the LP and keep a small, disclosed portion liquid for operational flexibility. The disclosure matters: "80% of LP locked until March 2027, 20% held for pool operations" is a verifiable claim, while "liquidity is locked" while 40% sits in a wallet is the kind of statement that ends communities.
One more useful property: fees keep accruing. Locking delays access to the LP tokens, not the yield they earn. Every swap still pays its 0.30% into the reserves that your LP tokens own, and you collect all of it at unlock.
3. Confirm the LP token and amount you are locking
Paste the pair address; the locker tool resolves the LP token and reads your balance from Arc Mainnet. Check both:
- The right pair. If your token has more than one pool — an old V2 pair from a test, a V3 position, a pair created by someone else — make sure you are locking the pool that actually trades. Verify the pair address on
https://explorer.arc.ioand compare the reserves against what you deposited. - The right amount. You can lock a portion; you cannot partially unlock. If you intend to lock everything, check the figure before signing, because a mistyped amount is unrecoverable until expiry.
4. Decide the beneficiary
The beneficiary is the address that can claim the LP tokens once the unlock time passes. It can be a different address from the wallet submitting the lock, which makes a few useful patterns possible:
- Treasury multisig. The strongest practical choice. The locking wallet does not need to be the address that can eventually claim, so a compromised hot wallet cannot steal the position at unlock.
- Vesting or team allocation. Lock from an operational wallet and name the team or vesting address as beneficiary, so the position is provably earmarked.
- The same wallet. Simple and fine, provided you do not plan to retire that key.
Whatever you choose, treat the beneficiary as a wallet you must still control at unlock. If the key is lost, nobody can claim, and the LP tokens remain locked indefinitely. There is no recovery path.
5. Pay the fee and submit the lock
Sign the flat 50 USDC service fee and confirm. Each lock is recorded separately with its own LP token address, amount, beneficiary and unlock timestamp, so multiple locks — across pools or across portions of the same position — are individually readable.
The whole thing settles in under a second, deterministically; one confirmation is final. When the transaction appears on the explorer, the lock is already in effect. There is no delay window in which the LP tokens are still withdrawable.
6. Publish the lock so traders can verify it
Locking only pays off if people can check it. Publish the locker contract address, the amount locked, the beneficiary if you are comfortable naming it, and the exact unlock timestamp in both block-time and human form.
Then show traders the two-step verification, because a claim you cannot check is not a claim:
- Open the pair on
https://explorer.arc.ioand find the LP token address. - Look at who holds the LP tokens. If the holder is the locker contract, read the unlock timestamp the contract exposes for that lock. If the holder is an ordinary wallet, the liquidity can be withdrawn at any time.
That is exactly the check the Arc Token Checker automates: it locates the pair, reports how deep it is and states whether the LP tokens are locked, burned or sitting in a wallet. Assume every cautious buyer runs it before their first purchase.
7. Plan the unlock before it arrives
Nothing happens automatically at the expiry date. The locker simply stops refusing withdrawal, and the beneficiary claims whenever convenient. There is no penalty for claiming late, and the position keeps earning swap fees in the meantime.
That is also why the unlock date is a communication problem, not just a technical one. Long before the date arrives, say what happens next:
- Re-lock. Rolling the majority forward each period is the cleanest signal, and it keeps the position verifiable.
- Reduce. Partial withdrawal to recover capital is normal position management — see add and remove liquidity on Arc for how a partial exit returns both sides of the pool.
- Withdraw fully. Legitimate if you are winding the project down or migrating, and catastrophic for holder trust if you have not signalled it months in advance.
Silence at the unlock date is read as the beginning of an exit even when it is not one.
What it costs
| Item | Amount | Notes |
|---|---|---|
| Arctools service fee | 50 USDC flat | One payment per lock |
| Gas | Cents | 20 Gwei floor; 100,000 gas = 0.002 USDC |
| LP tokens | Not spent | Still yours, held by the locker until unlock |
| Fees earned while locked | Yours | Accrue into the reserves your LP owns |
Locking is one of the cheapest credibility purchases available: 50 USDC and cents of gas, with no capital surrendered. Compare it against the alternative signal at the same price point — the pool and the ownership contract are the only things buyers check, and you can clear both for 100 USDC of service fees plus gas. If you would rather give up the LP permanently than lock it, burning the LP tokens is stronger and irreversible; the pool creation guide covers when burning is the better choice.
Common mistakes
- Locking a token amount you did not mean to. No partial unlock exists. Double-check before signing.
- Locking the wrong pair. Old pairs and test pools still hold LP tokens. Verify the reserves on the explorer first.
- Choosing a duration shorter than your launch narrative. A lock expiring in three weeks will be noticed.
- Naming a beneficiary you cannot control. Only the beneficiary can claim, and there is no recovery.
- Claiming "liquidity locked" while holding a majority unlocked. Lock a disclosed majority, or do not make the claim.
- Treating a lock as a safety guarantee. Ownership, mint authority and tax ceilings are separate risks that a lock does nothing about.
- Going quiet at unlock. Announce the plan months ahead so a re-lock is read as commitment rather than improvisation.
- Expecting automatic release. Nothing is pushed to you; claim when you choose, at no penalty.
Where to go next
Run the Arc Token Checker on your own token after locking. It is free, needs no wallet, and tells you what a cautious buyer sees: whether an owner still exists, whether supply can be minted, what the tax ceilings are and how the liquidity is held. Whatever it flags is what to fix next, and make your Arc token safe is the ordered checklist for doing so — checker first, then ownership, then liquidity, then supply.
Lock LP tokens on Arc Mainnet until a date you choose and prove it onchain. It costs a flat 50 USDC on Arc Mainnet. Open Arc Liquidity Locker →