Locking From a Squads Vault, in One Paragraph
If your project treasury sits in a Squads multisig, you can now lock tokens from it without moving them to a hot wallet first. On StakePoint, a member of the Squad builds the lock as a Squads proposal, the other signers approve it in the Squads app, and when it executes the tokens move from the vault into the lock. The vault is the owner of the lock, so unlocking later is also a Squad decision. No browser extension, no intermediate wallet, and nothing moves until your signers say so.
Key Takeaways
- Tokens lock directly from the multisig vault. The vault signs by executing a proposal, the same way it signs anything else.
- The lock belongs to the vault, not to the member who created the proposal. Only the Squad can unlock it.
- Works for standard token locks, LP locks, reward token locks and vesting schedules.
- You need the multisig account address, not the vault address, and a connected wallet that is a member of the Squad.
- The vault needs about 0.025 SOL for the platform fee and account rent, the same as any wallet creating a lock.
Lock From Your Squads Vault
Non-custodial · Squads proposal flow · Independently audited
Why This Was Worth Building
The usual workaround for a multisig treasury was to vote a transfer out to a single wallet, lock from that wallet, and vote again to clean up afterwards. That means two governance rounds, a window where tokens sit on a hot key, and a lock owned by whoever held that key. For a DAO or a funded project the whole point of the multisig is that no single person holds the treasury, and the workaround quietly broke that.
A proposal flow fixes it. The multisig stays the owner at every step: it holds the tokens before the lock, it signs the deposit, and it is the only party that can withdraw at the unlock date. The lock page shows the vault address as the creator, which is what investors want to see from a treasury anyway.
How the Squads Proposal Flow Works
Squads v4 lets a vault execute arbitrary instructions once a proposal reaches the approval threshold. StakePoint uses that to run its normal lock instructions with the vault as the signer instead of a wallet.
A lock on StakePoint is two steps on chain: create the lock pool, then initialise it and deposit the tokens. Both are packaged into one Squads batch under one proposal, so your signers approve once and the steps execute in order. The deposit cannot run before the pool exists, and nothing can be inserted between them.
The member who starts the flow signs a couple of small transactions to create the proposal accounts. Those do not touch the treasury. They only write the proposal into Squads, and the rent they pay is returned when the proposal accounts are closed afterwards.
Step by Step
Open the token locker, or the reward locker if the token pays distributions to holders and you want the locked position to keep receiving them.
Connect a wallet that is a member of the Squad and click Create Lock.
Choose "Lock from a Squads vault".
Paste the multisig account address and click Load vault. This is the address shown on your Squad's Settings page in the Squads app. It is not the vault address, and the page will tell you if you paste the wrong one.
The vault's tokens are listed. Pick the token, the amount and the lock duration, then click Create Squads Proposal and sign the transactions in your wallet. This creates the proposal. No tokens move.
In the Squads app, collect the remaining approvals and execute the proposal.
Back on StakePoint, press Check now. Once the lock is confirmed on chain, the lock page is created and the lock address is shown for sharing or whitelisting.
The page keeps checking for ten minutes after you submit, and remembers the pending proposal in your browser if you close it, so a Squad that approves the next day loses nothing. Reopen the locker and it offers to check again.
What Each Person Needs
The member creating the proposal needs their wallet connected, membership of the Squad with permission to create proposals, and a small amount of SOL for the proposal accounts, around 0.03 SOL. Most of that is rent that comes back.
The vault needs the tokens being locked and about 0.025 SOL to cover StakePoint's platform fee and the rent for the lock accounts. These come out of the vault when the proposal executes, exactly as they would from a wallet.
The other signers need nothing beyond their usual Squads access. They see a proposal with a StakePoint memo describing the lock and approve it as normal.
Unlocking and Claiming Later
Because the vault owns the lock, the unlock is a proposal too. On the lock page, a Squad member loads the multisig, the page confirms the vault matches the lock's creator, and one click builds the withdraw proposal. The Squad approves and executes it, and the tokens return to the vault.
Reward locks work the same way. The locked position keeps receiving the token's holder distributions while locked, and claiming them to the vault is a proposal that any member can build from the lock page.
Vesting schedules created from a vault can be cancelled by proposal where the schedule was made revocable. The beneficiary claims their vested tokens with their own wallet as usual.
What This Is Not
It is not a change to the lock itself. A Squads lock sits in the same Program Derived Address vault as every other lock on StakePoint, enforced by the same audited program, with no admin keys and no early unlock. The only difference is who signed the deposit.
It is also not a separate product with its own trust assumptions. StakePoint never holds the proposal, never signs on behalf of the vault, and cannot execute anything. The Squads program enforces the threshold, and the StakePoint program enforces the lock.
Frequently Asked Questions
Do I need the SquadsX browser extension?
No. StakePoint builds the Squads proposal itself from the lock page. Connect any member wallet, paste the multisig address and the flow handles the rest.
Which address do I paste, the vault or the multisig?
The multisig account address, which you will find on your Squad's Settings page in the Squads app. The vault is derived from it automatically. The vault address on its own cannot be traced back to the multisig, so pasting it will not work.
Who owns the lock?
The vault. The lock page shows the vault address as the creator, and only a proposal executed by the Squad can withdraw at the unlock date.
Can I lock LP tokens from a Squads vault?
Yes. Any token the vault holds is listed, including LP tokens from Raydium, Meteora and PumpSwap.
What if my Squad takes days to approve?
That is fine. The proposal waits in Squads until it reaches threshold. The StakePoint page remembers the pending lock in your browser and checks again when you come back, or you can press Check now once it has executed.
How many signatures does the proposing member make?
Usually two, sometimes three for tokens with more accounts involved. These create the proposal and do not move any tokens.
*Lock from your Squads vault: Solana Token Locker. Keep receiving holder distributions while locked: Reward Token Locker. Read the audit and security model: StakePoint Security.*