Using a Squads multisig vault with Kausa

Campaign creators can set a Squads multisig vault as the payout address for their campaign. Donations go to that vault, and withdrawals require multiple signers to approve. Nobody can move the funds alone, including the campaign creator.

Why use a multisig?

A regular Solana wallet has one private key. If that key leaks or the holder disappears, the donated funds are gone. A Squads multisig adds N-of-M signing, so for example 2-of-3 signers must approve before anything moves.

This is worth the setup overhead when:

• The campaign is raising enough that single-key control is a real risk.
• An organization needs internal approval controls over the treasury.
• Donors want to see that no one person can drain the wallet.

Setting up a Squads vault

1. Go to app.squads.so and connect your Solana wallet.
2. Click Create a Squad and add the wallet addresses of your co-signers.
3. Choose a threshold (e.g., 2-of-3) and confirm the transaction to deploy the multisig on-chain.
4. Once the Squad exists, open the Vault tab and copy the vault address (a Solana public key like 7Xx...abc).

Using it in Kausa

1. On the Create Campaign page, fill in the usual fields (title, description, goal, payout wallet).
2. Below the payout wallet, paste your Squads vault address into the Squads Multisig Wallet field.
3. Kausa checks the address on-chain. A green checkmark means it found a valid Squads vault.
4. Submit the campaign. Donations will go to the multisig vault from that point on.

The campaign page shows a "🔐 Squads Multisig" badge so donors can see the funds are multisig-protected.

Limitations

• Deploying a Squads multisig costs about 0.1 SOL in rent.
• Every withdrawal needs the required number of signers to approve through the Squads app. This is slower than a regular wallet, by design.
• Kausa currently runs on Solana devnet. Your Squads vault must also be on devnet.

Resources

• Squads documentation
• Squads v4 program on GitHub
• Squads security best practices