Select wallet pop-up
Squad details
Squad members and confirmation threshold setup
Summary of your Squad's details
Treasury tab
Send popup
Coinflow off-ramp popup
Withdrawal Verification
Off-ramping
Bank account details
Amount and Transaction speed
Overview section
Limit order section
Streams section
Active transactions, inflows and outflows sections
Stake section
Managed assets section
Transactions tab
Active transaction. Expanded view
Detailed view
"Ready" transaction
Global Priority Fee
Batch Actions
Auto rent reclaim settings
Members Page
Add member pop-up
Remove member pop-up
Permissions
Fee Relayer
Treasury tab
Sub-accounts
Deposit pop-up
Send pop-up
Sending assets to another wallet
Review page
Batch send
Two options for Batch Send
Receive screen
Tokens in the Coins tab
Burn Tokens
Contacts pop-up
Limit Orders vs Swaps
"Limit Order" tab
"Open Position" section
Spot Swaps
Swap Information
Squads Validator in the Staking Tab
Validator Staking
fuseSOL
## Overview Users can [swap](/main/navigating-your-squad/trade) their SOL from within the Squads app for fuseSOL, the industry's first smart wallet liquid staking token. ## What is fuseSOL fuseSOL is [Fuse’s](https://fusewallet.com/) native LST that: 1. Accrues staking rewards 2. Provides instant liquidity 3. Abstracts Solana network fees in the Fuse app Powered by [Sanctum](https://x.com/sanctumso), fuseSOL is the next generation of LSTs that abstracts away Solana network fees - a feature only possible today with fuseSOL and Fuse, Solana's first smart wallet. ## How to stake with fuseSOL **To swap SOL for fuseSOL:** 1. Go to either the "Treasury" or "Dashboard" Page and find the "Trade" icon. 2. Select either "[Instant Swap](/main/navigating-your-squad/trade/swaps)" or "[Limit Order](/main/navigating-your-squad/trade/limit-orders)" to proceed. 3. Choose the account from which you want to place the trade. 4. Select SOL and fuseSOL as the pair you want to trade and the amount. 5. Launch the transaction. Once the transaction reaches the confirmation threshold and is executed, the swap will be completed. ## How to unstake and withdraw SOL **To swap fuseSOL for SOL:** * Navigate to the "Treasury" tab and click on the "Swap" icon. * Choose fuseSOL and the amount you want to swap to and initiate a transaction.JitoSOL
## Overview Users can deposit their SOL holdings into Jito stake pool, which lets them earn staking rewards with additional returns for MEV redistribution. ## What is JitoSOL JitoSOL is the first MEV-powered liquid staking derivative on Solana. By exchanging your SOL for JitoSOL you maintain SOL's liquidity and earn yield from staking. That yield receives an additional boost thanks to MEV rewards redistribution. ## What is MEV **MEV (Maximum extractable value)** - describes profits that accrue to entities producing blocks on a blockchain based on their ability to include, exclude and change the order of transactions in a block. ## How to stake with Jito Stake Pool **To stake SOL:** 1. Navigate to the "Staking" tab and select "Liquid" section. 2\. Click on the "Jito stake pool" block. 3\. Select the amount of SOL you wish to delegate to the pool and click "Deposit" button. *Please note that staking happens in epochs. Each epoch lasts approximately 3 days. If you stake during an ongoing epoch, you will start earning staking rewards after the start of the next epoch.* 4. Your SOL will start the activating period upon the transaction execution and will appear in the vault as JitoSOL. Once the new epoch starts, you will start earning rewards. ## How to unstake and withdraw SOL **To unstake JitoSOL, you can either swap it or unstake through the Squads app:** * Navigate to the "Treasury" tab, click on the "Swap" icon, choose JitoSOL and the amount you want to swap to, and initiate a transaction. * Or: Click on the "Unstake" button on the "Jito stake pool" block, select the amount you want to unstake, and initiate a transaction. Your JitoSOL tokens will be successfully unstaked after the transaction is executed.Marinade
## Overview Users can deposit their SOL holdings into Marinade stake pool, which lets them earn staking rewards and receive mSOL token, which can be used to gain additional yield. ## What is mSOL Marinade is a non-custodial liquid staking protocol built on the Solana blockchain. With Marinade users can stake their SOL holdings without locking them up. By staking with Marinade users receive mSOL which is issued 1:1 to their initial stake. mSOL then can be used to earn additional rewards through DeFI protocols, which can be accessed using the SquadsX extension. ## How to stake with Marinade Stake Pool **To stake SOL:** 1. Navigate to the "Staking" tab and select "Liquid" section. 2\. Click on the "Marinade stake pool" block. 3\. Select the amount of SOL you wish to delegate to the pool and click "Deposit" button. *Please note that staking happens in epochs. Each epoch lasts approximately 3 days. If you stake during an ongoing epoch, you will start earning staking rewards after the start of the next epoch.* 4. Your SOL will start the activating period upon the transaction execution (more on the transactions [here](/main/navigating-your-squad/transactions#how-transactions-work-inside-squads)) and will appear in the vault as the mSOL. Once the new epoch starts, you will start earning rewards. ## How to unstake from Marinade Stake Pool **To unstake mSOL:** 1. Navigate to the "Treasury" tab, click on the "Swap" icon, choose mSOL and the token you want to swap to, and initiate a transaction. 2. Your mSOL will be successfully unstaked after the transaction is executed.SolBlaze
## Overview Users can deposit their SOL holdings into Solblaze stake pool, which lets them earn staking rewards and receive bSOL token, which can be used to gain additional yield. ## What is bSOL Users can stake their SOL holdings without locking them up with SolBlaze's liquid staking. By staking with SolBlaze, users receive bSOL, which is issued 1:1 to their initial stake. bSOL can then be used to earn additional rewards through DeFi protocols, which can be accessed using the SquadsX extension. ## How to stake with SolBlaze Stake Pool **To stake SOL:** 1. Navigate to the "Staking" tab and select "Liquid" section. 2\. Click on the "SolBlaze stake pool" block. 3\. Select the amount of SOL you wish to delegate to the pool and click "Deposit" button. *Please note that staking happens in epochs. Each epoch lasts approximately 3 days. If you stake during an ongoing epoch, you will start earning staking rewards after the start of the next epoch.* 4. Your SOL will start the activating period upon the transaction execution (more on the transactions [here](/main/navigating-your-squad/transactions)) and will appear in the vault as the bSOL. Once the new epoch starts, you will start earning rewards. ## How to unstake from SolBlaze Stake Pool **To unstake bSOL, you can either swap it or unstake through the Squads app:** * Navigate to the "Treasury" tab, click on the "Swap" icon, choose bSOL and the amount you want to swap to, and initiate a transaction. * Or: Click on the "Unstake" button on the "SolBlaze stake pool" block, select the amount you want to unstake, and initiate a transaction. Your bSOL tokens will be successfully unstaked after the transaction is executed.marginfi
## Overview Users can deposit their SOL holdings into the marginfi stake pool, which lets them earn staking rewards and receive LST token, which can be used to gain additional yield. ## What is LST? Users can stake their SOL holdings without locking them up with marginfi's liquid staking solution. By staking with marginfi, users receive LST, which is issued 1:1 to their initial stake. LST can then be used to earn additional rewards through DeFi protocols, which can be accessed using the SquadsX extension. ## How to stake with marginfi Stake Pool? **To stake LST:** 1. Navigate to the "Staking" tab and select "Liquid" section. 2\. Click on the "marginfi stake pool" block. 3\. Select the amount of SOL you wish to delegate to the pool and click "Deposit" button. *Please note that staking happens in epochs. Each epoch lasts approximately 3 days. If you stake during an ongoing epoch, you will start earning staking rewards after the start of the next epoch.* 4. Your SOL will start the activating period upon the transaction execution (more on the transactions [here](/main/navigating-your-squad/transactions)) and will appear in the vault as the LST. Once the new epoch starts, you will start earning rewards. ## How to unstake from marginfi Stake Pool? **To unstake LST, you can either swap it or unstake through the Squads app:** * Navigate to the "Treasury" tab, click on the "Swap" icon, choose LST and the amount you want to swap to, and initiate a transaction. * Or: Click on the "Unstake" button on the "marginfi stake pool" block, select the amount you want to unstake, and initiate a transaction. Your LST will be successfully unstaked after the transaction is executed.Liquid Staking Tab
Locate the "Stake" button
Stake SOL with Marinade Native
Unstake your SOL from Marinade Native
Programs tab
Add program pop-up
Transfer program upgrade authority
Safe Authority Transfer
Program upgrades
Add upgrade pop-up
Set upgrade buffer authority pop-up
Validators tab
Add validator pop-up
Set withdraw authority pop-up
Safe Authority Transfer (SAT) pop-up
Validator pop-up
Token Manager
Token creation popup
Create Token popup
Mint Token popup
Change Mint Authority
Freeze Account
Transfer Freeze Authority
Burn Freeze Authority
TX Builder tab
Select transaction type
Transaction draft
Populated transaction draft
Anchor transaction
Rust transaction
Base 58 transaction
Settings page
Change threshold pop-up
Spending limits settings
Privacy settings
Treasury tab
Add Safe Multisig pop-up
Safe wallet as a view-only account
Add SquadsX
Download SquadsX
Add your SquadsX key
Squads in the SquadsX extension
What is a Squad?
A Squad is a programmable multi-signature wallet that allows teams and individuals to take full control of their treasury and developer assets.I’m getting an error and can’t create a Squad/create a transaction/sign a transaction.
This can happen due to several reasons. This is a general guideline based on our experience of the most frequent problems and solutions. If those steps are not working for you, please contact us on Discord in the support channel or create a ticket. 1. Make sure you are connected **with the right wallet**, which is already added to a Squad. 2. Make sure to be connected to **the appropriate network**. Squads Protocol is running on Solana mainnet. Check the network setting of your wallet to see to which chain are you connected. 3. Make sure that you **have enough SOL** in your personal wallet (not a Squad’s vault) to pay Solana network fees. 4. If you are using Ledger and all of your transactions are automatically declined with an error, please make sure that you have enabled **blind signing** on the Ledger. Also, make sure that your software is up-to-date.I’ve created a Squad but can’t find my private key. Can you share it with me?
Squads vaults are not traditional hot wallets, they are **PDAs** (Program derived addresses). This means there are no private keys associated with them. PDAs are addresses generated to be controlled only by one specific program. Squads’ vaults are owned and controlled by the Squads program. Please refer to [this section](https://solana.com/docs/core/pda) of Solana docs for an overview of PDAs.Which blockchain is Squads Protocol built on?
Squads Protocol is built on the Solana blockchain.Is Squads Protocol permissionless?
Yes, Squads Protocol is permissionless to interact with.How can I contribute to the protocol?
The protocol's codebase is [open-sourced](https://github.com/Squads-Protocol/v4), allowing you to build on top of it permissionlessly. If you need assistance, please reach out to us on [Discord](https://discord.com/invite/squadsprotocol).Can I connect my Squad to other dapps on Solana?
Yes, to interact with dapps that are not directly integrated inside the platform, users can use the [SquadsX browser extension](/main/navigating-your-squad/squadsx).Can I create a Squad and gate access to it with NFTs?
We don’t support the creation of NFT-gated Squads. Members are added to a Squad via their public keys.Would my assets be affected if the Squads UI is unavailable?
No, as all your assets are stored in the Squads multisig program onchain. In the unlikely event that Squads Labs ceases operations or the UI becomes inaccessible, your assets will remain secure, and only you have the authority to move them. Above all, you can always interact with the program and your assets held within the multisig via either the SDK or the CLI. Learn more [here](/main/additional-resources/what-if-the-squads-app-goes-down).Can I add a custom RPC to use the Squads app?
Yes. By default, the Squads app uses Triton as RPC provider. You can switch to Helius at any time or add a custom RPC provider URL by simply clicking on the "Connect Wallet" button within the Squads app.**Guidelines on Simulating Transactions:** When reviewing a simulated transaction, check the simulation details in the Explorer Inspector. This step ensures that the transaction will perform as intended before executing it. Ideally also ensure the programs your transaction is calling are known to you, as malicious programs have the ability to change execution behavior between when you simulate and when you execute. Here are specific elements to watch out for and how to handle them: * BPFLoaderUpgradeab1e11111111111111111111111: * "New authority Some(XXX)": When you see this message, it means you are changing the buffer/program authority to a different wallet. Confirm that changing the authority is your intended action, and verify that the new wallet address (XXX) is correct. * "Upgraded program XXX": This message indicates that program XXX is being upgraded. Review the transaction details to ensure that this upgrade is expected and intended as part of the transaction. * Token Program (TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA): * "Instruction: Approve": This means that you are delegating funds to another wallet. Confirm that this delegation is intended, as any misconfiguration can lead to a loss of funds. If delegation is not intended, take immediate action to correct it. In addition, double-check the tokens and amounts that will be moved by any transaction. In cases where swaps are involved, be aware that other tokens may be moved as part of the swap, but the total USD value should still align with what you intended. ### Treasury Segmentation While transaction controls like time locks protect individual transactions, treasury segmentation provides an additional layer of security at the organizational level. This strategy involves creating a "cold", advanced security Reserve Treasury account where your business secures the majority of your assets and one or more operations accounts for everyday use that require a lower level of security. **Reserve Treasury** * Contains 85-95% of your total assets * Employs stringent security: higher thresholds, extended time locks * Reserved for infrequent transactions and long-term asset storage * Advanced key management practices (e.g. only use dedicated devices/hardware wallets) for maximum protection **Operations Account** * Holds 5-15% of funds for routine transactions * Uses more accessible security: lower thresholds, accessible key management * Handles payroll, vendor payments, and daily operations * Receives periodic replenishment from the Reserve Treasury **Program Upgrade Account** * Dedicated account with specialized security for program upgrades * Separate from both reserve and operations to isolate upgrade permissions * Employs stringent security: higher thresholds, time locks * Advanced key management practices (e.g. only use dedicated devices/hardware wallets) for maximum protection This structure compartmentalizes risk—if your operations account is compromised, most assets remain protected in your more secure reserve treasury. Meanwhile, your team maintains the operational flexibility needed for day-to-day activities without navigating excessive security hurdles for routine transactions. ### Program Upgrades: Double Verification and Verifiable Builds #### Understanding Buffer Accounts A buffer account is a temporary onchain storage location that holds program code before it's deployed to its final program address. This intermediary step allows for verification before execution of the upgrade. Key Functions: * Stores the compiled program binary data onchain * Enables verification before the actual upgrade occurs * Provides a checkpoint for security review #### Verifiable Builds [Verifiable builds](https://github.com/Ellipsis-Labs/solana-verifiable-build) ensure the integrity of program code throughout the upgrade process by generating a cryptographic hash that can be independently verified by all team members. Implementation Process: * Build your program locally, generating a unique cryptographic hash * Deploy the program to a buffer account * Share the expected hash with all team members * Team members independently verify the buffer content matches this hash * Execute the upgrade from buffer to program account * Post-upgrade, verify the deployed program hash matches the verified buffer This process confirms deployed code matches the audited version, prevents unauthorized modifications, creates an audit trail through git commit references, and enables external verification of deployed programs against audit reports. ### Squads Frontend Verification Accounts with high-value operations - such as Reserve Treasury and Program Upgrade accounts - should ensure transaction integration and the validity of the Squads frontend using multiple interfaces. **Explorers** Explorers provide basic transaction verification but have limitations: Current Capabilities: * View transaction metadata, status, IDs, and associated accounts * Confirm transaction creation time Limitations: * Limited parsing of complex transactions and inner instructions We are currently working with Solana Foundation on parsing Squads transactions in the Solana Explorer and implementing Squads transaction parsing in the Range interface.
**CLI Tools** Direct Interaction: * Users can interact directly with the Squads CLI for core transaction operations. The CLI enables programmatic control of Squads multisig accounts without relying on web interfaces * Links to our CLI tools: [Squads v3 CLI](https://github.com/Squads-Protocol/squads-cli) and [Squads v4 CLI](https://docs.squads.so/main/development/cli/installation) Transaction Verification (coming soon): * No dedicated verification tool exists yet for Squads transactions * A comprehensive CLI tool is under development to automate transaction parsing and verification
**Run UI Locally**\ \ There are two lightweight backup front-ends designed for easy verification, decentralization, and security. These clients are just five files each, making them simple to hash against a commit, deploy to IPFS, or self-host—ensuring complete transparency: * Download and run the Squads lightweight front-ends from GitHub: * v4:
| Exchange | Receive (from Squads multisig) | Deposit (into Squads multisig) |
|---|---|---|
| Coinbase | true | true |
| Binance | true | true |
| Kraken | true | true |
| Backpack | true | true |
| OKX | true | true |
| Swissborg | true | true |
| Bybit | true | false |
| Bitget | true | false |
Squads on mobile
| OtterSec Formal Verification | /files/2M58gZY9oQQc9ro66ZLR | https://osec.io/blog/2023-01-26-formally-verifying-solana-programs#case-study-squads-multisig |
const connection = new Connection("http://localhost:8899", "confirmed");
| Read more about development on Squads | ||
| Join the Squads Discord |
import * as multisig from "@sqds/multisig";
import { Connection, Keypair } from "@solana/web3.js";
// Defines permissions enum
const { Permission, Permissions } = multisig.types;
async function main() {
// Cluster Connection
// Required argument if you use the .rpc method
const connection = new Connection("< your rpc here >");
// Random Public Key that will be used to derive a multisig PDA
// This will need to be a signer on the transaction
const createKey = Keypair.generate().publicKey;
// Creator should be a Keypair or a Wallet Adapter wallet
const creator = Keypair.generate();
// Derive the multisig PDA
const [multisigPda] = multisig.getMultisigPda({
createKey,
});
const programConfigPda = multisig.getProgramConfigPda({})[0];
const programConfig =
await multisig.accounts.ProgramConfig.fromAccountAddress(
connection,
programConfigPda
);
const configTreasury = programConfig.treasury;
const ix = await multisig.instructions.multisigCreateV2({
// Must sign the transaction, unless the .rpc method is used.
createKey: createKey.publicKey,
// The creator & fee payer
creator: creator.publicKey,
// The PDA of the multisig you are creating, derived by a random PublicKey
multisigPda,
// Here the config authority will be the system program
configAuthority: null,
// Create without any time-lock
timeLock: 0,
// List of the members to add to the multisig
members: [{
// Members Public Key
key: creator.publicKey,
// Granted Proposer, Voter, and Executor permissions
permissions: Permissions.all(),
},
{
key: secondMember.publicKey,
// Member can only add votes to proposed transactions
permissions: Permissions.fromPermissions([Permission.Vote]),
},
],
// This means that there needs to be 2 votes for a transaction proposal to be approved
threshold: 2,
// This is for the program config treasury account
treasury: configTreasury,
// Rent reclaim account
rentCollector: null
});
console.log("Multisig created: ", signature)
}
import * as multisig from "@sqds/multisig";
import { Connection, PublicKey } from "@solana/web3.js";
async function main(member: PublicKey) {
// Cluster Connection
// Required argument if you use the .rpc method
const connection = new Connection("<your rpc url>");
// If you've saved your createKey, you can define it as a static PublicKey
const createKey = new PublicKey("<your createkey>")
// Derive the multisig PDA
const [multisigPda] = multisig.getMultisigPda({
createKey,
});
// or
// const multisigPda = new PublicKey("<your multisig key>");
// Derive the PDA of the Squads Vault
const [vaultPda] = multisig.getVaultPda({
multisigPda,
index: 0,
});
// Get deserialized multisig account info
const multisigInfo = await multisig.accounts.Multisig.fromAccountAddress(
connection,
multisigPda
);
// Get the updated transaction index
const currentTransactionIndex = Number(multisigInfo.transactionIndex);
const newTransactionIndex = BigInt(currentTransactionIndex + 1);
// Create a config transaction, of type changeThreshold
const ix = await multisig.instructions.configTransactionCreate({
feePayer: member,
multisigPda: controlledMultisigPda,
// Replace with current index if needed
transactionIndex: newTransactionIndex,
// Member must have at least "Proposer" permissions
creator: member,
actions: [{
// Type of action
__kind: "ChangeThreshold",
newThreshold: 3
}],
}),
}
import * as multisig from "@sqds/multisig";
import { Connection, PublicKey } from "@solana/web3.js"
async function main(member: PublicKey) {
// Cluster Connection
const connection = new Connection("<your rpc url>");
// If you've saved your createKey, you can define it as a static PublicKey
const createKey = new PublicKey("<your createkey>")
// Derive the multisig PDA
const [multisigPda] = multisig.getMultisigPda({
createKey,
});
// or
// const multisigPda = new PublicKey("<your multisig key>");
// Get deserialized multisig account info
const multisigInfo = await multisig.accounts.Multisig.fromAccountAddress(
connection,
multisigPda
);
// Get the current transaction index
const transactionIndex = Number(multisigInfo.transactionIndex);
// or, if this is tied to your first transaction
// const transactionIndex = 1n;
const ix = await multisig.instructions.proposalCancel({
multisigPda,
transactionIndex,
// Member must have "Voter" permissions
member: member,
});
}