Skip to main content

Vaulting and Vesting

Lock a portion of your token supply with time-based release schedules.

What is Vaulting?

Vaulting locks a percentage of your token supply. This:

  • Signals long-term commitment to holders
  • Prevents immediate dumps
  • Builds trust with your community

What is Vesting?

Vesting releases locked tokens gradually over time. You can configure:

  • Cliff period — Time before any tokens unlock
  • Vesting duration — Time over which tokens gradually release

Base Token Vaulting

On Base, you can vault 0-90% of the token supply:

"deploy a token called MyAgent with 30% vaulted on base"
"deploy TeamToken with 20% vault, 7 day lockup, vesting over 30 days on base"

Configuration Options

ParameterDescriptionDefault
Vault percentage0-90% of supply0% (no vault)
Lockup/cliffMinimum 7 days7 days
Vesting durationDays to fully vest0 (immediate after cliff)
Vault recipientWho receives vested tokensDeployer

Example Configurations

Simple lockup (no vesting):

"deploy a token with 25% vaulted for 14 days on base"

After 14 days, all vaulted tokens unlock at once.

Lockup with vesting:

"deploy a token with 30% vault, 7 day cliff, 60 day vesting on base"

After 7 days, tokens begin unlocking linearly over 60 days.

Solana Token Vesting

On Solana, vesting uses the Raydium LaunchLab mechanism:

ParameterDescription
totalLockedAmountNumber of tokens to lock (in token units with decimals)
cliffPeriodSeconds before vesting starts (e.g., 30 days = 2,592,000 seconds)
unlockPeriodSeconds over which tokens vest linearly
"launch a token on solana with 50% locked, 30 day cliff, 90 day vesting"
note

Solana vesting parameters are specified in seconds, not days. Bankr handles the conversion when you use natural language like "30 day cliff".

Important Notes

  • Vault recipient is immutable — On Base, you cannot change who receives vested tokens after deployment
  • Minimum lockup — Base requires at least 7 days
  • No vault by default — If you don't specify, no tokens are locked