Solana Token Vesting
Release tokens gradually to team members, investors and advisors. Tokens are held in Program Derived Addresses with no private keys and unlock continuously across your schedule.
Set a cliff, choose a duration, and only the beneficiary can claim. SPL and Token-2022 supported.
Vesting Explorer
Vest SPL tokens and Token-2022 tokens on Solana with cliffs and linear release. Every schedule is publicly verifiable on-chain.
Total Schedules
2
Active
1
Permanent
2
My Schedules
0
How Does Solana Token Vesting Work?
To vest tokens on Solana, connect your wallet on StakePoint, select the SPL or Token-2022 token you want to vest, enter the beneficiary wallet, set a cliff and total duration, and confirm. Your tokens are immediately transferred into a Program Derived Address on-chain.
Tokens unlock continuously across the vesting period. The beneficiary can claim whatever has vested at any point, and the remainder keeps unlocking until the schedule completes. Every claim is recorded permanently on Solana.
Only the beneficiary wallet can claim. Nobody else, including StakePoint, can redirect or withdraw vesting tokens. Schedules created as permanent cannot be cancelled by anyone.
What Can I Vest on Solana?
StakePoint supports vesting any SPL token or Token-2022 token on Solana, including tokens with transfer taxes, reflection mechanics, and custom extensions. This covers tokens from every major Solana launchpad.
Vesting suits team allocations, seed and private round investor tokens, advisor grants, and marketing reserves. Each recipient gets their own schedule, and a single creator can run as many schedules as their tokenomics require.
If you want a single unlock date rather than gradual release, use the token locker instead. See our comparison of vesting versus locking to decide which fits your project.
How Vesting Is Secured
StakePoint's vesting is a non-custodial Anchor smart contract deployed on Solana mainnet. When a schedule is created, tokens are transferred into a Program Derived Address, an on-chain account with no private key. Only the beneficiary wallet can claim, and only what has actually vested.
The upgrade authority for the StakePoint smart contract is controlled by a 3-of-4 Squads multisig with hardware wallet signers. No single party can modify the program unilaterally. All vesting schedules are permanently recorded on Solana's blockchain.
Verify program on SolscanToken Vesting FAQ
Everything you need to know about vesting tokens on Solana
How do I create a vesting schedule on Solana?
Connect your Solana wallet on StakePoint, select the SPL or Token-2022 token you want to vest, enter the beneficiary wallet address, set a cliff and total duration, and confirm. Your tokens are immediately transferred into a Program Derived Address on-chain and unlock continuously across the schedule.
What is the difference between vesting and locking?
Locking holds tokens until a single unlock date, then releases everything at once. Vesting releases tokens gradually over time, optionally after a cliff. Vesting suits team and investor allocations, locking suits liquidity and supply commitments.
Who can claim the vested tokens?
Only the beneficiary wallet set at creation. The smart contract enforces this on-chain. Neither the creator nor StakePoint can redirect tokens to a different wallet once the schedule exists.
Can a vesting schedule be cancelled?
Only if the creator enabled cancellation at creation. Schedules created as permanent cannot be cancelled by anyone, including StakePoint. Every schedule publicly shows whether it is permanent or cancellable, so investors can verify before trusting it.
What is a cliff?
A cliff is a waiting period at the start during which nothing can be claimed. Once it passes, everything vested up to that point becomes claimable at once, and the rest continues unlocking gradually until the schedule completes.
Is there a limit on vesting duration?
No. Schedules can run from an hour to several years, with an optional cliff of any length up to the total duration. A creator can also run as many separate schedules as their tokenomics require, one per beneficiary per token.