Testnet · chain 6
Open app
  1. Docs
  2. Products
  3. Liquidity locks

Products

Liquidity locks

Lock an exact typed Dexlyn V1 LP Coin with explicit costs and third-party boundaries.

Revision 64 min read
On this page
  1. When to use it
  2. Before you start
  3. Create an LP lock
  4. Practical example
  5. Fees and costs
  6. Claim
  7. What Trust Stack does and does not guarantee
  8. Common problems

The Dexlyn V1 adapter locks a legacy typed LP Coin in an isolated vault until an immutable UTC time. It is separate from the core standard-asset package because DEX packages, pool provenance, legacy Coin behavior, and upgrade authority have their own risk boundary.

Dexlyn LP lock form showing pool types, LP amount, beneficiary, and unlock time
Fig. 01Dexlyn LP lock form showing pool types, LP amount, beneficiary, and unlock timeFull size

When to use it#

Use this product when the creator already holds Dexlyn V1 LP Coins and wants to demonstrate that an exact quantity cannot be withdrawn through the lock until a public maturity time.

The lock does not add liquidity, remove liquidity, swap assets, migrate a pool, verify project economics, or guarantee the value of the LP position.

Before you start#

You need:

  • the exact two underlying coin type strings;
  • the pool curve (Uncorrelated or Stable) and token ordering used by the intended Dexlyn pool;
  • sufficient balance of that typed LP Coin;
  • the final beneficiary and future UTC unlock time; and
  • SUPRA for network gas.

Confirm pool provenance independently. A type string that compiles is not proof that the pool is official, liquid, safe, or economically valuable.

Create an LP lock#

  1. Open Liquidity locks (Create > Liquidity lock in the dApp sidebar) and connect StarKey. Read the External Dexlyn upgrade authority notice.
  2. Pick one of Your LP positions, read from the connected wallet, or enter Token X Move type, Token Y Move type, and Pool curve (Uncorrelated or Stable) yourself. Use Swap token X and token Y if the ordering is reversed.
  3. Let the dApp derive the LP coin type and verify the pool against the pinned Dexlyn V1 testnet router.
  4. Enter the Beneficiary address and LP amount (or Use maximum LP balance), and set Unlock date and time (UTC) with the UTC date-time picker. The unlock time must be at least two minutes ahead.
  5. Select Review LP lock and check the LP amount and base units, pair, curve, Dexlyn pool, LP coin type, lock adapter, beneficiary, and unlock time.
  6. Select Lock derived LP tokens and sign the lock transaction.
  7. Wait for the matching creation event and save the vault, pool, adapter deployment, and transaction hash.

The adapter constructs a fixed generic function target from the reviewed types. It does not accept an arbitrary router or function target.

Practical example#

A project owns 500 LP Coins for a Dexlyn TOKEN_A/TOKEN_B pool and locks all of them for its community treasury until 1 January 2028.

  • The project supplies the exact typed LP balance and pays creation gas.
  • Trust Stack collects no protocol fee.
  • The LP Coins remain in the lock vault until maturity.
  • At maturity, the treasury beneficiary pays claim gas and receives the same typed LP Coins.
  • Removing liquidity afterward is a separate Dexlyn operation with separate DEX behavior and costs.

Fees and costs#

ActionTrust Stack protocol feeWho paysOther cost
Create LP lockNoneNobodyCreator supplies LP Coins and pays Supra network gas
Claim matured LP CoinsNoneBeneficiarySupra network gas
Verify an LP lockNoneNobodyNone
Add/remove liquidity or swapNot a Trust Stack actionDexlyn userDexlyn fees, price impact, slippage, and gas may apply

Trust Stack does not take a percentage of the LP position. External Dexlyn fees or economic losses are outside the lock and should not be described as Trust Stack protocol fees. See Fee governance.

Claim#

Dexlyn LP claim workspace for reading lock terms and releasing matured LP tokens
Fig. 02Dexlyn LP claim workspace for reading lock terms and releasing matured LP tokensFull size
  1. Open Manage liquidity lock (Manage & claim > Liquidity claims in the dApp sidebar).
  2. Select the LP lock adapter deployment that created the vault, then enter Token X Move type, Token Y Move type, Pool curve, and the LP lock vault address.
  3. Verify the LP amount, pool, adapter deployment, beneficiary, unlock time, and vault balance read directly from Supra.
  4. Connect the beneficiary wallet after maturity.
  5. Select Claim LP tokens, sign in StarKey, and wait for the matching event.
  6. Confirm terminal state, zero vault balance, and receipt of the typed LP Coin.

What Trust Stack does and does not guarantee#

Trust Stack checks the immutable lock terms, exact generic LP type, beneficiary authorization, maturity, claim state, and vault conservation. It does not audit the Dexlyn pool's reserves, underlying token issuers, price, impermanent loss, router, governance, or future upgrades.

Common problems#

  • Type mismatch: coin ordering and curve type must exactly match the LP Coin held by the wallet.
  • No LP balance: adding liquidity is a separate prerequisite outside Trust Stack.
  • Claim fails after maturity: verify the beneficiary, complete type parameters, and claimed state.
  • Pool is unsafe or inactive: a valid lock does not certify the pool.
  • LP value changed: the lock preserves LP units, not their market value or redemption output.