How to Verify a Liquidity Lock on Arc

A screenshot is not a lock. A tweet is not a lock. A lock is a position held by a locker contract with an unlock timestamp you can read on the explorer, and checking it takes about two minutes.

Works on Arc testnet today; mainnet September 16, 2026.

Why the check matters

Claiming locked liquidity is trivial. Actually locking it is a transaction. The gap between the two is where a large share of losses in this industry live, and the only reliable way to tell them apart is to read the chain yourself.

The check below works on Arc's public testnet at testnet.arcscan.app today, and will work on mainnet with the explorer Circle publishes when public mainnet opens on September 16, 2026.

The five-step verification

1. Find the LP token or position. Get the trading pair for the token. For a Uniswap V2-style pool, the pair contract issues fungible LP tokens. For Uniswap V3 or V4, liquidity is held as a position NFT rather than fungible LP tokens.

2. Open the holders tab. On the explorer, search the LP token contract and open its holders list. This shows who actually controls the pool.

3. Confirm a locker contract holds the position. The locked share should sit at a locker contract address, not at the deployer's wallet or a fresh anonymous address. If the top holder is an EOA, the pool is not locked, regardless of what the project says.

4. Read the unlock timestamp. Open the locker contract and read the position: the unlock date, the amount, and the beneficiary. Verified contracts expose a Read Contract tab for exactly this. How to use Arcscan.

5. Check the proportion. This is the step people skip. A lock covering 8% of the pool while 92% remains withdrawable is not a locked pool. Compare the locked amount to the LP token's total supply.

[SCREENSHOT: Arcscan holders tab for an LP token showing a locker contract as top holder]

Things that look like locks and are not

• A burn address holding LP tokens. That is burnt liquidity, not locked — different property, arguably stronger, but it is permanent and irreversible. Know which one you are looking at.
• Tokens sent to a multisig. Discretionary control by several people is still discretionary control.
• A lock with an unlock date next week. Technically a lock. Practically a countdown.
• A lock on the wrong pair. Some projects lock a thin secondary pool while the primary pool stays open. Check the pair with the actual depth.
• A V3 position locked out of range. A concentrated Uniswap V3 or V4 position parked in a price band far from the market provides no usable liquidity, however long it is locked. Check the range, not just the lock.

Checks worth running alongside

Liquidity is one dimension. Also look at:

Token contract verification. Is the source published and matched? Can the owner mint, pause, blacklist or change fees? Read those functions directly rather than trusting a summary.

Holder concentration. Open the token's holders tab. Supply sitting in locks, vesting contracts and pools is fine. Large anonymous balances are the risk. Team token locks explains what should be locked.

Team allocation. Is it under a vesting schedule with a real cliff, or is it in a wallet? Vesting on Arc.

Four green checks — verified contract, locked liquidity, vested team, sane distribution — do not guarantee a good project. They do rule out the failure modes that are purely mechanical.

If you are the project being checked

Make this easy. Publish the token contract, the lock position, the vesting schedules and the distribution as explorer links in one place, before anyone asks. Then run the verification yourself, as a stranger, and see whether the answers you get match the story you are telling.

Team Finance produces locks and schedules that live in audited, non-custodial contracts with a public position anyone can read — more than $2.7 billion secured across 40,000+ projects on 26 chains since 2020. How to lock liquidity on Arc.

Testnet caveat

Everything on the Arc public testnet, chain ID 5042002, is test data. Tokens there have no value, and a lock on a testnet pool proves your process works, not that your project is funded. Practise the verification there so it is second nature on mainnet. Testnet guide.