> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jup.ag/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> These docs cover what users see and do on jup.ag, Jupiter Mobile and Jupiter Wallet.
> Universal Deposit, the GUM route in Jupiter Bridge and other GUM integrations on jup.ag are built by GUM. For how they work, their full fee rules, security model and APIs, the reference is the GUM docs: start from https://docs.gum.ag/llms.txt.
> When the GUM docs and these docs differ on how a GUM product behaves on jup.ag, describe the jup.ag experience from these docs and the mechanics and fees from the GUM docs.

# Jupiter Lock FAQ

> Frequently asked questions about Jupiter Lock: creating locks, vesting schedules, claiming tokens, and security.

## General

> [accordion] What is Jupiter Lock?
>
> Jupiter Lock is a free token locking and vesting tool on Solana. It allows anyone to create onchain escrows that hold tokens and release them according to a defined vesting schedule.

> [accordion] Who can create a lock?
>
> Anyone with a Solana wallet. There are no restrictions on who can create a lock. Multisig wallets are also supported.

> [accordion] Are there any fees?
>
> No. Jupiter Lock has no protocol fees. You only pay standard Solana network fees for transactions (creating a lock, claiming tokens, etc.). Jupiter Lock is a public good.

> [accordion] Is Jupiter Lock audited?
>
> Yes. The program has been audited by OtterSec and Sec3. Read the [OtterSec](https://github.com/jup-ag/docs/blob/main/static/files/audits/lock-ottersec.pdf) and [Sec3](https://github.com/jup-ag/docs/blob/main/static/files/audits/lock-sec3.pdf) reports.

## Creating a Lock

> [accordion] What tokens can I lock?
>
> SPL and Token-2022 tokens on Solana, verified or not. For a Token-2022 token, the form warns that some extensions may be incompatible with the Jupiter Lock program: check them before you lock. See [Token Compatibility](https://docs.jup.ag/user-docs/launch/lock/how-it-works.md#token-compatibility).

> [accordion] Can I create a simple lock with no gradual vesting?
>
> Yes. Set the cliff unlock amount to the full token amount. Since nothing remains to vest after the cliff, all tokens become claimable at the cliff date. The vesting duration and frequency have no effect in this case.

> [accordion] Can I create one lock for multiple recipients?
>
> No. Each lock has exactly one recipient wallet. To distribute tokens to multiple wallets, create a separate lock for each recipient: **Add another lock** adds them to the same form, and each one is created in its own transaction.

> [accordion] Is there a minimum or maximum lock duration?
>
> No. There are no limits on lock duration or token amount. The cliff date cannot be in the past, and the vesting duration must be a whole multiple of the unlock frequency. See [Lock Parameters](https://docs.jup.ag/user-docs/launch/lock/how-it-works.md#lock-parameters).

> [accordion] Can I modify a lock after creation?
>
> No. Vesting parameters (cliff date, vesting duration, token amount, frequency) are permanent once the lock is created. The only actions possible after creation are changing the recipient wallet or cancelling the lock, and only if the corresponding permissions were set at creation. Both are done from **Edit** on the lock. Cancelling returns unvested tokens to the creator and sends tokens already vested but not yet claimed to the current recipient. See [Permissions](https://docs.jup.ag/user-docs/launch/lock/how-it-works.md#permissions).

> [accordion] What are permissions in Jupiter Lock?
>
> When creating a lock, the creator defines two permissions:
>
> * "Who can change the recipient?" sets who can reassign the lock to a different wallet.
> * "Who can cancel the contract?" sets who can cancel the lock entirely.
>
> Each one is set to None, Only Creator, Only Recipient, or Creator or Recipient (either of them), and defaults to None. These permissions are set once and cannot be modified. If both are set to None, the lock is fully irreversible. See [Permissions](https://docs.jup.ag/user-docs/launch/lock/how-it-works.md#permissions).

## Claiming Tokens

> [accordion] How do I claim my tokens?
>
> Connect your recipient wallet to the [Jupiter Lock interface](https://lock.jup.ag/). The UI shows how many tokens have vested and are available to claim. You trigger a claim transaction to transfer them to your wallet.

> [accordion] Are unlocked tokens sent automatically?
>
> No. The recipient must manually claim unlocked tokens through the Jupiter Lock interface.

> [accordion] Do unclaimed tokens expire?
>
> No. Unclaimed tokens remain in the escrow indefinitely. You can claim them at any time after they have vested.

## Security and Risks

> [accordion] What happens if my wallet is compromised?
>
> There is no built-in recovery mechanism. If the recipient wallet is compromised, the only option is if the lock was created with permissions allowing the creator to change the recipient or cancel the lock. If those permissions were not set, the tokens are only claimable by the compromised wallet.

> [accordion] What happens if the locked token loses value or liquidity?
>
> Jupiter Lock only manages the escrow and vesting schedule. It does not monitor or react to changes in the token itself. If the token loses value or liquidity, the lock still functions as configured, but the tokens may have no practical value when claimed.

> [accordion] Is the Lock program immutable?
>
> No. The program is upgradeable, but updates are only made when critical. The program has been audited by OtterSec and Sec3.

## Relationship to Other Jupiter Products

> [accordion] Is Jupiter Lock a standalone tool?
>
> Yes. Jupiter Lock has no technical dependency on other Jupiter products. It can be used independently by anyone.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.