Before you start
- Use a separate Squad, three independent Solana test wallets supported by Squads, and a test recipient. Keep customer funds and production wallets out of the exercise.
- Check the network and any setup or transaction fees before creating a Squad. Squads limits custom member permissions in its dashboard to Business and Enterprise plans.
Data and access
Who does what
Set a two-wallet threshold
Create the test Squad with three member wallet addresses and a confirmation threshold of two. Record the Squad address and verify each member address from its own wallet.
Check. The test Squad lists your three distinct member addresses and a threshold of two. Check who can approve and execute.
Review and approve from one wallet
Create a small test SOL transfer from the test vault. In Transactions, open the proposal and confirm the vault, asset, amount and recipient. Approve it from one member wallet. The proposal should remain Active. Check the recipient’s balance before continuing.
Check. One eligible member has approved, the status is Active and the recipient balance is unchanged.
Reach the threshold with a second wallet
Open the same proposal from a second member wallet. Review the transfer details before approving. Confirm the proposal moves to Ready and the recipient’s balance is unchanged.
Check. The same proposal has two eligible approvals. It is ready to execute and the recipient balance is still unchanged.
Execute from an eligible wallet
Execute the Ready proposal from a member with execution permission. Check the resulting signature and recipient balance on the same network.
Check. The network confirms the execution signature and the recipient receives the expected test amount.
Check your result
One approval leaves the proposal Active. The second approval makes it Ready. The transfer changes the recipient’s balance after successful execution on the network.
What we tested
Tested on . We loaded the Squads program from Solana devnet and ran it locally in LiteSVM with disposable wallets. With one vote the proposal stayed Active and execution failed. The second vote moved the program state to Approved. Local execution transferred 10,000,000 lamports.
If you get stuck
The proposal stays Active or execution is unavailable
Check that the approvals came from distinct eligible wallets and refer to the same proposal. If you use custom roles, verify that eligible voters can meet the threshold and a member has execution permission. Check whether the Squad has a timelock.