Token locks

A fixed token lock moves one exact Fungible Asset allocation into its own untransferable vault. The beneficiary is chosen at creation and may claim the complete allocation only at or after the immutable UTC unlock time.

When to use it

Use a fixed lock for a one-time release date, such as:

• a team allocation that becomes available on a specific date;
• a treasury or community allocation with a public maturity time;
• a token commitment where partial claims are not required; or
• a simple beneficiary lock without creator cancellation.

For gradual release, use vesting. For continuous payroll accrual, use payment streams.

Before you start

The creator needs:

• the token's Fungible Asset metadata address;
• enough token balance to fund the entire lock;
• the final beneficiary address and future UTC unlock time; and
• 50 SUPRA plus network gas.

Verify the token's symbol, decimals, issuer capabilities, and metadata address. Names and symbols are not unique identifiers.

Create a lock

1. Open Create token lock.
2. Enter the Fungible Asset metadata address and select Token details.
3. Confirm the token identity, decimals, admission status, and your live balance.
4. Enter the amount, beneficiary, and UTC unlock time.
5. Review the display amount, exact base units, beneficiary, network, immutable terms, and live fee.
6. Sign the transaction in StarKey.
7. Wait for the matching LockCreated event and save the lock object address, transaction hash, and public-proof link.

Funding and lock creation are atomic. A successful transaction withdraws the tokens and deposits them into the new lock vault; it cannot create an unfunded position.

Practical example

Acme locks 100,000 EXR for a contributor until 1 January 2028.

• Acme supplies the full 100,000 EXR when the lock is created.
• Acme pays the current 50 SUPRA protocol fee plus creation gas.
• Before 1 January 2028, neither Acme nor the contributor can withdraw the allocation.
• At maturity, the contributor signs one claim and receives all 100,000 EXR.
• The contributor pays claim gas, but Trust Stack charges no claim fee.

The creator cannot shorten, extend, split, revoke, transfer, or change the beneficiary after creation.

Fees and costs

The 50 SUPRA fee is separate from the locked asset; it does not reduce the beneficiary's token allocation. It is charged only when creation succeeds. An abort rolls back both the vault and protocol fee transfer, although failed transactions may still consume network gas.

The signed transaction includes a maximum acceptable fee. The current schedule is 50 SUPRA under the immutable 10,000 SUPRA cap. Governance may move it within that cap, and an approved governor-multisig change applies when executed. See Fee governance.

Claim a lock

1. Connect the beneficiary wallet on Supra Testnet.
2. Open My positions or the lock's direct claim link.
3. Verify the lock object address, creator, token, amount, beneficiary, and unlock time.
4. Wait until the on-chain timestamp reaches the unlock time.
5. Sign Claim and wait for the matching LockClaimed event.
6. Confirm the position is terminal, the vault is empty, and the beneficiary balance increased by the exact locked amount.

The dApp disables claiming for the wrong wallet, before maturity, or after the one-time claim has already completed.

What is guaranteed

• Creation and full funding succeed or fail together.
• Only the immutable beneficiary can claim.
• The creator has no early-withdrawal path.
• Every position has an isolated object and vault; user funds are not pooled.
• The claim is one-time and should leave the expected vault balance at zero.
• Accidental surplus cannot be redirected to the creator or an arbitrary caller.

Common problems

• Wrong token displayed: stop and compare the full metadata address.
• Insufficient balance: the creator needs the locked tokens, 50 SUPRA, and gas.
• Claim button disabled: confirm the connected wallet and the on-chain unlock timestamp.
• Position missing: use the saved object address directly; indexer discovery may lag the chain.
• Token has issuer controls: a vault cannot remove mint, freeze, or dispatch capabilities retained by the asset issuer.