Why locking LP matters

When a token launches, the team pairs it with WBESC (or FUSD, BUSDC) to create a tradable pool on BescSwap. The DEX issues LP tokens that represent ownership of that pool — whoever holds the LP can withdraw the BESC and the matched supply of your token whenever they like.

If the team holds the LP and pulls it, the pool drains. Holders are left with tokens that can't be sold at any meaningful price. That's the textbook rug pull, and it's the single biggest reason new buyers refuse to touch a launch.

Locking LP means depositing those LP tokens into a time-locked vault contract. While they're locked, no one — not the team, not BescPad — can withdraw them. The lock is enforced by the contract, anyone can read its state from the explorer, and the unlock date is set in stone.

It's the single highest-trust signal you can ship that costs almost nothing. New holders look for it before they buy. If you don't lock, every honest project you compete with looks safer than yours by default.

Lock vs burn — pick the right one

There are two ways to make LP non-rugable:

Lock LP

LP tokens go into the locker vault. They're retrievable on the unlock date — not before, not after a vote, not via any back door. You set the duration.

Use when: you want the option to migrate liquidity later (to a new DEX, to a different pair, to a re-launch). You're treating the lock as a trust signal that's eventually returnable to you.

Burn LP

LP tokens are sent to 0x000…dead. Permanently destroyed. The pool can never be removed, by anyone, ever.

Use when: you want the strongest possible trust signal and you're committed to this pair forever. Common for long-term community projects and tokens that will never need a re-launch.

Most launches lock for 1–2 years and then renew (or eventually burn). Some long-term projects burn from day one. Either is acceptable. Anything shorter than 6 months reads as half-hearted to most buyers.

How much LP to lock and for how long

The honest answer: lock all of it, for at least a year. Anything less invites scrutiny you don't want during the first weeks of trading.

If you have a real reason to retain some LP — phased liquidity migration, a partner deal — lock at least 80% of it and have the remainder vested through a separate smart contract. Don't keep loose LP in a personal wallet "just in case." That's the wallet your holders will screenshot every time price dips.

Duration guideline:

• 3 months: the absolute minimum. Reads as "we'll be gone soon."
• 6 months: functional but unimpressive.
• 1 year: the standard for serious launches.
• 2 years+: reads as long-term commitment.
• Burn / 99 years: the strongest signal short of full burn.

How to lock LP on BescPad

Walk through:

1. Get LP tokens first. If you haven't added liquidity yet, do that on BescSwap (or via /tax-free-lp if your token is registered). Adding liquidity returns LP tokens to the wallet that did the add.
2. Open /locker. Connect the wallet holding the LP tokens.
3. Search by pair address. Paste either the LP pair contract address or the underlying token's address — the locker resolves both.
4. Specify amount + duration. Most teams pick "Lock max" and a date 1–2 years out. The form shows the exact unlock timestamp and the beneficiary wallet (whoever signs the lock transaction).
5. Approve, then lock. Two transactions: first one approves the locker contract to move your LP tokens, second creates the lock. Total gas: ~0.5 BESC.
6. Save the vault page URL. The locker shows a confirmation with a permalink to your vault. Anyone with that link — or just the token address — can verify the lock independently on the explorer.

How a buyer verifies your lock

This is what holders will do when they look at your token. Spend two minutes doing it yourself for your own token, in incognito mode, before you announce the launch:

1. Go to /locker and search by the token address.
2. Confirm a lock entry appears with: amount, unlock date, beneficiary wallet.
3. Click through to the on-chain vault contract on the explorer. Verify the lock parameters there too (the locker UI just displays what the contract says).
4. Compare the locked LP amount to the total LP supply — ideally ~100%. If only a fraction is locked, that's a yellow flag (ask the team why).
5. Confirm the beneficiary is either the team's multi-sig or burned (0x000…dead). A single EOA beneficiary means one wallet can withdraw when the lock expires — not malicious, just worth knowing.

If your token doesn't pass this two-minute check, fix it before announcing — not after holders start asking.

Common mistakes that destroy trust

• Locking the wrong LP token. If you added liquidity through tools that route through wrapper contracts, you may end up with LP for a different pair than you think. Always double-check the pair address by reading token0() and token1() on the explorer.
• Locking only the team's portion, leaving public LP unlocked. If the team locks 10% and the other 90% sits in a hot wallet, that 90% can rug. Lock everything you control.
• Three-month locks "to start." By month two, your holders are watching the calendar. Either lock long from day one or commit to extend before the deadline becomes visible.
• Single-EOA beneficiary with poor opsec. The lock contract enforces the unlock date, but on the unlock date the beneficiary can withdraw. If that wallet's seed leaks, your future LP is gone. Use a multi-sig if the value justifies it.
• "Locked" claims with no on-chain entry. Some teams claim locked LP but it doesn't appear in any public locker. There's no such thing as an off-chain lock for an on-chain asset. If it's not in the locker contract, it's not locked.
• Burning LP before pool is fully seeded. Once burned, you cannot add more LP from a privileged contract (you can still add as a regular user). If you plan to grow liquidity over time, lock; don't burn.

Renewing, extending, and what happens at unlock

Extending a lock is easy and you should plan to do it well before the original expiry. Most projects extend at the 6-month mark of a 12-month lock so the visible countdown never drops below 6 months.

To extend: open the existing vault, sign a transaction that pushes the unlock date forward. Same gas cost as the initial lock, no need to re-deposit.

If the unlock date arrives without extension, the beneficiary wallet can withdraw the LP. The withdrawal is on-chain and immediately visible to anyone watching the contract. If you genuinely intend to retire the project gracefully, communicate the unlock plan publicly weeks in advance and let holders make informed decisions.

FAQ

What's the difference between locking and burning LP?

Locking puts the LP tokens in a vault that releases them on a date you set. Burning sends them to a dead address permanently. Lock is reversible (on unlock date); burn is forever.

How do I know a project's LP is really locked?

Open /locker, search the token address. A real lock shows the amount, beneficiary, and unlock date with an on-chain vault link. If a project claims locked LP but nothing appears there, the claim is false.

Can BescPad release my locked LP early?

No. The lock contract enforces the unlock date on-chain. Even BescPad cannot withdraw before the date you set.

What if I forget to extend before the unlock date?

The LP becomes withdrawable to the beneficiary. The withdrawal is on-chain and visible. If you want to avoid this, set a calendar reminder for ~60 days before unlock and extend then.

Should I lock LP I added through /tax-free-lp?

Yes — lock it the same way as any other LP. The tax-free-LP helper exempts the LP add from your token's tax; the resulting LP tokens behave like any other LP and need to be locked or burned independently.

Can I lock LP for someone else?

The wallet that signs the lock transaction becomes the beneficiary by default. Some locker variants let you specify a different beneficiary address. Be careful — the beneficiary is the only wallet that can withdraw on unlock.

How much LP should I lock?

All of it. Anything less invites questions you don't want to answer during your launch's first month. If you must retain some LP for an operational reason, lock at least 80% and explain the remainder publicly.