Docs

vautl is one Solana program. It handles token vaults with vesting schedules, and bounties that pay wallets for locking a specific token. Every button on this site builds a transaction against that program. The site holds no keys and never takes custody.

Program ID: 56prTEtY19u1EHvMRnwQh674KTiNj6dnKvTXyVCXbfo7

A vault is two accounts. The vault account stores the owner, mint, amount, withdrawn amount, and schedule. The tokens sit in a token account whose authority is a program-derived address with no SOL and no data, so on-chain it reads as an ordinary wallet. That is what lets reward distributors pay it.

Deposits are measured by what lands in the token account, not what you typed in. Tokens with a transfer tax have the tax netted out, so the locked amount matches its real balance.

Withdrawing, extending, topping up, and closing all require the owner’s signature. There is no admin instruction that can move user funds.

A schedule is three timestamps: start, cliff, end. Nothing vests before the cliff. Between cliff and end the vault vests linearly. After end, it’s all unlocked. An all-at-once vault just sets cliff equal to end: 0% until the date, 100% at it. Linear vaults can also unlock in chunks (daily, weekly, monthly): claimable amounts then grow once per period instead of every second.

Top up adds tokens under the existing schedule. Extend pushes the cliff and end forward. Dates only move forward, so a vault can’t be shortened once it exists. When you extend, whatever has already vested is frozen in as a floor, so extending never pulls back tokens you could already claim.

Fully withdrawn and empty vaults can be closed to get the rent back.

The vault can hold tokens other than the locked one. Claiming rewards sweeps those balances to the vault owner. Anyone can trigger the sweep, but it can only pay the owner.

Whether a distributor pays a vault is up to the distributor. StonkFun’s distributor skips program vaults today, so locked StonkFun reward coins are not earning. We’re talking to their team about fixing that. Until then the site is in early access; locking itself works fine.

A bounty pays a reward to whoever vaults a chosen token on a chosen schedule. The reward goes into escrow when the bounty is posted, so every live bounty is funded.

If the minimum fill equals the required amount, one claimer vaults everything and takes the whole reward. Set the minimum lower and it’s a community bounty: wallets vault partial amounts and get paid pro rata at the posted rate.

Claims are atomic. The vault and the payout happen in the same transaction, so two people can’t claim the same funds. The poster can cancel whenever and gets back whatever hasn’t been claimed. Expired bounties stop accepting claims.

Claiming creates a new vault in your wallet: about 0.0024 SOL of rent, refundable when the vault is closed.

A vault can be created for someone else. The creator pays the fee and funds the deposit, but the owner recorded on-chain is the recipient’s wallet. The recipient never has to sign anything; the vault is theirs from the moment the transaction lands.

Gifting is irrevocable. Only the recipient can ever withdraw, extend, top up, or close a gifted vault. There is no revoke instruction and no admin path back, so double check the address before sending.

A lockathon vault is always all-at-once: one unlock date, nothing vested before it, everything at it. What makes it a lockathon is a set of extension terms created with the vault: a reward token, a price, a duration, and a multiplier. The terms are written into the vault account at creation and can never be changed.

While the vault is live, anyone can extend it by paying the current price. The payment goes to the vault owner minus the protocol fee, and the single unlock date moves forward by the duration. After each extension the price is multiplied by the multiplier, so a 1.1x multiplier makes every extension 10% more expensive than the last, while 1.0x keeps the price flat. Extensions close once the vault reaches its unlock date.

Extending never re-locks tokens that have already vested. The vested amount is frozen as a floor before the schedule moves, the same guarantee a manual extend gives.

Setting terms is free. The fee on each extension is read from a config account with a hard 2% ceiling enforced by the program; the admin can adjust it but never above that. If the reward token is wrapped SOL, extensions are priced and paid in native SOL.

We never skim withdrawals or reward claims. Fees go to a protocol wallet hardcoded in the program; changing it takes a program upgrade.

No admin keys over user funds. Changing a vault takes the owner’s signature, and payout destinations come from the vault itself rather than from whoever sends the transaction.

The site is a viewer plus a transaction builder. If it went offline tomorrow, your vaults would sit exactly where they are and you could still withdraw by sending the same instructions from any Solana client.

Your tokens live in vault accounts on Solana, not on our servers. No database to lose, no company that needs to keep operating for your vault to keep working. As long as Solana exists, your vault does too, on the schedule you set.

The program is permissionless. It checks the owner’s signature, never the front end a transaction came from. This site is one way to use it, not the way. Any Solana client can read your vault, build the same withdraw instruction, and get the same result, because the vesting math runs on-chain.

Practical habit: bookmark the share link for any vault you care about. It gives you the vault address up front, and everything else can always be rebuilt from the chain.

Each instruction emits an event. The activity feeds on vault, token, and wallet pages are built from these, and anyone can reconstruct the same history from the chain.

Vault pages decode these into a readable history: deposits, withdrawals, extensions, top ups, reward sweeps. See yours under vaults.