Vesting Model
Every lock created on Jupiter Lock follows a cliff + linear vesting model. The vesting schedule is defined at creation and cannot be changed afterward.- Cliff + Linear Vesting
- Simple Lock (Full Release at One Date)
This is the standard configuration. The vesting schedule has two phases:
- Cliff phase. No tokens are available until the cliff date. On that date, a predefined amount (the cliff unlock amount) becomes claimable immediately.
- Linear vesting phase. After the cliff, the remaining tokens unlock gradually over the defined vesting duration, at the unlock frequency you set (every given number of minutes, days, weeks, months, or years).
There is no minimum or maximum for lock duration or token amount. The vesting duration must be a whole multiple of the unlock frequency: 12 months with a monthly frequency works, but 1 year with a weekly frequency does not.
Lock Parameters
When creating a lock on lock.jup.ag, you select the token, then fill in the following fields (names as shown in the form). Every parameter is permanent once the lock is created; afterward, the recipient can only be changed, or the lock cancelled, if the permissions allow it.
Each lock has exactly one recipient. To distribute tokens to multiple wallets, select Add another lock in the form to add one lock per recipient. You review them together, and each lock is created in its own transaction, approved in your wallet.
Permissions
At creation, the lock creator assigns two permissions: Who can change the recipient? This determines which party can reassign the lock to a different wallet after creation: None, Only Creator, Only Recipient, or Creator or Recipient (either of them). Who can cancel the contract? This determines which party can cancel the lock entirely, with the same four options. These permissions are set once and cannot be changed after the lock is created. Both default to None in the form.If both permissions are set to None, the lock becomes fully irreversible: it cannot be cancelled and the recipient cannot be changed.
- Update recipient moves the lock to a new recipient address, with the same vesting terms.
- Cancel lock ends the lock: unvested tokens return to the creator’s address, and tokens already vested but not yet claimed are sent to the current recipient’s address. Cancellation is irreversible.
Claiming Tokens
Unlocked tokens are not sent automatically. The recipient must manually claim them through the Jupiter Lock interface.1
Connect wallet
The recipient connects the wallet specified in the lock.
2
View available tokens
The interface shows how many tokens have vested and are available to claim.
3
Claim
The recipient triggers a claim transaction. Claimed tokens are transferred from the escrow to the recipient’s wallet.
Token Compatibility
Jupiter Lock supports SPL and Token-2022 tokens on Solana, whether or not Jupiter has verified them. When you select a token, the form flags what can affect the lock:- A Token-2022 token shows a warning that transfer hooks or other extensions may be incompatible with the Jupiter Lock program. Check the token’s extensions before you lock it.
- Token Authority: the token has a freeze authority, which can freeze your token account so that you cannot lock or claim, or a permanent delegate, which can burn or move the locked tokens.
- Transfer Tax: the token charges a transfer fee, shown as a percentage.
- A token that Jupiter has not verified is marked as not verified.
Onchain Mechanics
When a lock is created, an escrow account is deployed onchain. The locked tokens are transferred from the creator’s wallet to this escrow account. The escrow is controlled by the Jupiter Lock program. Tokens remain in the escrow until claimed by the recipient according to the vesting schedule.The Jupiter Lock program is upgradeable. Due to the sensitive nature of the program, updates are only made when critical. The program has been audited by OtterSec and Sec3.

