AseLock

Token lock & vesting

AseLock escrows LP shares and tokens inside the contract itself. Lock pool liquidity to a date, vault team tokens, or set a linear vesting schedule that beneficiaries claim against whenever they want. Every lock is public and gets its own page.

What AseLock is

AseLock is the platform's locker contract, and the Token Lock page is its frontend. Locked assets live inside the contract's own storage, not in a wallet or on a server, so nobody can touch them early, not the site, not the locker owner, and not us. The contract decides when things move.

Every lock gets a number and its own public page at /lock/<number>, with the token, amount, dates and current state laid out. A lock can only ever be in one of three states: LOCKED, RELEASED or BURNED.

The four lock types

LP lock

• Pick a pool you provide liquidity to, the amount of shares, and an unlock date. The shares move from your wallet into the lock contract, while the liquidity itself stays in the pool.
• Two signatures: the first approves the lock contract to move your pool shares, the second creates the lock.
• The unlock date must be in the future, and the contract enforces it. Even you cannot withdraw before it passes.
• After the date, tap Unlock on the lock page and the same shares come back to your wallet.

Token lock

• Escrow any ARC-20 token until a date you choose. Team allocations, treasury reserves, airdrop supplies, whatever needs a visible commitment.
• Same flow as LP: approve the token spend first, then create the lock.
• The contract measures what actually arrived, not what you typed. A token that taxes the transfer and under-delivers fails the lock instead of quietly locking less.

Vesting

Vesting is a token lock that pays out gradually instead of all at once. The amount releases on a straight line between a start and end date: nothing before the start, everything by the end, and a proportional slice in between.

• Single beneficiary. Lock an amount for yourself or a wallet you control, then claim whatever has vested at any time.
• Multi beneficiary. One lock covers a whole team: one address,amount per line, up to 64 people, each with their own allocation on the same schedule.
• Claim whenever. Claims can happen as often as you like, even daily. Each claim pays the vested amount minus what was already paid, so nothing is lost by claiming early and often.
• Tax tokens stay fair. If a token's transfer fee eats part of a claim, the contract records only what actually arrived. The missing remainder stays claimable, so the schedule still pays the full allocation in the end.
• Beneficiary handoff. On a multi vesting lock, each beneficiary can move their own slot, every unpaid and future payout, to a different wallet without affecting anyone else.

Unlock vs burn

Once an LP or token lock exists it has exactly two exits, both permanent and both owner only:

• Unlock returns the assets to the owner. Only possible after the unlock date passes.
• Burn sends the locked shares or tokens to the zero address at any time, even before the date. A burned lock stays on the list marked BURNED as a public proof that those assets can never move again.

Burning an LP lock is how you prove liquidity is gone for good. It is different from the automatic migration burn on AsePad launches, which happens inside the pad contract at graduation; a manual lock and burn is the way to make the same commitment on any pool, any time.

Vesting locks have no unlock and no burn. They only move through claims, so a vesting schedule can never be cut short by anyone.

Managing a lock

• Transfer. The whole ownership of an LP or token lock can move to another wallet. The date and amount do not change, the new owner simply steps into your place. This cannot be undone.
• My locks. The Token Lock page lists every lock your wallet owns plus every vesting slot where you are a beneficiary, and any token or pool page links straight to the locks that touch it.

Verifying on chain

Locks are public state. The lock page reads the record straight from the AseLock contract, and the contract address itself is listed on the contracts page. Because burn sends assets to the zero address on chain, a BURNED lock can be checked on the explorer like any other transaction, no trust in this site required.