# Table of Contents

- [What is Squads Protocol | Development | Squads Docs](#what-is-squads-protocol-development-squads-docs)
- [What is SquadsX | SquadsX Beta (Development) | Squads Docs](#what-is-squadsx-squadsx-beta-development-squads-docs)
- [Understanding the SquadsX Extension Wallet | SquadsX Beta (Development) | Squads Docs](#understanding-the-squadsx-extension-wallet-squadsx-beta-development-squads-docs)
- [Overcoming Integration Obstacles | SquadsX Beta (Development) | Squads Docs](#overcoming-integration-obstacles-squadsx-beta-development-squads-docs)
- [Not Using Wallet Standard Adapter | SquadsX Beta (Development) | Squads Docs](#not-using-wallet-standard-adapter-squadsx-beta-development-squads-docs)
- [Ephemeral Signers | SquadsX Beta (Development) | Squads Docs](#ephemeral-signers-squadsx-beta-development-squads-docs)
- [UI Feedback and Delayed Execution | SquadsX Beta (Development) | Squads Docs](#ui-feedback-and-delayed-execution-squadsx-beta-development-squads-docs)
- [Large Transaction Problem | SquadsX Beta (Development) | Squads Docs](#large-transaction-problem-squadsx-beta-development-squads-docs)
- [Mandatory Sign-In with Off-chain Message Signing | SquadsX Beta (Development) | Squads Docs](#mandatory-sign-in-with-off-chain-message-signing-squadsx-beta-development-squads-docs)
- [Security Audits | Security | Squads Docs](#security-audits-security-squads-docs)
- [How secure is Squads | Security | Squads Docs](#how-secure-is-squads-security-squads-docs)
- [Squads Protocol v3 | Security | Squads Docs](#squads-protocol-v3-security-squads-docs)
- [Formal Verifications | Security | Squads Docs](#formal-verifications-security-squads-docs)
- [Squads Protocol v4 | Security | Squads Docs](#squads-protocol-v4-security-squads-docs)
- [Squads Protocol v3 | Security | Squads Docs](#squads-protocol-v3-security-squads-docs)
- [Squads Protocol v4 | Security | Squads Docs](#squads-protocol-v4-security-squads-docs)
- [Bug bounty | Security | Squads Docs](#bug-bounty-security-squads-docs)
- [Instructions | Development | Squads Docs](#instructions-development-squads-docs)
- [Use Cases | Development | Squads Docs](#use-cases-development-squads-docs)
- [Quickstart | Development | Squads Docs](#quickstart-development-squads-docs)
- [Multisig | Development | Squads Docs](#multisig-development-squads-docs)
- [Accounts | Development | Squads Docs](#accounts-development-squads-docs)
- [Vault | Development | Squads Docs](#vault-development-squads-docs)
- [Create Multisig | Development | Squads Docs](#create-multisig-development-squads-docs)
- [Overview | Development | Squads Docs](#overview-development-squads-docs)
- [Reject Proposal | Development | Squads Docs](#reject-proposal-development-squads-docs)
- [Controlled Multisig Instructions | Development | Squads Docs](#controlled-multisig-instructions-development-squads-docs)
- [Controlled Multisigs | Development | Squads Docs](#controlled-multisigs-development-squads-docs)
- [Batch | Development | Squads Docs](#batch-development-squads-docs)
- [Transactions | Development | Squads Docs](#transactions-development-squads-docs)
- [Close Vault Transaction Account | Development | Squads Docs](#close-vault-transaction-account-development-squads-docs)
- [SDKs | Development | Squads Docs](#sdks-development-squads-docs)
- [Create Config Transaction | Development | Squads Docs](#create-config-transaction-development-squads-docs)
- [Approve Proposal | Development | Squads Docs](#approve-proposal-development-squads-docs)
- [Time-locks | Development | Squads Docs](#time-locks-development-squads-docs)
- [Permissions | Development | Squads Docs](#permissions-development-squads-docs)
- [Add To Batch | Development | Squads Docs](#add-to-batch-development-squads-docs)
- [Remove Spending Limit | Development | Squads Docs](#remove-spending-limit-development-squads-docs)
- [Spending Limits | Development | Squads Docs](#spending-limits-development-squads-docs)
- [Create Proposal | Development | Squads Docs](#create-proposal-development-squads-docs)
- [We're here to help | Development | Squads Docs](#we-re-here-to-help-development-squads-docs)
- [Installation | Development | Squads Docs](#installation-development-squads-docs)
- [Cancel Proposal | Development | Squads Docs](#cancel-proposal-development-squads-docs)
- [Vault Check | Development | Squads Docs](#vault-check-development-squads-docs)
- [Execute Config Transaction | Development | Squads Docs](#execute-config-transaction-development-squads-docs)
- [Add spending limit | Development | Squads Docs](#add-spending-limit-development-squads-docs)
- [Execute Vault Transaction | Development | Squads Docs](#execute-vault-transaction-development-squads-docs)
- [Create Batch | Development | Squads Docs](#create-batch-development-squads-docs)
- [Proposal | Development | Squads Docs](#proposal-development-squads-docs)
- [Accounts | Development | Squads Docs](#accounts-development-squads-docs)
- [Create Vault Transaction | Development | Squads Docs](#create-vault-transaction-development-squads-docs)
- [Add Member | Development | Squads Docs](#add-member-development-squads-docs)
- [Remove Member | Development | Squads Docs](#remove-member-development-squads-docs)
- [Squads Actions and Blinks | Development | Squads Docs](#squads-actions-and-blinks-development-squads-docs)
- [Migrating from MultisigCreate v1 to v2 | Development | Squads Docs](#migrating-from-multisigcreate-v1-to-v2-development-squads-docs)
- [Set Rent Collector | Development | Squads Docs](#set-rent-collector-development-squads-docs)
- [Developers | Squads Legacy (v3) | Squads Docs](#developers-squads-legacy-v3-squads-docs)
- [Activating a Transaction | Squads Legacy (v3) | Squads Docs](#activating-a-transaction-squads-legacy-v3-squads-docs)
- [Swap | Squads Legacy (v3) | Squads Docs](#swap-squads-legacy-v3-squads-docs)
- [Owners and Settings | Squads Legacy (v3) | Squads Docs](#owners-and-settings-squads-legacy-v3-squads-docs)
- [Staking | Squads Legacy (v3) | Squads Docs](#staking-squads-legacy-v3-squads-docs)
- [Tensor | Squads Legacy (v3) | Squads Docs](#tensor-squads-legacy-v3-squads-docs)
- [Bonfida | Squads Legacy (v3) | Squads Docs](#bonfida-squads-legacy-v3-squads-docs)
- [Transactions | Squads Legacy (v3) | Squads Docs](#transactions-squads-legacy-v3-squads-docs)
- [Create a Squad | Squads Legacy (v3) | Squads Docs](#create-a-squad-squads-legacy-v3-squads-docs)
- [What's a Squad? | Squads Legacy (v3) | Squads Docs](#what-s-a-squad-squads-legacy-v3-squads-docs)
- [General | Squads Legacy (v3) | Squads Docs](#general-squads-legacy-v3-squads-docs)
- [Creators | Squads Legacy (v3) | Squads Docs](#creators-squads-legacy-v3-squads-docs)
- [Apps | Squads Legacy (v3) | Squads Docs](#apps-squads-legacy-v3-squads-docs)
- [Dialect | Squads Legacy (v3) | Squads Docs](#dialect-squads-legacy-v3-squads-docs)
- [Costs of using Squads | Squads Legacy (v3) | Squads Docs](#costs-of-using-squads-squads-legacy-v3-squads-docs)
- [Dashboard | Squads Legacy (v3) | Squads Docs](#dashboard-squads-legacy-v3-squads-docs)
- [Authorities | Squads Legacy (v3) | Squads Docs](#authorities-squads-legacy-v3-squads-docs)
- [PDAs | Squads Legacy (v3) | Squads Docs](#pdas-squads-legacy-v3-squads-docs)
- [Transactions | Squads Legacy (v3) | Squads Docs](#transactions-squads-legacy-v3-squads-docs)
- [Coinflow | Squads Legacy (v3) | Squads Docs](#coinflow-squads-legacy-v3-squads-docs)
- [Token Manager | Squads Legacy (v3) | Squads Docs](#token-manager-squads-legacy-v3-squads-docs)
- [Loading the Program | Squads Legacy (v3) | Squads Docs](#loading-the-program-squads-legacy-v3-squads-docs)
- [Stakewiz | Squads Legacy (v3) | Squads Docs](#stakewiz-squads-legacy-v3-squads-docs)
- [Derivation | Squads Legacy (v3) | Squads Docs](#derivation-squads-legacy-v3-squads-docs)
- [Executing | Squads Legacy (v3) | Squads Docs](#executing-squads-legacy-v3-squads-docs)
- [Create a Multisig | Squads Legacy (v3) | Squads Docs](#create-a-multisig-squads-legacy-v3-squads-docs)
- [Anchor IDL | Squads Legacy (v3) | Squads Docs](#anchor-idl-squads-legacy-v3-squads-docs)
- [Vault | Squads Legacy (v3) | Squads Docs](#vault-squads-legacy-v3-squads-docs)
- [Multisig | Squads Legacy (v3) | Squads Docs](#multisig-squads-legacy-v3-squads-docs)
- [Instruction | Squads Legacy (v3) | Squads Docs](#instruction-squads-legacy-v3-squads-docs)
- [Validators | Squads Legacy (v3) | Squads Docs](#validators-squads-legacy-v3-squads-docs)
- [Transaction | Squads Legacy (v3) | Squads Docs](#transaction-squads-legacy-v3-squads-docs)
- [SDK | Squads Legacy (v3) | Squads Docs](#sdk-squads-legacy-v3-squads-docs)
- [SolBlaze | Squads Legacy (v3) | Squads Docs](#solblaze-squads-legacy-v3-squads-docs)
- [Approve / Reject a Transaction | Squads Legacy (v3) | Squads Docs](#approve-reject-a-transaction-squads-legacy-v3-squads-docs)
- [Create a Transaction | Squads Legacy (v3) | Squads Docs](#create-a-transaction-squads-legacy-v3-squads-docs)
- [What is a multisig | Squads Docs](#what-is-a-multisig-squads-docs)
- [Adding Instructions | Squads Legacy (v3) | Squads Docs](#adding-instructions-squads-legacy-v3-squads-docs)
- [JitoSOL | Squads Legacy (v3) | Squads Docs](#jitosol-squads-legacy-v3-squads-docs)
- [Marinade | Squads Legacy (v3) | Squads Docs](#marinade-squads-legacy-v3-squads-docs)
- [Welcome to Squads Multisig | Squads Docs](#welcome-to-squads-multisig-squads-docs)
- [Rent Reclaim | Squads Docs](#rent-reclaim-squads-docs)
- [Who we are - Squads Labs | Squads Docs](#who-we-are-squads-labs-squads-docs)
- [Fee Relayer | Squads Docs](#fee-relayer-squads-docs)
- [TX Builder | Squads Legacy (v3) | Squads Docs](#tx-builder-squads-legacy-v3-squads-docs)
- [Priority fees | Squads Docs](#priority-fees-squads-docs)
- [Manage Members | Squads Docs](#manage-members-squads-docs)
- [Lido | Squads Legacy (v3) | Squads Docs](#lido-squads-legacy-v3-squads-docs)
- [Contacts | Squads Docs](#contacts-squads-docs)
- [Programs | Squads Legacy (v3) | Squads Docs](#programs-squads-legacy-v3-squads-docs)
- [Batch actions | Squads Docs](#batch-actions-squads-docs)
- [Limit Orders | Squads Docs](#limit-orders-squads-docs)
- [On and Off-Ramp | Squads Docs](#on-and-off-ramp-squads-docs)
- [Swaps | Squads Docs](#swaps-squads-docs)
- [Trade | Squads Docs](#trade-squads-docs)
- [Coin List Filter | Squads Docs](#coin-list-filter-squads-docs)
- [Privacy | Squads Docs](#privacy-squads-docs)
- [Security | Squads Docs](#security-squads-docs)
- [Sub-accounts | Squads Docs](#sub-accounts-squads-docs)
- [Permissions | Squads Docs](#permissions-squads-docs)
- [Treasury | Squads Docs](#treasury-squads-docs)
- [Airdrop Checker | Squads Docs](#airdrop-checker-squads-docs)
- [Create a Squad | Squads Docs](#create-a-squad-squads-docs)
- [Payments | Squads Docs](#payments-squads-docs)
- [Sphere | Squads Docs](#sphere-squads-docs)
- [Direct Staking | Squads Docs](#direct-staking-squads-docs)
- [Reporting and Accounting | Squads Docs](#reporting-and-accounting-squads-docs)
- [Stake | Squads Docs](#stake-squads-docs)
- [Commands | Development | Squads Docs](#commands-development-squads-docs)
- [Key aspects of using a multisig | Squads Docs](#key-aspects-of-using-a-multisig-squads-docs)
- [Sending assets to/from centralized exchange (CEXs) | Squads Docs](#sending-assets-to-from-centralized-exchange-cexs-squads-docs)
- [Developers assets | Squads Docs](#developers-assets-squads-docs)
- [Staking with Squads | Squads Docs](#staking-with-squads-squads-docs)
- [Members | Squads Docs](#members-squads-docs)
- [Marinade Native | Squads Docs](#marinade-native-squads-docs)
- [Virtual US Bank Account | Squads Docs](#virtual-us-bank-account-squads-docs)
- [Spending Limits | Squads Docs](#spending-limits-squads-docs)
- [Integral | Squads Docs](#integral-squads-docs)
- [Costs of using Squads | Squads Docs](#costs-of-using-squads-squads-docs)
- [Request Finance | Squads Docs](#request-finance-squads-docs)
- [Time Locks | Squads Docs](#time-locks-squads-docs)
- [SquadsX | Squads Docs](#squadsx-squads-docs)
- [What if the Squads app goes down | Squads Docs](#what-if-the-squads-app-goes-down-squads-docs)
- [SNS | Squads Docs](#sns-squads-docs)
- [Range | Squads Docs](#range-squads-docs)
- [Squads on Mobile | Squads Docs](#squads-on-mobile-squads-docs)
- [Dashboard | Squads Docs](#dashboard-squads-docs)
- [Pricing | Squads Docs](#pricing-squads-docs)
- [Integrated apps | Squads Docs](#integrated-apps-squads-docs)
- [Transactions | Squads Docs](#transactions-squads-docs)
- [Bridge Off-Ramp | Squads Docs](#bridge-off-ramp-squads-docs)
- [Transaction Builder | Squads Docs](#transaction-builder-squads-docs)
- [Coinflow Off-ramp | Squads Docs](#coinflow-off-ramp-squads-docs)
- [TipLink | Squads Docs](#tiplink-squads-docs)
- [Third-Party Payouts | Squads Docs](#third-party-payouts-squads-docs)
- [FAQs | Squads Docs](#faqs-squads-docs)
- [Manage assets | Squads Docs](#manage-assets-squads-docs)
- [Safe | Squads Docs](#safe-squads-docs)
- [Settings | Squads Docs](#settings-squads-docs)
- [Validators | Squads Docs](#validators-squads-docs)
- [Advanced Security Best Practices | Squads Docs](#advanced-security-best-practices-squads-docs)
- [Start using SquadsX | Squads Docs](#start-using-squadsx-squads-docs)
- [Compatible Apps | Squads Docs](#compatible-apps-squads-docs)
- [Quickstart Guide | Squads Docs](#quickstart-guide-squads-docs)
- [Liquid Staking | Squads Docs](#liquid-staking-squads-docs)
- [Token Manager | Squads Docs](#token-manager-squads-docs)
- [Programs | Squads Docs](#programs-squads-docs)
- [Treasury Management Overview | Squads Docs](#treasury-management-overview-squads-docs)
- [Email Protection | Cloudflare](#email-protection-cloudflare)

---

# What is Squads Protocol | Development | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F2000527778-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FN3uSSG0wf4ItEAVWx2hY%252Fuploads%252FZLmIMLB5MuaJDHQmgWER%252Fsquads-protocol-solana-account-abstraction-smart-contract-wallet-infrastructure-multisig-solana-svm-multi-signature-tokenized-assets-squads-solana.png%3Falt%3Dmedia%26token%3D19994c12-eafe-42f5-8665-0cc4bd60b9b0&width=1248&dpr=4&quality=100&sign=3dbdb386&sv=2)

Squads Protocol is a collection of programs on the Solana blockchain that implements smart contract-level account abstraction and acts as the perfect foundation for building products that will help onboard the next billion users into crypto.

It secures $10+ billion in value and the leading product built on top of it, the Squads platform, is trusted and used by over 250 teams in the ecosystem, such as Jupiter, Pyth, Raydium, Marginfi, Backpack, Drift, Helius, Kamino, Jito, Tensor, Helium and many others.

Squads Protocol is a collection of programs (smart contracts) that enables developers to use smart account technology to build novel asset management and self-custody solutions.

Since its launch in 2021, Squads Protocol has become Solana's smart account standard - securing $10+ billion in value for leading teams, applications, and institutions. We are trusted and used by over 250 teams in the ecosystem, such as Jupiter, Pyth, Raydium, Marginfi, Backpack, Drift, Helius, Kamino, Jito, Tensor, Helium, and many others.

Due to its permissionless nature, developers can seamlessly integrate Squads Protocol's programs into their own applications, enabling enhanced features that leverage multi-signature functionality and Solana's account abstraction capabilities. These features include spending limits, sub-accounts, time locks, and more.

To start your journey into interacting with Squads Protocol and the v4 program, you can read our [Quickstart](https://docs.squads.so/main/development/introduction/quickstart)
 guide. It will walk you through creating a complete workflow using the Squads Typescript SDK in just 10 minutes.

For more specific instructions, head to the [Overview](https://docs.squads.so/main/development/typescript/overview)
 page.

[NextUse Cases](https://docs.squads.so/main/development/introduction/use-cases)

Last updated 1 year ago

---

# What is SquadsX | SquadsX Beta (Development) | Squads Docs

SquadsX is a web-extension wallet powered by Squads Protocol and its v4 program. It enables users to safely engage with Solana applications through their Squad. This simplifies the creation of multisig transactions, allowing users to interact with applications as they would with conventional wallets.

This documentation provides a developer reference for using and integrating with SquadsX.

### 

[](https://docs.squads.so/main/squadsx-beta-development#why-squadsx-matters)

Why SquadsX Matters

Think of SquadsX as the next big step in the evolution of self-custody - it's convenient, secure, and forgiving. It's a significant addition to the primary Squads product. This web-extension wallet can potentially unlock access to the value managed by numerous active Squads for many existing Solana products. We believe that improvements in the wallet-app compatibility could scale up opportunities for the entire ecosystem.

[NextUnderstanding the SquadsX Extension Wallet](https://docs.squads.so/main/squadsx-beta-development/understanding-the-squadsx-extension-wallet)

Last updated 2 years ago

---

# Understanding the SquadsX Extension Wallet | SquadsX Beta (Development) | Squads Docs

Technically, SquadsX is a Wallet Standard-compliant browser extension wallet. It holds the private key of a Squad member, which it uses for signing transactions. While linked to applications, SquadsX communicates the Squads Multisig Vault PDA as the active address. The transaction signing process occurs behind the scenes as follows:

1.  The application creates an original transaction (OT) that uses the Vault as the "signer" address.
    
2.  SquadsX disassembles the OT, crafting a new Multisig Transaction (MT) from the OT's instructions. Essentially, the MT is a transaction that saves the instructions on-chain, allowing for later execution upon multisig member approval.
    
3.  SquadsX uses the member's private key to sign the MT, returning a signed MT that "wraps" the OT back to the application.
    
4.  The application submits the signed MT to an RPC node, creating a new Squads Multisig Transaction account on-chain.
    
5.  With the completion of the app-side process, an asynchronous voting procedure starts, usually conducted in the Squads app or an alternative user interface.
    
6.  Once the Squads Multisig Transaction receives approval, the transaction execution commences within the Squads app, implementing the instructions contained within the OT via one or more CPI calls "signed" by the Vault PDA.
    

[PreviousWhat is SquadsX](https://docs.squads.so/main/squadsx-beta-development)
[NextOvercoming Integration Obstacles](https://docs.squads.so/main/squadsx-beta-development/guides/overcoming-integration-obstacles)

Last updated 2 years ago

---

# Overcoming Integration Obstacles | SquadsX Beta (Development) | Squads Docs

Off the bat, SquadsX might already be perfectly integrated with your app, assuming it supports the Wallet Standard and embodies certain characteristics, which we will discuss in detail later.

Nevertheless, Smart Wallets are relatively new players in the Solana space. Multisig Transactions deviate from standard transactions, demanding multiple green lights before execution. Thus, the creation and execution of a transaction becomes an asynchronous multi-step process.

To ensure full compatibility with SquadsX and similar Smart Wallets that utilize the "delayed transaction execution" strategy, app developers might need to occasionally contemplate specific measures. With this in mind, we're joining forces with leading Solana products to smooth out any existing rough edges.

Here are the common issues we've stumbled upon during SquadsX's testing phase, and the recommended solutions for each:

1.  [Not using the Wallet Standard adapter](https://docs.squads.so/main/squadsx-beta-development/guides/overcoming-integration-obstacles/not-using-wallet-standard-adapter)
    
2.  [Ephemeral Signers](https://docs.squads.so/main/squadsx-beta-development/guides/overcoming-integration-obstacles/ephemeral-signers)
    
3.  [Large transaction problem](https://docs.squads.so/main/squadsx-beta-development/guides/overcoming-integration-obstacles/large-transaction-problem)
    
4.  [UI feedback and delayed execution](https://docs.squads.so/main/squadsx-beta-development/guides/overcoming-integration-obstacles/ui-feedback-and-delayed-execution)
    
5.  [Mandatory Sign-In with off-chain message signing](https://docs.squads.so/main/squadsx-beta-development/guides/overcoming-integration-obstacles/mandatory-sign-in-with-off-chain-message-signing)
    

[PreviousUnderstanding the SquadsX Extension Wallet](https://docs.squads.so/main/squadsx-beta-development/understanding-the-squadsx-extension-wallet)
[NextNot Using Wallet Standard Adapter](https://docs.squads.so/main/squadsx-beta-development/guides/overcoming-integration-obstacles/not-using-wallet-standard-adapter)

Last updated 2 years ago

---

# Not Using Wallet Standard Adapter | SquadsX Beta (Development) | Squads Docs

**TLDR:** Update your Wallet Adapter package to the latest version that supports the Wallet Standard.

**Problem**

The Wallet Standard is a protocol and a collection of interfaces that allows apps to automatically detect the wallets installed by the user. SquadsX implements Wallet Standard and should be recognized by most of the apps already. That said, not every app uses the latest Wallet Adapter version that supports Wallet Standard.

**Solution**

If your app doesn't detect an installed SquadsX extension, make sure to update the [Wallet Adapter](https://github.com/solana-labs/wallet-adapter)
 package to the latest version.

[PreviousOvercoming Integration Obstacles](https://docs.squads.so/main/squadsx-beta-development/guides/overcoming-integration-obstacles)
[NextEphemeral Signers](https://docs.squads.so/main/squadsx-beta-development/guides/overcoming-integration-obstacles/ephemeral-signers)

Last updated 2 years ago

---

# Ephemeral Signers | SquadsX Beta (Development) | Squads Docs

**TLDR:** Avoid Ephemeral Signers in your transactions if possible. If not, prefer `SystemProgram.createAccountWithSeed` to `SystemProgram.createAccount`. If that doesn't work either use the `getEphemeralSigners` API exposed by SquadsX via the Wallet Standard interface.

**Problem**

Ephemeral Signer (ES) is a key that is expected to sign the transaction and be discarded right after. An example of when such ephemeral signers are needed is the `SystemProgram.createAccount` instruction. This instruction requires the new account to be a signer to verify that whoever calls this instruction actually holds authority over this account.

The `Keypair.generate()` method is typically used by app developers to create ephemeral signers, but this mechanism doesn't work with Smart Wallets that don't execute the transaction immediately. In these cases, the ephemeral keypair will not be available to sign the "execute" transaction because it has already been lost and forgotten.

**Solution 1**

Quite often you can avoid Ephemeral Signers completely by using `SystemProgram.createAccountWithSeed` instead of `SystemProgram.createAccount`. The difference between the two is that the latter requires the new account's signature, whereas the former doesn't because the new account is "controlled" by the `basePubkey` which most likely is your primary singer anyway.

For example, here's how you can do this in a transaction that typically requires an Ephemeral Signer: wrapping SOL via an auxiliary token account.

Copy

    // Generate a random seed.
    const seed = Keypair.generate().publicKey.toBase58().slice(0, 32);
    
    // Calculate a publicKey that will be controlled by the walletPubkey.
    const auxAccountPubkey = await PublicKey.createWithSeed(
      walletPubkey,
      seed,
      TOKEN_PROGRAM_ID
    );
    
    // Create token account.
    // Using `createAccountWithSeed` allows us to avoid the second signer,
    // because this instruction requires signing only from `basePubkey`.
    const createAccountIx = SystemProgram.createAccountWithSeed({
      fromPubkey: walletPubkey,
      basePubkey: walletPubkey,
      seed,
      newAccountPubkey: auxAccountPubkey,
      lamports: (await getMinimumBalanceForRentExemptAccount(connection)) + amount,
      space: ACCOUNT_SIZE,
      programId: TOKEN_PROGRAM_ID,
    });// Some code

**Solution 2**

If the Solution 1 doesn't fit your needs, and you absolutely need a second signer in your transaction, we got you covered too. SquadsX exposes the `getEphemeralSigners` API that allows apps to request any number of ephemeral signers from the wallet. The wallet returns an array of account addresses that the app developer can use in their transactions. The API is exposed via the Wallet Standard feature detection mechanism and can be used as follows.

Copy

    import { useWallet } from "@solana/wallet-adapter-react";
    
    const { wallet } = useWallet()
    
    // ...
      
    <button
      onClick={async () => {
        const adapter = wallet?.adapter;
    
        const ephemeralSignerAddress = adapter &&
          "standard" in adapter &&
          "fuse:getEphemeralSigners" in adapter.wallet.features &&
          (await adapter.wallet.features["fuse:getEphemeralSigners"].getEphemeralSigners(1))[0]
    
        const ephemeralSignerPubkey = ephemeralSignerAddress ? new Pubkey(ephemeralSignerAddress) : null
    
        // Use `ephemeralSignerPubkey` in your transaction.
      })}
    />// Some code

There's an open sRFC with the effort of making this feature into the Wallet Standard, so other wallets can implement it too. Once it happens, we hope that using`Keypair.generate` for creating Ephemeral Signers becomes a thing of a past.

[PreviousNot Using Wallet Standard Adapter](https://docs.squads.so/main/squadsx-beta-development/guides/overcoming-integration-obstacles/not-using-wallet-standard-adapter)
[NextLarge Transaction Problem](https://docs.squads.so/main/squadsx-beta-development/guides/overcoming-integration-obstacles/large-transaction-problem)

Last updated 2 years ago

---

# UI Feedback and Delayed Execution | SquadsX Beta (Development) | Squads Docs

**TLDR**: Don't show errors or optimistic UI state update if you can't detect the transaction effect: the transaction executions may be delayed.

_A complete guide on how UI feedback and delayed execution will be available shortly._

[PreviousLarge Transaction Problem](https://docs.squads.so/main/squadsx-beta-development/guides/overcoming-integration-obstacles/large-transaction-problem)
[NextMandatory Sign-In with Off-chain Message Signing](https://docs.squads.so/main/squadsx-beta-development/guides/overcoming-integration-obstacles/mandatory-sign-in-with-off-chain-message-signing)

Last updated 2 years ago

---

# Large Transaction Problem | SquadsX Beta (Development) | Squads Docs

**TLDR**: Use Address Lookup Tables (ALTs) and Versioned Transactions to reduce the transaction size.

_A complete guide on how to implement ALTs and versioned transactions will be available shortly._

[PreviousEphemeral Signers](https://docs.squads.so/main/squadsx-beta-development/guides/overcoming-integration-obstacles/ephemeral-signers)
[NextUI Feedback and Delayed Execution](https://docs.squads.so/main/squadsx-beta-development/guides/overcoming-integration-obstacles/ui-feedback-and-delayed-execution)

Last updated 2 years ago

---

# Mandatory Sign-In with Off-chain Message Signing | SquadsX Beta (Development) | Squads Docs

**TLDR**: Avoid making the Sign-In mandatory for using the app, consider the scenario when a wallet can't sign messages (PDA). In the long term, support the Sign-In with Smart Wallet standard.

[PreviousUI Feedback and Delayed Execution](https://docs.squads.so/main/squadsx-beta-development/guides/overcoming-integration-obstacles/ui-feedback-and-delayed-execution)

Last updated 2 years ago

---

# Security Audits | Security | Squads Docs

Squads Labs has engaged several reputable audit firms to thoroughly review the codebase of Squads Protocol and its associated programs:

*   [Security audits of Squads Protocol v4](https://docs.squads.so/main/security/security-audits/squads-protocol-v4)
     (powering Squads);
    
*   [Security audits of Squads Protocol v3](https://docs.squads.so/main/security/security-audits/squads-protocol-v3)
     (powering Squads Legacy).
    

These third-party audits ensure a neutral and in-depth assessment of the security of Squads Protocol.

[PreviousHow secure is Squads](https://docs.squads.so/main/security)
[NextSquads Protocol v4](https://docs.squads.so/main/security/security-audits/squads-protocol-v4)

Last updated 1 year ago

---

# How secure is Squads | Security | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F785938575-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FZK4Op7PNd2kAk4XdWjb8%252Fuploads%252F9sSLkWDO3Gz1bMvKF27f%252Fsquads%2520security.png%3Falt%3Dmedia%26token%3D81e98a48-38bd-4ffd-88bb-f14865b15c32&width=1248&dpr=4&quality=100&sign=18526cde&sv=2)

The Squads platform is built on top of Squads Protocol — the smart account standard on Solana and the SVM, securing $10 billion across 40+ thousand smart accounts.

To ensure that it is secure, we have taken the following actions:

1.  [Multiple security audits](https://docs.squads.so/main/security/security-audits)
    ;
    
2.  [Several formal verifications of the program](https://docs.squads.so/main/security/formal-verifications)
    ;
    
3.  [A perpetual bug bounty program](https://docs.squads.so/main/security/bug-bounty)
    .
    

Squads Protocol's codebase is open-sourced (available to view [here](https://github.com/Squads-Protocol/v4)
) and the programs have been written in [Anchor](https://www.anchor-lang.com/)
, a framework for building secure Solana programs.

Additionally, we strongly believe that core primitives existing on open and permissionless networks should be made immutable as soon as practically possible. We are committed to making Squads Protocol programs immutable within months of public release.

*   Squads Protocol v3 (powering Squads Legacy) has been [immutable since February 2023](https://x.com/SquadsProtocol/status/1628776620243963904?s=20)
     and Squads Labs nor anyone else can alter the on-chain code in any way.
    
*   Squads Protocol v4 (powering Squads) was launched in October 2023 and it has been [immutable since November 2024](https://x.com/SquadsProtocol/status/1859947607671607443)
    , unalterable by Squads Labs or any third party.
    

[NextSecurity Audits](https://docs.squads.so/main/security/security-audits)

Last updated 11 months ago

---

# Squads Protocol v3 | Security | Squads Docs

[](https://github.com/Squads-Protocol/squads-mpl/blob/main/Squads_V3_Audit_Bramah.pdf)

![Cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F785938575-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FZK4Op7PNd2kAk4XdWjb8%252Fuploads%252FSn4qPhynYwd2HrzaCbrm%252FScreenshot%25202023-09-27%2520at%252010.06.39.png%3Falt%3Dmedia%26token%3D3bf4e06d-4877-454e-8f44-625c015b8e7c&width=490&dpr=4&quality=100&sign=cac60e6e&sv=2)

**Bramah Security Audit**

[](https://github.com/Squads-Protocol/squads-mpl/blob/main/Squads%20V3%20-%20OtterSec%20Audit.pdf)

![Cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F785938575-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FZK4Op7PNd2kAk4XdWjb8%252Fuploads%252F6ROYj6uguUoAyvlZ52Za%252FScreenshot%25202023-09-27%2520at%252010.00.45.png%3Falt%3Dmedia%26token%3D5c6236c4-ca67-4fe3-b47e-9df114ed31d2&width=490&dpr=4&quality=100&sign=2fbcc99a&sv=2)

**OtterSec Security Audit**

[](https://github.com/Squads-Protocol/squads-mpl/blob/main/Squads_V3_MPL_Audit_Neodyme.pdf)

![Cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F785938575-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FZK4Op7PNd2kAk4XdWjb8%252Fuploads%252Fbl8bUduiG490rLgFsJnq%252FScreenshot%25202023-09-27%2520at%252009.57.59.png%3Falt%3Dmedia%26token%3Debd68c51-6ec6-4bb8-ab7a-be9e3db4bf0a&width=490&dpr=4&quality=100&sign=c33dd729&sv=2)

**Neodyme Security Audit**

[PreviousSquads Protocol v4](https://docs.squads.so/main/security/security-audits/squads-protocol-v4)
[NextFormal Verifications](https://docs.squads.so/main/security/formal-verifications)

Last updated 11 months ago

---

# Formal Verifications | Security | Squads Docs

**What is formal verification?**

Formal verification (FV) is the process of using a formal specification to verify the correctness of a system. The goal of FV is to ensure that a program is free of bugs and meets its requirements.

As of today:

*   Squads Protocol v3 was the first program formally verified on Solana. The report made by OtterSec is accessible [here](https://docs.squads.so/main/security/formal-verifications/squads-protocol-v3)
    .
    
*   Squads Protocol v4 is formally verified by [two independent auditors](https://docs.squads.so/main/security/formal-verifications/squads-protocol-v4)
    .
    

As opposed to a security audit which specifically focuses on identifying security vulnerabilities, Formal verification is a different, mathematical approach to evaluating that a program is working as intended.

When a program is connected to the internet, there is the new risk that bugs may introduce security holes into your system. Even simple buffer overflows can be exploited by skilled attackers to compromise the integrity of a program. Formal verification is one of the most effective methods to ensure a program is free from such vulnerabilities.

OtterSec developed and released the first framework for formally verifying Solana programs in January of this year (2023). They chose Squads Protocol v3 as a case study to showcase the efficacy of this method: [https://osec.io/blog/2023-01-26-formally-verifying-solana-programs](https://osec.io/blog/2023-01-26-formally-verifying-solana-programs)

[PreviousSquads Protocol v3](https://docs.squads.so/main/security/security-audits/squads-protocol-v3)
[NextSquads Protocol v4](https://docs.squads.so/main/security/formal-verifications/squads-protocol-v4)

Last updated 1 year ago

---

# Squads Protocol v4 | Security | Squads Docs

[](https://github.com/Squads-Protocol/v4/blob/main/audits/ottersec_squads_v4_audit_2024.pdf)

![Cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F785938575-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FZK4Op7PNd2kAk4XdWjb8%252Fuploads%252F6ROYj6uguUoAyvlZ52Za%252FScreenshot%25202023-09-27%2520at%252010.00.45.png%3Falt%3Dmedia%26token%3D5c6236c4-ca67-4fe3-b47e-9df114ed31d2&width=490&dpr=4&quality=100&sign=2fbcc99a&sv=2)

**OtterSec Formal Verification**

[](https://github.com/Squads-Protocol/v4/blob/main/audits/certora_squads_v4_security_report_and_formal_verification_2024_final.pdf)

![Cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F785938575-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FZK4Op7PNd2kAk4XdWjb8%252Fuploads%252FuckoUGWmQntv0SG83mOm%252FScreenshot%25202023-09-27%2520at%252010.50.48.png%3Falt%3Dmedia%26token%3D1b559a92-e6c8-4296-a50f-c2c90e102e12&width=490&dpr=4&quality=100&sign=a58852e3&sv=2)

**Certora Formal Verification**

[PreviousFormal Verifications](https://docs.squads.so/main/security/formal-verifications)
[NextSquads Protocol v3](https://docs.squads.so/main/security/formal-verifications/squads-protocol-v3)

Last updated 8 months ago

---

# Squads Protocol v3 | Security | Squads Docs

[](https://osec.io/blog/2023-01-26-formally-verifying-solana-programs#case-study-squads-multisig)

![Cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F785938575-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FZK4Op7PNd2kAk4XdWjb8%252Fuploads%252F6ROYj6uguUoAyvlZ52Za%252FScreenshot%25202023-09-27%2520at%252010.00.45.png%3Falt%3Dmedia%26token%3D5c6236c4-ca67-4fe3-b47e-9df114ed31d2&width=490&dpr=4&quality=100&sign=2fbcc99a&sv=2)

**OtterSec Formal Verification**

[PreviousSquads Protocol v4](https://docs.squads.so/main/security/formal-verifications/squads-protocol-v4)
[NextBug bounty](https://docs.squads.so/main/security/bug-bounty)

Last updated 11 months ago

---

# Squads Protocol v4 | Security | Squads Docs

[](https://github.com/Squads-Protocol/v4/blob/main/audits/trail_of_bits_squads_v4_security_audit.pdf)

![Cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F785938575-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FZK4Op7PNd2kAk4XdWjb8%252Fuploads%252FlyGuKUydsJ1L2tqLnX7v%252FScreenshot%25202023-09-27%2520at%252010.09.43.png%3Falt%3Dmedia%26token%3Da0b77ebb-e3cb-4330-889d-7d2927db764c&width=490&dpr=4&quality=100&sign=a8dcf2bc&sv=2)

**Trail of Bits Security Audit** **2023**

[](https://github.com/Squads-Protocol/v4/blob/main/audits/neodyme_squads_v4_report.pdf)

![Cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F785938575-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FZK4Op7PNd2kAk4XdWjb8%252Fuploads%252Fbl8bUduiG490rLgFsJnq%252FScreenshot%25202023-09-27%2520at%252009.57.59.png%3Falt%3Dmedia%26token%3Debd68c51-6ec6-4bb8-ab7a-be9e3db4bf0a&width=490&dpr=4&quality=100&sign=c33dd729&sv=2)

**Neodyme Security Audit 2023**

[](https://github.com/Squads-Protocol/v4/blob/main/audits/ottersec_squads_v4_audit.pdf)

![Cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F785938575-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FZK4Op7PNd2kAk4XdWjb8%252Fuploads%252F6ROYj6uguUoAyvlZ52Za%252FScreenshot%25202023-09-27%2520at%252010.00.45.png%3Falt%3Dmedia%26token%3D5c6236c4-ca67-4fe3-b47e-9df114ed31d2&width=490&dpr=4&quality=100&sign=2fbcc99a&sv=2)

**OtterSec Security Audit 2023**

[](https://github.com/Squads-Protocol/v4/blob/main/audits/certora_squads_v4_security_report_and_formal_verification.pdf)

![Cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F785938575-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FZK4Op7PNd2kAk4XdWjb8%252Fuploads%252FuckoUGWmQntv0SG83mOm%252FScreenshot%25202023-09-27%2520at%252010.50.48.png%3Falt%3Dmedia%26token%3D1b559a92-e6c8-4296-a50f-c2c90e102e12&width=490&dpr=4&quality=100&sign=a58852e3&sv=2)

**Certora Security Audit Oct 2023**

[](https://github.com/Squads-Protocol/v4/blob/main/audits/certora_squads_v4_security_report_and_formal_verification_2024.pdf)

![Cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F785938575-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FZK4Op7PNd2kAk4XdWjb8%252Fuploads%252FuckoUGWmQntv0SG83mOm%252FScreenshot%25202023-09-27%2520at%252010.50.48.png%3Falt%3Dmedia%26token%3D1b559a92-e6c8-4296-a50f-c2c90e102e12&width=490&dpr=4&quality=100&sign=a58852e3&sv=2)

**Certora Security Audit Dec 2023**

[](https://github.com/Squads-Protocol/v4/blob/main/audits/neodyme_squads_v4_report_2024.pdf)

![Cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F785938575-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FZK4Op7PNd2kAk4XdWjb8%252Fuploads%252Fbl8bUduiG490rLgFsJnq%252FScreenshot%25202023-09-27%2520at%252009.57.59.png%3Falt%3Dmedia%26token%3Debd68c51-6ec6-4bb8-ab7a-be9e3db4bf0a&width=490&dpr=4&quality=100&sign=c33dd729&sv=2)

**Neodyme Security Audit 2024**

[](https://github.com/Squads-Protocol/v4/blob/main/audits/ottersec_squads_v4_audit_2024.pdf)

![Cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F785938575-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FZK4Op7PNd2kAk4XdWjb8%252Fuploads%252F6ROYj6uguUoAyvlZ52Za%252FScreenshot%25202023-09-27%2520at%252010.00.45.png%3Falt%3Dmedia%26token%3D5c6236c4-ca67-4fe3-b47e-9df114ed31d2&width=490&dpr=4&quality=100&sign=2fbcc99a&sv=2)

**OtterSec Security Audit 2024**

[PreviousSecurity Audits](https://docs.squads.so/main/security/security-audits)
[NextSquads Protocol v3](https://docs.squads.so/main/security/security-audits/squads-protocol-v3)

Last updated 11 months ago

---

# Bug bounty | Security | Squads Docs

1.  Reporting security problems
    
2.  Incident response process
    
3.  Security bug bounties
    

[](https://docs.squads.so/main/security/bug-bounty#reporting-security-problems)

Reporting security problems


----------------------------------------------------------------------------------------------------------------

DO NOT CREATE AN ISSUE to report a security problem. Instead, please send an email to **[\[email protected\]](https://docs.squads.so/cdn-cgi/l/email-protection)
** and provide your GitHub username so we can add you to a new draft security advisory for further discussion.

For security reasons, we do not accept vulnerability disclosures presently via email, nor do we accept attachments when provided via email for vulnerability disclosures.

We suggest that you ensure that multi-factor authentication is enabled on your account prior to submitting.

[](https://docs.squads.so/main/security/bug-bounty#incident-response-process)

**Incident response process**


----------------------------------------------------------------------------------------------------------------

In case an incident is discovered or reported, the following process will be followed to contain, respond and remediate:

### 

[](https://docs.squads.so/main/security/bug-bounty#id-1.-establish-a-new-draft-security-advisory)

**1\.** Establish a new draft security advisory

In response to an email to **[\[email protected\]](https://docs.squads.so/cdn-cgi/l/email-protection)
**, a member of the Squads team will:

*   create a new draft security advisory for the incident at
    
    *   [Squads-Protocol/squads-mpl](https://github.com/Squads-Protocol/squads-mpl)
         if the security vulnerability has been found in the Squads Protocol v3 program,
        
    *   or at [Squads-Protocol/v4](https://github.com/Squads-Protocol/v4)
         if it has been found in the Squads Protocol v4 program.
        
    
*   add the reporter's github user and the squads-protocol/security-incident-response-team group to the draft security advisory
    
*   create a private fork of the repository (grey button towards the bottom of the page)
    
*   respond to the reporter by email, sharing a link to the draft security advisory.
    

If the advisory is the result of an audit finding, a similar but slightly modified process is followed:

*   follow the same process as above but add the auditor's GitHub username and begin the title with "\[Audit\]".
    

### 

[](https://docs.squads.so/main/security/bug-bounty#id-2.-triage)

2\. Triage

Within the draft security advisory, the Squads protocol team and the reporter will discuss and determine the severity of the issue. The Squads Protocol team will ultimately be the determining party for any aspects related to the severity of the issue (and any associated bounty).

If necessary, members of the squads-protocol/security-incident-response-team group may add other GitHub users to the advisory to assist with triage.

In the event of a non-critical advisory, the Squads team will work to communicate as broadly where possible with relevant stakeholders and interested parties.

### 

[](https://docs.squads.so/main/security/bug-bounty#id-3.-prepare-fixes)

3\. Prepare fixes

For the affected branches prepare a fix for the issue and push them to the corresponding branch in the private repository associated with the draft security advisory.

Normal CI procedures will not be present within the private repository so you must build from source and manually verify fixes.

Code review from the reporter is ideal, as well as from multiple members of the Squads development team.

### 

[](https://docs.squads.so/main/security/bug-bounty#id-4.-ship-the-patch)

4\. Ship the patch

Once the fix is accepted, a member of the squads-protocol/security-incident-response-team group should prepare a single patch file for each affected branch.

The commit title for the patch should only contain the advisory id, and not disclose any further details about the incident.

### 

[](https://docs.squads.so/main/security/bug-bounty#id-5.-public-disclosure-and-release)

**5\. Public disclosure and release**

Once the fix has been deployed, the patches from the security advisory may be merged into the main source repository. At this time, more broad public disclosure may occur via the official Squads Twitter account and other official mediums of communication.

A new official release for each affected branch should be shipped and upgraded to as quickly as possible.

### 

[](https://docs.squads.so/main/security/bug-bounty#id-6.-security-advisory-bounty-accounting-and-cleanup)

**6\. Security advisory bounty accounting and cleanup**

If this issue is eligible for a bounty, prefix the title of the security advisory with one of the following, depending on the severity:

*   being able to steal funds
    
*   being able to freeze funds or render them inaccessible by their owners
    
*   being able to perform replay attacks on the same chain
    
*   being able to change Squad settings or module settings without consent of owners
    

Confirm with the reporter that they agree with the severity assessment, and discuss as required to reach a conclusion.

[](https://docs.squads.so/main/security/bug-bounty#security-bug-bounties)

**Security bug bounties**


--------------------------------------------------------------------------------------------------------

We offer bounties for critical security issues. Please see below for more details. Either a demonstration or a valid bug report is all that's necessary to submit a bug bounty.

A patch to fix the issue isn't required.

#### 

[](https://docs.squads.so/main/security/bug-bounty#ability-to-steal-funds)

Ability to Steal Funds

$300,000 USD in locked SOL tokens (locked for 12 months)

*   theft of funds without users signature from any account
    
*   theft of funds without users interaction with the Multisig program
    
*   theft of funds that requires users signature - creating a Multisig program that drains funds.
    

#### 

[](https://docs.squads.so/main/security/bug-bounty#loss-of-availability-ability-to-freeze-funds)

Loss of Availability / Ability to Freeze Funds

$200,000 USD in locked SOL tokens (locked for 12 months):

*   Ability to freeze a User’s ability to claim funds from a Multisig
    

#### 

[](https://docs.squads.so/main/security/bug-bounty#replay-attacks)

Replay Attacks

$25,000 USD in locked SOL tokens (locked for 12 months):

*   Ability to replay a previously executed transaction involving a Squads Multisig
    

#### 

[](https://docs.squads.so/main/security/bug-bounty#settings-modifications)

Settings Modifications

$10,000 USD in locked SOL tokens (locked for 12 months):

*   Modification of any Multisig or module settings without proper authorization by the owners of the Multisig
    

### 

[](https://docs.squads.so/main/security/bug-bounty#in-scope)

In Scope

These are the two on-chain programs in scope for the bug bounty:

*   Squads Protocol v4 on-chain program ([SQDS4ep65T869zMMBKyuUq6aD6EgTu8psMjkvj52pCf](https://explorer.solana.com/address/SQDS4ep65T869zMMBKyuUq6aD6EgTu8psMjkvj52pCf)
    )
    
*   Squads Protocol v3 on-chain program ([SMPLecH534NA9acpos4G6x7uf3LWbCAwZQE9e8ZekMu](https://explorer.solana.com/address/SQDS4ep65T869zMMBKyuUq6aD6EgTu8psMjkvj52pCf)
    )
    

### 

[](https://docs.squads.so/main/security/bug-bounty#out-of-scope)

Out of Scope

The following components are out of scope for the bounty program:

*   any encrypted credentials, auth tokens, etc. checked into the repo
    
*   bugs in dependencies, please take them upstream!
    
*   attacks that require social engineering
    
*   any files, modules or libraries other than the ones mentioned above
    
*   any points listed as an already known weaknesses
    
*   any points listed in the audit reports
    
*   any points fixed in a newer version.
    

### 

[](https://docs.squads.so/main/security/bug-bounty#eligibility)

Eligibility

The participant submitting the bug report shall follow the process outlined within this document.

Multiple submissions for the same class of exploit are still eligible for compensation, though may be compensated at a lower rate, however these will be assessed on a case-by-case basis.

Participants located in OFAC sanctioned countries may not participate in the bug bounty program at this time.

### 

[](https://docs.squads.so/main/security/bug-bounty#duplicate-reports)

Duplicate reports

Compensation for duplicative reports will be split among reporters with first to report taking priority using the following equation:

`R: total reports`

`ri: report priority`

`bi: bounty share`

`bi = 2 ^ (R - ri) / ((2^R) - 1)`

### 

[](https://docs.squads.so/main/security/bug-bounty#payment-of-bug-bounties)

Payment of Bug Bounties

Bounties are paid out NET and are reviewed on a rolling basis. We try to respond to every submission within 24 hours, but some may take longer as we assess relevance and impact.

### 

[](https://docs.squads.so/main/security/bug-bounty#responsible-disclosure-policy)

Responsible Disclosure Policy

If you comply with the policies below when reporting a security issue to us, we will not undergo legal action or a law enforcement investigation against you in response to your report.

We ask that:

*   You give us reasonable time to investigate and mitigate an issue you report before making public any information about the report or sharing such information with others.
    
*   You make a good faith effort to avoid security violations and disruptions to others, including (but not limited to) destruction of data and interruption or degradation of our services.
    
*   You do not exploit a security issue you discover for any reason. This includes demonstrating additional risk, such as an attempted compromise of sensitive company data or probing for additional issues.
    
*   You have not violated any other applicable laws or regulations.
    
*   You are not currently subject to any U.S. sanctions administered by the Office of Foreign Assets Control of the U.S. Department of the Treasury (“OFAC”).
    

[PreviousSquads Protocol v3](https://docs.squads.so/main/security/formal-verifications/squads-protocol-v3)

Last updated 2 years ago

---

# Instructions | Development | Squads Docs

[Create Multisig](https://docs.squads.so/main/development/typescript/instructions/create-multisig)
[Create Config Transaction](https://docs.squads.so/main/development/typescript/instructions/create-config-transaction)
[Create Vault Transaction](https://docs.squads.so/main/development/typescript/instructions/create-vault-transaction)
[Create Proposal](https://docs.squads.so/main/development/typescript/instructions/create-proposal)
[Approve Proposal](https://docs.squads.so/main/development/typescript/instructions/approve-proposal)
[Reject Proposal](https://docs.squads.so/main/development/typescript/instructions/reject-proposal)
[Cancel Proposal](https://docs.squads.so/main/development/typescript/instructions/cancel-proposal)
[Execute Config Transaction](https://docs.squads.so/main/development/typescript/instructions/execute-config-transaction)
[Execute Vault Transaction](https://docs.squads.so/main/development/typescript/instructions/execute-vault-transaction)
[Create Batch](https://docs.squads.so/main/development/typescript/instructions/create-batch)
[Add To Batch](https://docs.squads.so/main/development/typescript/instructions/add-to-batch)
[Close Vault Transaction Account](https://docs.squads.so/main/development/typescript/instructions/close-vault-transaction-account)
[Controlled Multisig Instructions](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions)

[PreviousOverview](https://docs.squads.so/main/development/typescript/overview)
[NextCreate Multisig](https://docs.squads.so/main/development/typescript/instructions/create-multisig)

Last updated 1 year ago

---

# Use Cases | Development | Squads Docs

Squads is a powerful primitive that enables a variety of use-cases related to self-custody and account abstraction. Here are few of the major use-cases for Squads' tools:

### 

[](https://docs.squads.so/main/development/introduction/use-cases#configurable-app-vaults)

**Configurable App Vaults**

Use Squads to custody funds associated with your app, and allow various stakeholders to have control over the flow of these funds. An example of this would be a crowdfunding app, where funds raised are custodied in Squads, with the fundraiser admins and members of the app team as members.

### 

[](https://docs.squads.so/main/development/introduction/use-cases#custom-user-interfaces)

**Custom User Interfaces**

Use the Squads v4 SDK to create a custom UI, built to your liking for your Squad. This allows for a bespoke smart account experience, and less dependency on Squads' official services. For reference, check out our [public UI](https://github.com/Squads-Protocol/squads-v4-public-ui)
.

### 

[](https://docs.squads.so/main/development/introduction/use-cases#squads-blinks)

Squads Blinks

Build custom Solana actions and blockchain links (blinks) associated with a Squad that are shareable on a variety of websites like X.

[PreviousWhat is Squads Protocol](https://docs.squads.so/main/development)
[NextQuickstart](https://docs.squads.so/main/development/introduction/quickstart)

Last updated 1 year ago

---

# Quickstart | Development | Squads Docs

[](https://docs.squads.so/main/development/introduction/quickstart#set-up-your-workspace-1-minute)

Set up your workspace (1 minute)


----------------------------------------------------------------------------------------------------------------------------------------

**Important note**: You can find the code for this quickstart guide [here](https://github.com/Squads-Protocol/v4-examples/blob/main/typescript/main.ts)
.

Let's set up a new Typescript project. First, create a new directory.

Copy

    mkdir squads_quickstart

Copy

    cd squads_quickstart

Now, create a new file named `tsconfig.json`

Copy

    {
      "compilerOptions": {
        "module": "commonjs",
        "target": "es6",
        "esModuleInterop": true
      }
    }

Add a `package.json` file and add this content

Copy

    {
      "scripts": {
        "test": "npx mocha -r ts-node/register 'main.ts' --timeout 10000"
      },
      "dependencies": {
        "@solana/web3.js": "^1.73.0",
        "@sqds/multisig": "^2.1.3"
      },
      "devDependencies": {
        "@types/chai": "^4.3.3",
        "@types/mocha": "^10.0.6",
        "chai": "^4.3.6",
        "mocha": "^10.3.0",
        "ts-mocha": "^10.0.0",
        "typescript": "^4.8.3"
      }
    }

Here, the main takeaway is that we are going to use the `@sqds/multisig` package.

Last but not least, create a `main.ts` file at the same location, and add this code:

Copy

    import * as multisig from "@sqds/multisig";
    import {
      Connection,
      Keypair,
      LAMPORTS_PER_SOL,
      SystemProgram,
      TransactionMessage,
      clusterApiUrl,
    } from "@solana/web3.js";
    
    const { Permission, Permissions } = multisig.types;
    
    // Use 'https://api.devnet.solana.com' if there are struggles running locally
    const connection = new Connection("http://localhost:8899", "confirmed");

[](https://docs.squads.so/main/development/introduction/quickstart#lets-get-to-the-code-8-minutes)

Let's get to the code (8 minutes)


-----------------------------------------------------------------------------------------------------------------------------------------

### 

[](https://docs.squads.so/main/development/introduction/quickstart#create-a-multisig-2-minutes)

Create a multisig (2 minutes)

Let's set up a testing flow in which we're going to create a multisig, propose a new transaction, vote on that transaction and execute it.

First, let's add our first step: Setting up the multisig members and creating the multisig.

Copy

    describe("Interacting with the Squads V4 SDK", () => {
      const creator = Keypair.generate();
      const secondMember = Keypair.generate();
      before(async () => {
        const airdropSignature = await connection.requestAirdrop(
          creator.publicKey,
          1 * LAMPORTS_PER_SOL
        );
        await connection.confirmTransaction(airdropSignature);
      });
    
      const createKey = Keypair.generate();
    
      // Derive the multisig account PDA
      const [multisigPda] = multisig.getMultisigPda({
        createKey: createKey.publicKey,
      });
    
      it("Create a new multisig", async () => {
        const programConfigPda = multisig.getProgramConfigPda({})[0];
    
        console.log("Program Config PDA: ", programConfigPda.toBase58());
    
        const programConfig =
          await multisig.accounts.ProgramConfig.fromAccountAddress(
            connection,
            programConfigPda
          );
    
        const configTreasury = programConfig.treasury;
    
        // Create the multisig
        const signature = await multisig.rpc.multisigCreateV2({
          connection,
          // One time random Key
          createKey,
          // The creator & fee payer
          creator,
          multisigPda,
          configAuthority: null,
          timeLock: 0,
          members: [\
            {\
              key: creator.publicKey,\
              permissions: Permissions.all(),\
            },\
            {\
              key: secondMember.publicKey,\
              // This permission means that the user will only be able to vote on transactions\
              permissions: Permissions.fromPermissions([Permission.Vote]),\
            },\
          ],
          // This means that there needs to be 2 votes for a transaction proposal to be approved
          threshold: 2,
          rentCollector: null,
          treasury: configTreasury,
          sendOptions: { skipPreflight: true },
        });
        await connection.confirmTransaction(signature);
        console.log("Multisig created: ", signature);
      });

### 

[](https://docs.squads.so/main/development/introduction/quickstart#create-transaction-proposal-2-minutes)

Create transaction proposal (2 minutes)

Now, let's create a transaction proposal. We want the multisig to send 0.1 SOL to the creator. For purposes of this tutorial, we first have to send that amount to the multisig, and can then create a message containing the instruction that needs to be executed.

Copy

      it("Create a transaction proposal", async () => {
        const [vaultPda] = multisig.getVaultPda({
          multisigPda,
          index: 0,
        });
        const instruction = SystemProgram.transfer({
          // The transfer is being signed from the Squads Vault, that is why we use the VaultPda
          fromPubkey: vaultPda,
          toPubkey: creator.publicKey,
          lamports: 1 * LAMPORTS_PER_SOL,
        });
        // This message contains the instructions that the transaction is going to execute
        const transferMessage = new TransactionMessage({
          payerKey: vaultPda,
          recentBlockhash: (await connection.getLatestBlockhash()).blockhash,
          instructions: [instruction],
        });
    
        // Get the current multisig transaction index
        const multisigInfo = await multisig.accounts.Multisig.fromAccountAddress(
          connection,
          multisigPda
        );
    
        const currentTransactionIndex = Number(multisigInfo.transactionIndex);
    
        const newTransactionIndex = BigInt(currentTransactionIndex + 1);
    
        const signature1 = await multisig.rpc.vaultTransactionCreate({
          connection,
          feePayer: creator,
          multisigPda,
          transactionIndex: newTransactionIndex,
          creator: creator.publicKey,
          vaultIndex: 0,
          ephemeralSigners: 0,
          transactionMessage: transferMessage,
          memo: "Transfer 0.1 SOL to creator",
        });
    
        await connection.confirmTransaction(signature1);
    
        console.log("Transaction created: ", signature1);
    
        const signature2 = await multisig.rpc.proposalCreate({
          connection,
          feePayer: creator,
          multisigPda,
          transactionIndex: newTransactionIndex,
          creator,
        });
    
        await connection.confirmTransaction(signature2);
    
        console.log("Transaction proposal created: ", signature2);
      });

### 

[](https://docs.squads.so/main/development/introduction/quickstart#vote-on-the-transaction-proposal-2-minutes)

Vote on the transaction proposal (2 minutes)

Let's now vote on the transaction proposal we just made using the two Keypairs we created at the start of this tutorial: creator and secondMember.

Copy

      it("Vote on the created proposal", async () => {
        const transactionIndex =
          await multisig.accounts.Multisig.fromAccountAddress(
            connection,
            multisigPda
          ).then((info) => Number(info.transactionIndex));
    
        const signature1 = await multisig.rpc.proposalApprove({
          connection,
          feePayer: creator,
          multisigPda,
          transactionIndex: BigInt(transactionIndex),
          member: creator,
        });
    
        await connection.confirmTransaction(signature1);
    
        const signature2 = await multisig.rpc.proposalApprove({
          connection,
          feePayer: creator,
          multisigPda,
          transactionIndex: BigInt(transactionIndex),
          member: secondMember,
        });
    
        await connection.confirmTransaction(signature2);
      });

### 

[](https://docs.squads.so/main/development/introduction/quickstart#execute-the-transaction-2-minutes)

Execute the transaction (2 minutes)

Now the most important part, actually executing that transaction we proposed.

Copy

      it("Execute the proposal", async () => {
        const transactionIndex =
          await multisig.accounts.Multisig.fromAccountAddress(
            connection,
            multisigPda
          ).then((info) => Number(info.transactionIndex));
    
        const [proposalPda] = multisig.getProposalPda({
          multisigPda,
          transactionIndex: BigInt(transactionIndex),
        });
        const signature = await multisig.rpc.vaultTransactionExecute({
          connection,
          feePayer: creator,
          multisigPda,
          transactionIndex: BigInt(transactionIndex),
          member: creator.publicKey,
          signers: [creator],
          sendOptions: { skipPreflight: true },
        });
    
        await connection.confirmTransaction(signature);
        console.log("Transaction executed: ", signature);
      });
      
    // Don't forget to close the describe block here
    });

[](https://docs.squads.so/main/development/introduction/quickstart#start-a-local-validator-1-minute)

Start a local validator (1 minute)


--------------------------------------------------------------------------------------------------------------------------------------------

Now that you have a completed flow, let's actually execute these transactions on chain. For the purpose of this tutorial, we are going to do so on a local Solana instance.

If you do not yet have the Solana CLI installed, please do so by reading the following [guide](https://docs.solana.com/cli/install-solana-cli-tools)
.

Now, start up a local validator with the Squads V4 program preloaded.

**Note**: You will also have to clone the program config account from mainnet.

Copy

    solana-test-validator --url m --clone-upgradeable-program SQDS4ep65T869zMMBKyuUq6aD6EgTu8psMjkvj52pCf -c BSTq9w3kZwNwpBXJEvTZz2G9ZTNyKBvoSeXMvwb4cNZr -c Fy3YMJCvwbAXUgUM5b91ucUVA3jYzwWLHL3MwBqKsh8n

[](https://docs.squads.so/main/development/introduction/quickstart#set-your-environment-to-devnet-optional-1-minute)

Set Your Environment to Devnet (Optional, 1 minute)


-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------

If you run into issues creating a local validator and cloning the necessary accounts, you can optionally use Solana's devnet cluster. This is a useful alternative because all needed accounts will already be available.

To switch to devnet, edit the `connection` variable you defined earlier in the guide:

Copy

    const connection = new Connection("http://localhost:8899", "confirmed");

When using devnet, you may run into rate limit issues when attempting to request an airdrop. To circumvent this, we can use the keypair from our Solana CLI, and manually fund any keypairs we create. To do this, we can refactor the beginning of our script to accomplish this:

Copy

    // Add these two dependencies
    import path from "path";
    import dotenv from "dotenv";
    
    dotenv.config();
    
    // Add this before you define `describe`
    const keyFileContents = JSON.parse(
      readFileSync(path.join(process.env.HOME, ".config/solana/id.json")).toString()
    );
    
    const creator = Keypair.fromSecretKey(new Uint8Array(keyFileContents));
    const secondMember = Keypair.generate();

and then add this snippet at the beginning of your first test:

Copy

    try {
        // Attempt an airdrop
        await connection.requestAirdrop(
          secondMember.publicKey,
          1 * LAMPORTS_PER_SOL
        );
    } catch (e) {
        // If it fails due to rate limits, send from the filesystem keypair
        console.log("airdrop failed");
    
        const tx = new VersionedTransaction(
          new TransactionMessage({
            payerKey: creator.publicKey,
            recentBlockhash: await (
              await connection.getLatestBlockhash()
            ).blockhash,
            instructions: [\
              SystemProgram.transfer({\
                fromPubkey: creator.publicKey,\
                toPubkey: secondMember.publicKey,\
                lamports: 1_000_000,\
              }),\
            ],
          }).compileToV0Message()
        );
    
        tx.sign([creator]);
    
        console.log("✨ Sending SOL...");
        await connection.sendTransaction(tx);
        console.log("✅ SOL sent.");
    }

[](https://docs.squads.so/main/development/introduction/quickstart#execute-the-script)

Execute the script


--------------------------------------------------------------------------------------------------------------

Okay, let's execute the script and see what happens.

Copy

    yarn test

If you are encountering any issues here, try using another version of Node.js (above 20.xx). Additionally, switching SDK versions (to `2.1.1` or `2.1.0`) may alleviate any ESM resoultion issues.

If you get a "fetch failed" error, make sure your local validator is running.

[](https://docs.squads.so/main/development/introduction/quickstart#visualize-your-transactions)

Visualize your transactions


--------------------------------------------------------------------------------------------------------------------------------

Once the tests have passed, you can go to the [Solana Explorer](https://explorer.solana.com/?cluster=custom&customUrl=http%3A%2F%2Flocalhost%3A8899)
 and visualize your transactions by pasting their signature in the search bar and modifying the cluster endpoint to the one you want (mainnet, devnet, localnet...).

### 

[](https://docs.squads.so/main/development/introduction/quickstart#what-can-i-do-from-here)

What can I do from here?

[Read more about development on Squads](https://docs.squads.so/main/development/typescript/overview)

[Join the Squads Discord](https://discord.com/invite/squadsprotocol)

[PreviousUse Cases](https://docs.squads.so/main/development/introduction/use-cases)
[NextOverview](https://docs.squads.so/main/development/typescript/overview)

Last updated 1 year ago

---

# Multisig | Development | Squads Docs

The Multisig account serves as the global config for your Squad. This stores all data related to membership, permissions, thresholds, and more. It will be required for every instruction method and account derivation with the SDK.

The account address itself is derived via a createKey, which is a public key used as a seed. It is recommended to generate a one-time keypair for the createKey to avoid collisions, and save the public key, or the resulting multisig address for later use.

[](https://docs.squads.so/main/development/typescript/accounts/multisig#getting-the-multisig-account)

Getting the Multisig account


---------------------------------------------------------------------------------------------------------------------------------------

Copy

    import * as multisig from "@sqds/multisig";
    import { Keypair } from "@solana/web3.js";
    
    const { Multisig } = multisig.accounts;
    
    async function main() {
        // One-time keypair, used for derivation 
        const createKey = Keypair.generate();
    
        const [multisigPda] = multisig.getMultisigPda({
            createKey.publicKey,
        });
        
        const multisigAccount = await Multisig.fromAccountAddress(
            connection,
            multisigPda
        );
       
        console.log(multisigAccount);
    }

### 

[](https://docs.squads.so/main/development/typescript/accounts/multisig#notes)

Notes:

*   DO NOT send funds to this account. They will be lost if you do.
    
*   The Multisig account handles global config for the entirety of the Squad
    
*   The account is derived via a `createKey`, which is one of the singers for its creation.
    
*   See the [reference](https://docs.squads.so/main/development/reference/accounts#multisig)
     for more information on account structure and seeds.
    

[PreviousAccounts](https://docs.squads.so/main/development/typescript/accounts)
[NextVault](https://docs.squads.so/main/development/typescript/accounts/vault)

Last updated 1 year ago

---

# Accounts | Development | Squads Docs

[Multisig](https://docs.squads.so/main/development/typescript/accounts/multisig)
[Vault](https://docs.squads.so/main/development/typescript/accounts/vault)
[Transactions](https://docs.squads.so/main/development/typescript/accounts/transactions)
[Proposal](https://docs.squads.so/main/development/typescript/accounts/proposal)
[Batch](https://docs.squads.so/main/development/typescript/accounts/batch)

[PreviousRemove Spending Limit](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions/remove-spending-limit)
[NextMultisig](https://docs.squads.so/main/development/typescript/accounts/multisig)

---

# Vault | Development | Squads Docs

Vaults are the accounts that store assets and handle execution of [Vault Transactions](https://docs.squads.so/main/development/typescript/accounts/transactions#vault-transactions)
. They function differently from any other account associated with Squads, not holding any data directly.

[](https://docs.squads.so/main/development/typescript/accounts/vault#understanding-vaults)

Understanding Vaults


--------------------------------------------------------------------------------------------------------------------

Vaults are derived via a `vaultIndex`, which allows you select a specific vault by chronological number. Using this index will allow the SDK, and associated instructions to get the correct vault to target.

When you lookup a newly derived vault address on an explorer, it will show as an uninitialized account. This is because Solana requires any initialized account to have a non-zero SOL balance. Because of this, the account is never "created" by any instruction, only marked initialized as the user adds SOL.

When you create a new wallet with something like Phantom, that key will initially show as "uninitialized" on an explorer until you deposit funds. Same principle with Vaults!

[](https://docs.squads.so/main/development/typescript/accounts/vault#getting-the-vault-account)

Getting the Vault account


------------------------------------------------------------------------------------------------------------------------------

Copy

    import * as multisig from "@sqds/multisig";
    import { Keypair } from "@solana/web3.js";
    
    const { Multisig } = multisig.accounts;
    
    async function main() {
        // One-time keypair, used for derivation 
        const createKey = Keypair.generate();
    
        const [multisigPda] = multisig.getMultisigPda({
            createKey.publicKey,
        });
        
        const [vaultPda] = multisig.getVaultPda({
            multisigPda,
            index: 0
        });
       
        console.log(vaultPda);
    }

### 

[](https://docs.squads.so/main/development/typescript/accounts/vault#notes)

Notes:

*   Vault accounts hold assets, and handle the execution of Vault Transactions
    
*   Vaults hold no data, and are derived via an index
    
*   They are not "created" via any instruction, and will appear as "uninitialized" on an explorer until SOL is deposited
    

[PreviousMultisig](https://docs.squads.so/main/development/typescript/accounts/multisig)
[NextTransactions](https://docs.squads.so/main/development/typescript/accounts/transactions)

Last updated 1 year ago

---

# Create Multisig | Development | Squads Docs

Be sure to use `multisigCreateV2`, rather than the deprecated `multisigCreate`

This instruction will create a Multisig account with the necessary fields. This instruction requires that both the `creator` of the multisig, and the `createKey` be signers.

[](https://docs.squads.so/main/development/typescript/instructions/create-multisig#example)

Example


--------------------------------------------------------------------------------------------------------

Copy

    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)
    }

### 

[](https://docs.squads.so/main/development/typescript/instructions/create-multisig#notes)

Notes

*   Must specify permissions upfront for each member
    
*   Only specify a `configAuthority` if you want one admin key to be able to override all config
    
*   `createKey` must be a signer if using methods other than `.rpc`
    

[PreviousInstructions](https://docs.squads.so/main/development/typescript/instructions)
[NextCreate Config Transaction](https://docs.squads.so/main/development/typescript/instructions/create-config-transaction)

Last updated 1 year ago

---

# Overview | Development | Squads Docs

This section is made for developers wanting to integrate Squads Protocol into their own projects by interacting with v4.

It is structured as straightforward as possible with two sections, with the first being how to read data from the v4 program and the second being how to interact with it. In each section you will be able to find a detailed list of every account and instruction included in the Squads v4 SDK and Crate.

### 

[](https://docs.squads.so/main/development/typescript/overview#program-id)

Program ID

The Squads V4 program is deployed on the Solana mainnet-beta cluster.

Copy

    SQDS4ep65T869zMMBKyuUq6aD6EgTu8psMjkvj52pCf

### 

[](https://docs.squads.so/main/development/typescript/overview#interacting)

Interacting

Here are different ways to use the SDK:

*   `multisig.instructions`: This will return selected instructions, to be processed and sent by your client.
    
*   `multisig.rpc` : This will build selected instructions, put it in a transaction, and send immediately.
    
*   `multisig.transactions`: This will create selected instructions, and return a VersionedTransaction with the instruction added.
    
*   `multisig.accounts`: Various account types within the Squads program, and utility methods for working with them
    
*   `multisig.utils`: Provides helper functions for working with Squads
    
*   `multisig.types`: Various types related to Squads
    

### 

[](https://docs.squads.so/main/development/typescript/overview#table-of-contents)

Table of Contents

Here is a list of the different categories this section contains.

#### 

[](https://docs.squads.so/main/development/typescript/overview#reading-data-from-squads-accounts)

Reading data from Squads (Accounts)

*   [Read Multisig data](https://docs.squads.so/main/development/typescript/accounts/multisig)
    
*   [Read Transaction data](https://docs.squads.so/main/development/typescript/accounts/transactions)
    
*   [Read Proposal data](https://docs.squads.so/main/development/typescript/accounts/proposal)
    

#### 

[](https://docs.squads.so/main/development/typescript/overview#interact-with-the-squads-program-instructions)

Interact with the Squads program (Instructions)

*   [Create Multisig](https://docs.squads.so/main/development/typescript/instructions/create-multisig)
    
*   [Add Member](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions/add-member)
    
*   [Add Spending Limit](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions/add-spending-limit)
    
*   [Remove Spending Limit](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions/remove-spending-limit)
    
*   [Create Vault Transaction](https://docs.squads.so/main/development/typescript/instructions/create-vault-transaction)
    
*   [Create Proposal](https://docs.squads.so/main/development/typescript/instructions/create-proposal)
    
*   [Approve Transaction](https://docs.squads.so/main/development/typescript/instructions/approve-proposal)
    
*   [Reject Proposal](https://docs.squads.so/main/development/typescript/instructions/reject-proposal)
    
*   [Cancel Proposal](https://docs.squads.so/main/development/typescript/instructions/cancel-proposal)
    
*   [Execute Transaction](https://docs.squads.so/main/development/typescript/instructions/execute-vault-transaction)
    

[PreviousQuickstart](https://docs.squads.so/main/development/introduction/quickstart)
[NextInstructions](https://docs.squads.so/main/development/typescript/instructions)

Last updated 1 year ago

---

# Reject Proposal | Development | Squads Docs

Opposite of approval, any qualifying member key with "Voter" permissions can cast a rejection on proposal. Additionally, a rejection will fail if the proposal is stale (Proposal `transactionIndex` < Multisig `staleTransactionIndex`).

[](https://docs.squads.so/main/development/typescript/instructions/reject-proposal#example)

Example


--------------------------------------------------------------------------------------------------------

Copy

    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.proposalReject({
          multisigPda,
          transactionIndex,
          // Member must have "Voter" permissions
          member: member,
        });
    }

### 

[](https://docs.squads.so/main/development/typescript/instructions/reject-proposal#notes)

Notes

*   Rejecting members must have "Voter" permissions
    
*   A Proposal can not be rejected if the transaction index is less than the stale transaction index (see [Multisig reference](https://docs.squads.so/main/development/reference/accounts#multisig)
    )
    

[PreviousApprove Proposal](https://docs.squads.so/main/development/typescript/instructions/approve-proposal)
[NextCancel Proposal](https://docs.squads.so/main/development/typescript/instructions/cancel-proposal)

Last updated 1 year ago

---

# Controlled Multisig Instructions | Development | Squads Docs

Most multisigs are not Controlled Multisigs. To learn more, view the [reference](https://docs.squads.so/main/development/reference/controlled-multisigs)
.

There instructions below are only accessible for Squads function as Controlled Multisigs, meaning the multisig has a [Config Authority](https://docs.squads.so/main/development/reference/accounts#multisig)
.

For most multisigs, the following instructions can be achieved with a [Config Transaction](https://docs.squads.so/main/development/typescript/instructions/create-config-transaction)
.

[PreviousClose Vault Transaction Account](https://docs.squads.so/main/development/typescript/instructions/close-vault-transaction-account)
[NextAdd Member](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions/add-member)

Last updated 1 year ago

---

# Controlled Multisigs | Development | Squads Docs

Using a Controlled Multisig is not recommended for most use-cases. Please understand the tradeoffs of having a valid Config Authority before choosing to use this setup.

[](https://docs.squads.so/main/development/reference/controlled-multisigs#what-is-a-controlled-multisig)

What is a Controlled Multisig?


--------------------------------------------------------------------------------------------------------------------------------------------

To put it simply, a Controlled Multisig is a multisig with a set [Config Authority](https://docs.squads.so/main/development/reference/accounts#multisig-account-content)
. This allows the set config authority to manipulate the config of the Squad without being subject to consensus, causing the set key to essentially function as an admin.

[](https://docs.squads.so/main/development/reference/controlled-multisigs#why-use-a-config-authority)

Why use a Config Authority?


--------------------------------------------------------------------------------------------------------------------------------------

Any setups that require a single admin for config changes are suited for a Controlled Multisig. If you are an organization that requires a C-level executive to have specific config control, then a controlled multisig may be in order.

[PreviousSDKs](https://docs.squads.so/main/development/reference/sdks)
[NextVault Check](https://docs.squads.so/main/development/api/vault-check)

Last updated 1 year ago

---

# Batch | Development | Squads Docs

[PreviousProposal](https://docs.squads.so/main/development/typescript/accounts/proposal)
[NextAccounts](https://docs.squads.so/main/development/reference/accounts)

---

# Transactions | Development | Squads Docs

Transactions are split into two types, each with their own execution instructions and parameters. Both types are subject to consensus. The two types are:

*   [Vault Transactions:](https://docs.squads.so/main/development/typescript/accounts/transactions#vault-transactions)
     Store, vote, and execute on arbitrary Solana instructions
    
*   [Config Transactions](https://docs.squads.so/main/development/typescript/accounts/transactions#config-transactions)
    : Edit config in the Multisig account (members, spending limits, etc...)
    

Both types of transactions are bound to a transaction index, which denotes where the transaction is in the continuity of the multisig. This index is also used to derivation. Because of this, you can use the method below to derive the address of either account type:

### 

[](https://docs.squads.so/main/development/typescript/accounts/transactions#getting-a-transaction-address)

Getting a Transaction address

Copy

    import * as multisig from "@sqds/multisig";
    import { PublicKey } from "@solana/web3.js";
    
    async function main() {
        // Public Key of the Multisig PDA
        const multisigPda = new PublicKey("<my multisig>");
        
        // Fetch the deserialized Multisig account
        const multisigInfo = await multisig.accounts.Multisig.fromAccountAddress(
          connection,
          multisigPda
        );
    
        // Get the current transaction index
        const currentTransactionIndex = Number(multisigInfo.transactionIndex);
        const transactionIndex = BigInt(currentTransactionIndex + 1);
        // or, if this is your first transaction
        // const transactionIndex = 1n;
        
        // Can be either a VaultTransaction or ConfigTransaction
        const [transactionPda] = multisig.getTransactionPda({
            multisigPda,
            index: transactionIndex,
        });
    }

### 

[](https://docs.squads.so/main/development/typescript/accounts/transactions#vault-transactions)

Vault Transactions

This transaction type is by far the most common. Most actions you conduct via your multisig will be Vault Transactions. These take a Transaction Message containing a number of arbitrary instructions, and saves them in an account for voting and execution.

See [Create Vault Transaction](https://docs.squads.so/main/development/typescript/instructions/create-vault-transaction)
 for more information about how to create this account.

#### 

[](https://docs.squads.so/main/development/typescript/accounts/transactions#fetch-vault-transaction-info)

Fetch Vault Transaction Info

Copy

    // Fetch the deserialized account
    let transactionAccount = 
        await multisig.accounts.VaultTransaction.fromAccountAddress(
            connection,
            transactionPda
        );
          
    // Log the Vault Transaction structure
    console.log("Transaction: ", transactionAccount);

### 

[](https://docs.squads.so/main/development/typescript/accounts/transactions#config-transactions)

Config Transactions

Less common, but equally important is the config transaction, which is used to manage configurations (spending limits, members, time-locks, etc...) on your Multisig. These consist of a set of predefined actions that any given transaction can take, with some invalidating all previous transactions on execution.

See [Create Config Transaction](https://docs.squads.so/main/development/typescript/instructions/create-config-transaction)
 for more information about how to create this account.

#### 

[](https://docs.squads.so/main/development/typescript/accounts/transactions#fetch-config-transaction-info)

Fetch Config Transaction Info

Copy

    // Fetch the deserialized account
    const configTransactionAccount =
            await multisig.accounts.ConfigTransaction.fromAccountAddress(
                    connection, 
                    transactionPda
            );
            
    // Log the Config Transaction structure
    console.log("Config Transaction: ", configTransactionAccount);

### 

[](https://docs.squads.so/main/development/typescript/accounts/transactions#notes)

Notes

*   Two types of transactions: Vault Transactions, and Config Transactions
    
*   They require a proposal account to be voted on, and subsequently executed
    
*   See their [reference](https://docs.squads.so/main/development/reference/accounts#vault-transaction)
     for more information on account structure and seeds.
    

[PreviousVault](https://docs.squads.so/main/development/typescript/accounts/vault)
[NextProposal](https://docs.squads.so/main/development/typescript/accounts/proposal)

Last updated 1 year ago

---

# Close Vault Transaction Account | Development | Squads Docs

This instruction will reclaim rent from a Vault Transaction account, and close the account. This requires the transaction to be stale (`transactionIndex` < `staleTransactionIndex`), the corresponding proposal to be Cancelled, or the transaction itself be Executed.

[](https://docs.squads.so/main/development/typescript/instructions/close-vault-transaction-account#example)

Example


------------------------------------------------------------------------------------------------------------------------

Copy

    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.vaultTransactionAccountsClose({
            multisigPda,
            // This value should be the current rent collector Public Key of the Multisig.
            rentCollector: vaultPda,
            transactionIndex,
            multisig.programId,
        });
    }

### 

[](https://docs.squads.so/main/development/typescript/instructions/close-vault-transaction-account#notes)

Notes

*   Vault Transactions can be reclaimed when they are stale (`transactionIndex` < `staleTransactionIndex`), or of status Cancelled or Executed.
    
*   Reclaimed rent will be returned to the set rent collector on the Multisig account.
    

[PreviousAdd To Batch](https://docs.squads.so/main/development/typescript/instructions/add-to-batch)
[NextControlled Multisig Instructions](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions)

Last updated 1 year ago

---

# SDKs | Development | Squads Docs

Squads has 2 different SDKs, one for Typescript and one for Rust.

### 

[](https://docs.squads.so/main/development/reference/sdks#typescript)

Typescript

The Squads V4 Typescript SDK is named `@sqds/multisig` and can be found [here](https://www.npmjs.com/package/@sqds/multisig)
.

### 

[](https://docs.squads.so/main/development/reference/sdks#rust)

Rust

The Squads V4 Rust crate is named `squads-multisig` and can be found [here](https://crates.io/crates/squads-multisig)
.

[PreviousTime-locks](https://docs.squads.so/main/development/reference/time-locks)
[NextControlled Multisigs](https://docs.squads.so/main/development/reference/controlled-multisigs)

Last updated 1 year ago

---

# Create Config Transaction | Development | Squads Docs

Config Transactions are a little more complicated than the other ones, as there are multiple configuration arguments that you can supply to such a transaction.

Here are list of action types you can execute with Config Transactions, and their arguments:

*   **AddMember**
    
    *   _new\_member_ (**Member**): Key & corresponding permissions for the member you want to add.
        
    
*   **RemoveMember**
    
    *   _old\_member_ (**PublicKey**): Key of the member that you want to remove
        
    
*   **ChangeThreshold**
    
    *   _new\_threshold_ (**number**): New approval threshold that you want to enforce
        
    
*   **SetTimeLock**
    
    *   _new\_time\_lock_ (**number**): Change the `time_lock` of the multisig.
        
    
*   **AddSpendingLimit**
    
    *   _create\_key_ (**PublicKey**): Key that is used to seed the SpendingLimit PDA.
        
    *   _vault\_index_ (**number**): The index of the vault that the spending limit is for.
        
    *   _mint_ (**PublicKey**): The token mint the spending limit is for.
        
    *   _amount_ (**number**): The amount of tokens that can be spent in a period. This is respective of the mint's decimals. (i.e USDC has 6 decimals, so 1 USDC would be 1\_000\_000)
        
    *   _members_ (**PublicKey\[\]**): Members of the multisig that can use the spending limit. In case a member is removed from the multisig, the spending limit will remain existent, but unusable until deleted.
        
    *   _destinations_ (**PublicKey\[\]**): The destination addresses the spending limit is allowed to sent funds to. If empty, funds can be sent to any address.
        
    
*   **RemoveSpendingLimit**
    
    *   _spending\_limit_ (**Pubkey**): Account for the spending limit you want to remove.
        
    
*   **SetRentCollector**
    
    *   _new\_rent\_collector_ (**PublicKey | null**): Set the `rent_collector` config parameter of the multisig.
        
    

[](https://docs.squads.so/main/development/typescript/instructions/create-config-transaction#example-change-threshold)

Example (Change Threshold)


------------------------------------------------------------------------------------------------------------------------------------------------------

Copy

    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\
            }],
        }),
    }

### 

[](https://docs.squads.so/main/development/typescript/instructions/create-config-transaction#notes)

Notes

*   This is instruction is used for changing config in most multisigs (ones with no configAuthority)
    
*   Exectuing certain config transactions will invalidate other Active transactions (both config and vault type). This behavior is present with AddMember, RemoveMember, ChangeThreshold, and SetTimeLock
    
*   Multiple actions can be specified between instructions
    
*   For more information, see the [Config Transaction](https://docs.squads.so/main/development/typescript/accounts/transactions#config-transactions)
     section and [reference](https://docs.squads.so/main/development/reference/accounts#config-transaction)
    .
    

[PreviousCreate Multisig](https://docs.squads.so/main/development/typescript/instructions/create-multisig)
[NextCreate Vault Transaction](https://docs.squads.so/main/development/typescript/instructions/create-vault-transaction)

Last updated 1 year ago

---

# Approve Proposal | Development | Squads Docs

Proposals require approvals equal to the threshold for the underlying transaction to be executed. Any qualifying member key with "Voter" permissions can cast an approval on proposal. Additionally, an approval will fail if the proposal is stale (Proposal `transactionIndex` < Multisig `staleTransactionIndex`).

[](https://docs.squads.so/main/development/typescript/instructions/approve-proposal#example)

Example


---------------------------------------------------------------------------------------------------------

Copy

    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.proposalApprove({
          multisigPda,
          transactionIndex,
          // Member must have "Voter" permissions
          member: member,
        });
    }

### 

[](https://docs.squads.so/main/development/typescript/instructions/approve-proposal#notes)

Notes

*   Approving members must have "Voter" permissions
    
*   A Proposal can not be approved if the transaction index is less than the stale transaction index (see [Multisig reference](https://docs.squads.so/main/development/reference/accounts#multisig)
    )
    

[PreviousCreate Proposal](https://docs.squads.so/main/development/typescript/instructions/create-proposal)
[NextReject Proposal](https://docs.squads.so/main/development/typescript/instructions/reject-proposal)

Last updated 1 year ago

---

# Time-locks | Development | Squads Docs

A time-lock is a feature in which a transaction will be frozen for a certain period of time after reaching the ready to execute threshold.

Here is how to modify a time lock with the Squads Multisig SDK.

Copy

    await multisig.rpc.configTransactionCreate({
        connection,
        feePayer: members.proposer,
        multisigPda: autonomousMultisigPda,
        transactionIndex,
        creator: members.proposer.publicKey,
        // Set a new 1 minute time-lock
        actions: [{\
            __kind: "SetTimelock",\
            newTimeLock: 60 * 60\
        }],
    });

See the [Create a Config Transaction](https://docs.squads.so/main/development/typescript/instructions/create-config-transaction)
 guide for more insight on the accounts involved in that instruction.

[PreviousSpending Limits](https://docs.squads.so/main/development/reference/spending-limits)
[NextSDKs](https://docs.squads.so/main/development/reference/sdks)

Last updated 1 year ago

---

# Permissions | Development | Squads Docs

Permissions allow you to limit what actions specific members can take in your Squad. This is particularly useful when you want to assign different roles or responsibilities to different members. For example, you might want some members to only be able to vote on proposals, while others can initiate and execute transactions.

By assigning specific permissions, you can create a more secure and flexible Squads setup. For instance, you could have:

*   `Proposers`: Members who can initiate transactions
    
*   `Voters`: Members who can vote on proposals
    
*   `Executors`: Members who can execute transactions
    
*   `Almighty`: Members with full permissions to manage all aspects of the multisig (this is all of the above assigned to one member)
    

With the SDK, we provide a `Permissions` enum, that abstracts any of the complexities related to assigning permissions. Here's an example of how this is used with `multisigCreate:`

Copy

    import * as multisig from "@sqds/multisig";
    import { Connection, Keypair } from "@solana/web3.js";
    
    // Enums
    // "Permission" gives single permissions to aggregate in any combination
    // "Permissions" provides a method for almighty, and method to aggregate other permissions
    const { Permission, Permissions } = multisig.types;
    
    async function main() {
        /*
        See Instructions -> Create Multisig for full snippet
        */
        
        const ix = await multisig.instructions.multisigCreateV2({
            createKey: createKey.publicKey,
            creator: creator.publicKey,
            multisigPda,
            configAuthority: null,
            timeLock: 0,
            members: [{\
                    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]),\
                },\
            ],
            threshold: 2,
            rentCollector: null
        });
    }

[](https://docs.squads.so/main/development/reference/permissions#permission-mappings)

Permission Mappings


--------------------------------------------------------------------------------------------------------------

Permissions in the program are just mappings of u8 values. Stacking permissions for a single member requires adding up the combination of the permission mappings. Each permission maps to the following value:

*   **Proposer** - 1
    
*   **Voter** - 2
    
*   **Executor** - 4
    
*   **Almighty** (combination of all) - 7
    

This is only required to be understood if you are using the CLI, or interacting with the program without using the SDK.

[PreviousAccounts](https://docs.squads.so/main/development/reference/accounts)
[NextSpending Limits](https://docs.squads.so/main/development/reference/spending-limits)

Last updated 1 year ago

---

# Add To Batch | Development | Squads Docs

When adding to a batch, a few things need to be kept in mind:

*   When a new transaction is added, a vault transaction will be initialized with this method, and the batch's local index will be incremented
    
*   The `batchIndex` field refers to the global index of the batch account (like any other transaction), while `transactionIndex` refers to the batch's inner index for the transaction being initialized (will start at 1 for the first transaction)
    

[](https://docs.squads.so/main/development/typescript/instructions/add-to-batch#example)

Example


-----------------------------------------------------------------------------------------------------

Copy

    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 instruction = SystemProgram.transfer({
            fromPubkey: vaultPda,
            toPubkey: creator.publicKey,
            lamports: 1,
        });
          // This message contains the instructions that the transaction is going to execute
        const transferMessage = new TransactionMessage({
            payerKey: vaultPda,
            recentBlockhash: (await connection.getLatestBlockhash()).blockhash,
            instructions: [instruction],
        });
        
        // Add transaction to the batch
        const batchAddIx = await multisig.instructions.batchAddTransaction({
            // Index of the batch globally, like any other transaction
            batchIndex: BigInt(newTransactionIndex),
            multisigPda,
            vaultIndex: 0,
            transactionMessage: transferMessage,
            // Index of the transaction inside of the batch! Not globally. Starts at 1
            transactionIndex: 1,
            ephemeralSigners: 0,
            member: creator,
        });
    }

### 

[](https://docs.squads.so/main/development/typescript/instructions/add-to-batch#notes)

Notes

*   A Vault Transaction is initialized when you add to a batch
    
*   `batchIndex` field refers to a global index, while `transactionIndex` refers to the batch's inner index
    

[PreviousCreate Batch](https://docs.squads.so/main/development/typescript/instructions/create-batch)
[NextClose Vault Transaction Account](https://docs.squads.so/main/development/typescript/instructions/close-vault-transaction-account)

Last updated 1 year ago

---

# Remove Spending Limit | Development | Squads Docs

This instruction removes a spending limit at the discretion of the [Config Authority](https://docs.squads.so/main/development/reference/accounts#multisig)
.

[](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions/remove-spending-limit#typescript)

Typescript


-----------------------------------------------------------------------------------------------------------------------------------------------------

Copy

    import * as multisig from "@sqds/multisig";
    
    // Cluster Connection
    const connection = new Connection( < your rpc url > );
    
    // Fee payer is the a signer that pays the transaction fees
    const feePayer = Keypair.generate();
    
    // Derive the multisig PDA
    const multisigPda = multisig.getMultisigPda({
        // The createKey has to be a Public Key, see accounts reference for more info
        createKey,
    })[0];
    
    const spendingLimitPda = multisig.getSpendingLimitPda({
        multisigPda
        createKey: spendingLimitCreateKey,
    })[0];
    
    await multisig.rpc.multisigRemoveSpendingLimit({
        connection,
        multisigPda,
        spendingLimit: spendingLimitPda,
        configAuthority: null,
        feePayer: feePayer,
        rentCollector: feePayer.publicKey,
    });

### 

[](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions/remove-spending-limit#notes)

Notes

*   Can only be used with a [Controlled Multisig](https://docs.squads.so/main/development/reference/controlled-multisigs)
    .
    

[PreviousAdd spending limit](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions/add-spending-limit)
[NextAccounts](https://docs.squads.so/main/development/typescript/accounts)

Last updated 1 year ago

---

# Spending Limits | Development | Squads Docs

Spending Limits are made for certain members to not have to create a proposal transaction if they want to spend an amount under the Spending Limit set for them.

You can create, modify and remove Spending Limits with [Config Transactions](https://docs.squads.so/main/development/typescript/instructions/create-config-transaction)
.

[PreviousPermissions](https://docs.squads.so/main/development/reference/permissions)
[NextTime-locks](https://docs.squads.so/main/development/reference/time-locks)

Last updated 1 year ago

---

# Create Proposal | Development | Squads Docs

Proposals are tied to transactions one-to-one, enabling consensus and subsequent execution. They use the `transactionIndex` for mapping, which means that the index you used to create a transaction will be used to create a proposal for it.

[](https://docs.squads.so/main/development/typescript/instructions/create-proposal#example)

Example


--------------------------------------------------------------------------------------------------------

Copy

    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.proposalCreate({
            multisigPda,
            transactionIndex,
            // Must have "Voter" permissions at minimum
            creator: member,
        });
    }

### 

[](https://docs.squads.so/main/development/typescript/instructions/create-proposal#notes)

Notes

*   Proposal accounts must be created to successfully vote and execute vault transactions
    
*   For more information, see the [Vault Transaction](https://docs.squads.so/main/development/typescript/accounts/transactions#vault-transactions)
     section and [reference](https://docs.squads.so/main/development/reference/accounts#vault-transaction)
    .
    

[PreviousCreate Vault Transaction](https://docs.squads.so/main/development/typescript/instructions/create-vault-transaction)
[NextApprove Proposal](https://docs.squads.so/main/development/typescript/instructions/approve-proposal)

Last updated 1 year ago

---

# We're here to help | Development | Squads Docs

You can reach out to us on Discord if you encounter any issues when interacting with Squads Protocol or need help: [](https://discord.com/invite/YPXz64TrKs)
[https://discord.com/invite/YPXz64TrKs](https://discord.com/invite/YPXz64TrKs)

[PreviousCommands](https://docs.squads.so/main/development/cli/commands)
[NextMigrating from MultisigCreate v1 to v2](https://docs.squads.so/main/development/other/migrating-from-multisigcreate-v1-to-v2)

Last updated 1 year ago

---

# Installation | Development | Squads Docs

You can install the CLI with Cargo. For this an installation of Rust will be needed. You can find installation steps [here](https://www.rust-lang.org/tools/install)
.

Now, install the Squads CLI.

Copy

    cargo install squads-multisig-cli

[PreviousVault Check](https://docs.squads.so/main/development/api/vault-check)
[NextCommands](https://docs.squads.so/main/development/cli/commands)

Last updated 1 year ago

---

# Cancel Proposal | Development | Squads Docs

Cancelling a proposal will invalidate it. This requires that the member conducting the action have `Voter` permissions, the proposal is of `Approved` status, or the proposal is stale (Proposal `transactionIndex` < Multisig `staleTransactionIndex`).

[](https://docs.squads.so/main/development/typescript/instructions/cancel-proposal#example)

Example


--------------------------------------------------------------------------------------------------------

Copy

    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,
        });
    }

### 

[](https://docs.squads.so/main/development/typescript/instructions/cancel-proposal#notes)

Notes

*   Cancelling members must have "Voter" permissions
    
*   A Proposal can be cancelled if stale. The transaction index must be less than the stale transaction index (see [Multisig reference](https://docs.squads.so/main/development/reference/accounts#multisig)
    )
    

[PreviousReject Proposal](https://docs.squads.so/main/development/typescript/instructions/reject-proposal)
[NextExecute Config Transaction](https://docs.squads.so/main/development/typescript/instructions/execute-config-transaction)

Last updated 1 year ago

---

# Vault Check | Development | Squads Docs

This endpoint allows the caller to specify a Solana address and return whether or not that address is a valid Squads V3 or V4 vault account, and can receive funds.

**Endpoint:**

Copy

    https://4fnetmviidiqkjzenwxe66vgoa0soerr.lambda-url.us-east-1.on.aws/isSquad/<ADDRESS>

**Example Request:**

Copy

    https://4fnetmviidiqkjzenwxe66vgoa0soerr.lambda-url.us-east-1.on.aws/isSquad/HFwi9HgNtFcMwNJPHa1czrPhuxeZFZ7G9tPQ1LqAd7sy

**Example Response:**

Copy

    {
      “isSquad”: true,
      “version”: "v4“
    }

`isSquad` denotes whether the given address is a valid Squads vault or not. True means it is a valid V3 or V4 vault account.

`version` denotes which Squads program version the vault is from, if it is a valid vault. This will return V3, V4, or an empty string if `isSquad` is false.

### 

[](https://docs.squads.so/main/development/api/vault-check#important-notes)

Important Notes:

*   This endpoint does not check for ATA (associated token account) validity. **IF SENDING SPL TOKENS, YOU MUST CHECK THIS SEPARATELY.**
    
*   There is a rate limit of 25 RPS.
    
*   Do not expose the endpoint URL on your frontend. Either use SSR, or proxy the endpoint through a server you control.
    
*   If possible, cache responses to your own infrastructure to avoid polling the endpoint for the same addresses again and again.
    

[PreviousControlled Multisigs](https://docs.squads.so/main/development/reference/controlled-multisigs)
[NextInstallation](https://docs.squads.so/main/development/cli/installation)

Last updated 1 year ago

---

# Execute Config Transaction | Development | Squads Docs

Executing a config transaction will simply execute the action specified in the Config Transaction. This execution can range from a simple account field change on the Multisig, to multiple field changes and corresponding account creation.

This instruction requires that the Proposal accounts for the transaction is of `Approved` status, and the member running the instruction has `Executor` permissions.

[](https://docs.squads.so/main/development/typescript/instructions/execute-config-transaction#example)

Example


-------------------------------------------------------------------------------------------------------------------

Copy

    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 = multisig.instructions.configTransactionExecute({
            multisigPda,
            transactionIndex: newTransactionIndex,
            // Member must have "Executor" permissions
            member: creator.publicKey,
        });
    }

### 

[](https://docs.squads.so/main/development/typescript/instructions/execute-config-transaction#notes)

Notes

*   Member must have "Executor" permissions
    
*   Requires the corresponding proposal to be of `Approved` status
    
*   Will execute the specified action in the [Config Transaction](https://docs.squads.so/main/development/reference/accounts#config-transaction)
     account
    

[PreviousCancel Proposal](https://docs.squads.so/main/development/typescript/instructions/cancel-proposal)
[NextExecute Vault Transaction](https://docs.squads.so/main/development/typescript/instructions/execute-vault-transaction)

Last updated 1 year ago

---

# Add spending limit | Development | Squads Docs

This instruction adds a spending limit at the discretion of the [Config Authority](https://docs.squads.so/main/development/reference/accounts#multisig)
.

[](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions/add-spending-limit#example)

Example


--------------------------------------------------------------------------------------------------------------------------------------------

Copy

    import * as multisig from "@sqds/multisig";
    
    // Cluster Connection
    const connection = new Connection( < your rpc url > );
    
    // Fee payer is the a signer that pays the transaction fees
    const feePayer = Keypair.generate();
    
    // Derive the multisig PDA
    const multisigPda = multisig.getMultisigPda({
        // The createKey has to be a Public Key, see accounts reference for more info
        createKey,
    })[0];
    
    const spendingLimitCreateKey = Keypair.generate().publicKey;
    
    const spendingLimitPda = multisig.getSpendingLimitPda({
        multisigPda
        createKey: spendingLimitCreateKey,
    })[0];
    
    multisig.rpc.multisigAddSpendingLimit({
        connection,
        feePayer,
        // The multisig account Public Key
        multisigPda,
        // The spending limit account Public Key
        spendingLimit: spendingLimitPda,
        createKey: spendingLimitCreateKey,
        // Rent payer for state
        rentPayer: feePayer,
        // Spending limit amount
        amount: BigInt(1000000000),
        configAuthority: null,
        // Spending limit will apply daily, see reference for more info
        period: multisig.generated.Period.Day,
        // The mint of the token to apply the spending limit on
        mint: Keypair.generate().publicKey,
        destinations: [Keypair.generate().publicKey],
        // null means it will apply to all members, make it an array of Public Keys to specify certain members
        members: null,
        vaultIndex: 1,
    }),

### 

[](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions/add-spending-limit#notes)

Notes

*   Can only be used with a [Controlled Multisig](https://docs.squads.so/main/development/reference/controlled-multisigs)
    .
    

[PreviousSet Rent Collector](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions/set-rent-collector)
[NextRemove Spending Limit](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions/remove-spending-limit)

Last updated 1 year ago

---

# Execute Vault Transaction | Development | Squads Docs

Executing a vault transaction will take all of the instructions saved in the `message` field of the corresponding Vault Transaction account, and atomically execute them via CPI. This requires that the Proposal accounts for the transaction is of `Approved` status, and the member running the instruction has `Executor` permissions.

[](https://docs.squads.so/main/development/typescript/instructions/execute-vault-transaction#example)

Example


------------------------------------------------------------------------------------------------------------------

Copy

    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.vaultTransactionExecute({
            multisigPda,
            transactionIndex,
            // Member must have "Executor" permissions
            member: member,
        });
    }

### 

[](https://docs.squads.so/main/development/typescript/instructions/execute-vault-transaction#notes)

Notes

*   Member must have "Executor" permissions
    
*   Requires the corresponding proposal to be of `Approved` status
    
*   Will execute each instruction via CPI, requiring the instructions to be valid
    
    *   Since this is an asynchronous process, some instructions may become stale due to external program checks like slippage.
        
    

[PreviousExecute Config Transaction](https://docs.squads.so/main/development/typescript/instructions/execute-config-transaction)
[NextCreate Batch](https://docs.squads.so/main/development/typescript/instructions/create-batch)

Last updated 1 year ago

---

# Create Batch | Development | Squads Docs

Batches allow you to approve, reject, cancel, or execute multiple transactions with a single action.

When working with batches, you can follow this general procedure:

1.  Create a batch
    
2.  Create a proposal as a draft
    
3.  Add transactions to the batch
    
4.  Activate the proposal
    
5.  Vote on the proposal
    
6.  Execute the proposal
    

[](https://docs.squads.so/main/development/typescript/instructions/create-batch#example)

Example


-----------------------------------------------------------------------------------------------------

Copy

    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;
        
        // Create the batch, which we can add transactions to
        const batchCreateIx = await multisig.instructions.batchCreate({
            batchIndex: transactionIndex,
            creator: member,
            multisigPda,
            vaultIndex: 0,
            memo: "Creating a batch",
        });
        
        // Create the proposal for voting on the transactions
        const proposalCreateIx = await multisig.instructions.proposalCreate({
            multisigPda,
            // Created with the same index as the batch
            transactionIndex: transactionIndex,
            creator: member,
            // Proposal is created as a draft
            isDraft: true,
        });
    }

### 

[](https://docs.squads.so/main/development/typescript/instructions/create-batch#notes)

Notes

*   Batches are for coupling multiple vault transactions under one proposal
    
*   They have their own `transactionIndex` context, starting at 1
    

[PreviousExecute Vault Transaction](https://docs.squads.so/main/development/typescript/instructions/execute-vault-transaction)
[NextAdd To Batch](https://docs.squads.so/main/development/typescript/instructions/add-to-batch)

Last updated 1 year ago

---

# Proposal | Development | Squads Docs

Proposals handle consensus for a given transaction, mapped one-to-one. Without a proposal account for a transaction, it can not be voted on and subsequently executed.

### 

[](https://docs.squads.so/main/development/typescript/accounts/proposal#getting-a-proposal-account)

Getting a Proposal account

Copy

    import * as multisig from "@sqds/multisig";
    
    const { Proposal } = multisig.accounts;
    
    async function main() {
        // Public Key of the Multisig PDA
        const multisigPda = new PublicKey("MyAmazingMultisig");
        
        // Fetch the deserialized Multisig account
        const multisigInfo = await multisig.accounts.Multisig.fromAccountAddress(
          connection,
          multisigPda
        );
    
        // Get the current transaction index
        const currentTransactionIndex = Number(multisigInfo.transactionIndex);
        const transactionIndex = BigInt(currentTransactionIndex + 1);
        // or, if this is your first transaction
        // const transactionIndex = 1n;    
        
        // Bump is generally not needed
        const [proposalPda, proposalBump] = multisig.getProposalPda({
            multisigPda,
            transactionIndex,
        });
        
        const proposalAccount = await Proposal.fromAccountAddress(
            connection,
            proposalPda
        );
              
        // Log the proposal status
        console.log("Proposal Status", proposalAccount.status);
    }

### 

[](https://docs.squads.so/main/development/typescript/accounts/proposal#notes)

Notes

*   Required for voting on and executing transactions
    
*   They store status of consensus, and tallies for who's approved and rejected.
    
*   See the [reference](https://docs.squads.so/main/development/reference/accounts#proposal)
     for more information on account structure and seeds.
    

[PreviousTransactions](https://docs.squads.so/main/development/typescript/accounts/transactions)
[NextBatch](https://docs.squads.so/main/development/typescript/accounts/batch)

Last updated 1 year ago

---

# Accounts | Development | Squads Docs

This section outlines the different account types you will encounter when interacting with Squads v4, including seeds and the struct associated with the account type. The program for all derivations in this section is the Squads v4 program ID.

* * *

[](https://docs.squads.so/main/development/reference/accounts#multisig)

Multisig


-------------------------------------------------------------------------------------

The multisig account is the main config for your Squad. This will contain your threshold, members, config authority, and handle any time-locks.

### 

[](https://docs.squads.so/main/development/reference/accounts#pda-derivation)

PDA Derivation

A multisig account is derived with the following seeds:

`["multisig", "multisig", createKey]`

The createKey is a unique Public Key, made specifically to derive the Multisig PDA.

### 

[](https://docs.squads.so/main/development/reference/accounts#multisig-account-content)

Multisig Account Content

Copy

    #[account]
    pub struct Multisig {
        /// Key that is used to seed the multisig PDA.
        pub create_key: Pubkey,
        /// The authority that can change the multisig config.
        /// This is a very important parameter as this authority can change the members and threshold.
        ///
        /// The convention is to set this to `Pubkey::default()`.
        /// In this case, the multisig becomes autonomous, so every config change goes through
        /// the normal process of voting by the members.
        ///
        /// However, if this parameter is set to any other key, all the config changes for this multisig
        /// will need to be signed by the `config_authority`. We call such a multisig a "controlled multisig".
        pub config_authority: Pubkey,
        /// Threshold for signatures.
        pub threshold: u16,
        /// How many seconds must pass between transaction voting settlement and execution.
        pub time_lock: u32,
        /// Last transaction index. 0 means no transactions have been created.
        pub transaction_index: u64,
        /// Last stale transaction index. All transactions up until this index are stale.
        /// This index is updated when multisig config (members/threshold/time_lock) changes.
        pub stale_transaction_index: u64,
        /// Reserved for future use.
        pub _reserved: u8,
        /// Bump for the multisig PDA seed.
        pub bump: u8,
        /// Members of the multisig.
        pub members: Vec<Member>,
    }

* * *

[](https://docs.squads.so/main/development/reference/accounts#proposal)

Proposal


-------------------------------------------------------------------------------------

The proposal account tracks votes cast by members pertaining to a given transaction. It stores the status of the given transaction, allowing it to be executed once the multisig threshold has been met.

### 

[](https://docs.squads.so/main/development/reference/accounts#pda-derivation-1)

PDA Derivation

A proposal account is derived with the following seeds:

`["multisig", multisig_key (as buffer), "transaction", transaction_index, "proposal"]`

The transaction index is a number auto incrementing based on your Multisig's total transactions.

### 

[](https://docs.squads.so/main/development/reference/accounts#proposal-account-content)

Proposal Account Content

Copy

    #[account]
    pub struct Proposal {
        /// The multisig this belongs to.
        pub multisig: Pubkey,
        /// Index of the multisig transaction this proposal is associated with.
        pub transaction_index: u64,
        /// The status of the transaction.
        pub status: ProposalStatus,
        /// PDA bump.
        pub bump: u8,
        /// Keys that have approved/signed.
        pub approved: Vec<Pubkey>,
        /// Keys that have rejected.
        pub rejected: Vec<Pubkey>,
        /// Keys that have cancelled (Approved only).
        pub cancelled: Vec<Pubkey>,
    }

* * *

[](https://docs.squads.so/main/development/reference/accounts#vault-transaction)

Vault Transaction


-------------------------------------------------------------------------------------------------------

The vault transaction account stores a transaction message that is subsequently voted on via a proposal.

### 

[](https://docs.squads.so/main/development/reference/accounts#pda-derivation-2)

PDA Derivation

A vault transaction account is derived with the following seeds:

`["multisig", multisig_key (as buffer), "transaction", transaction_index]`

The transaction index is a number auto incrementing based on your Multisig's total transactions.

### 

[](https://docs.squads.so/main/development/reference/accounts#vault-transaction-account-content)

Vault Transaction Account Content

Copy

    #[account]
    pub struct VaultTransaction {
        /// The multisig this belongs to.
        pub multisig: Pubkey,
        /// Member of the Multisig who submitted the transaction.
        pub creator: Pubkey,
        /// Index of this transaction within the multisig.
        pub index: u64,
        /// bump for the transaction seeds.
        pub bump: u8,
        /// Index of the vault this transaction belongs to.
        pub vault_index: u8,
        /// Derivation bump of the vault PDA this transaction belongs to.
        pub vault_bump: u8,
        /// Derivation bumps for additional signers.
        /// Some transactions require multiple signers. Often these additional signers are "ephemeral" keypairs
        /// that are generated on the client with a sole purpose of signing the transaction and be discarded immediately after.
        /// When wrapping such transactions into multisig ones, we replace these "ephemeral" signing keypairs
        /// with PDAs derived from the MultisigTransaction's `transaction_index` and controlled by the Multisig Program;
        /// during execution the program includes the seeds of these PDAs into the `invoke_signed` calls,
        /// thus "signing" on behalf of these PDAs.  
        pub ephemeral_signer_bumps: Vec<u8>,
        /// data required for executing the transaction.
        pub message: VaultTransactionMessage,
    }

* * *

[](https://docs.squads.so/main/development/reference/accounts#batch)

Batch


-------------------------------------------------------------------------------

The batch account stores a collection of vault transactions, allowing them to be subsequently voted on, and executed with minimal actions.

### 

[](https://docs.squads.so/main/development/reference/accounts#pda-derivation-3)

PDA Derivation

A batch account is derived with the following seeds:

`["multisig", multisig_key (as buffer), "transaction", transaction_index]`

### 

[](https://docs.squads.so/main/development/reference/accounts#batch-transaction-account-content)

Batch Transaction Account Content

Copy

    #[account]
    #[derive(InitSpace)]
    pub struct Batch {
        /// The multisig this belongs to.
        pub multisig: Pubkey,
        /// Member of the Multisig who submitted the batch.
        pub creator: Pubkey,
        /// Index of this batch within the multisig transactions.
        pub index: u64,
        /// PDA bump.
        pub bump: u8,
        /// Index of the vault this batch belongs to.
        pub vault_index: u8,
        /// Derivation bump of the vault PDA this batch belongs to.
        pub vault_bump: u8,
        /// Number of transactions in the batch.
        pub size: u32,
        /// Index of the last executed transaction within the batch.
        /// 0 means that no transactions have been executed yet.
        pub executed_transaction_index: u32,
    }

* * *

[](https://docs.squads.so/main/development/reference/accounts#config-transaction)

Config Transaction


---------------------------------------------------------------------------------------------------------

The config transaction account is similar to a vault transaction, but deals directly with configuration parameters in your multisig account. These are used in cases where there is no set config authority.

### 

[](https://docs.squads.so/main/development/reference/accounts#pda-derivation-4)

PDA Derivation

A config transaction account is derived with the following seeds:

`["multisig", multisig_key (as buffer), "transaction", transaction_index]`

### 

[](https://docs.squads.so/main/development/reference/accounts#config-transaction-account-content)

Config Transaction Account Content

Copy

    #[account]
    pub struct ConfigTransaction {
        /// The multisig this belongs to.
        pub multisig: Pubkey,
        /// Member of the Multisig who submitted the transaction.
        pub creator: Pubkey,
        /// Index of this transaction within the multisig.
        pub index: u64,
        /// bump for the transaction seeds.
        pub bump: u8,
        /// Action to be performed on the multisig.
        pub actions: Vec<ConfigAction>,
    }

[PreviousBatch](https://docs.squads.so/main/development/typescript/accounts/batch)
[NextPermissions](https://docs.squads.so/main/development/reference/permissions)

Last updated 1 year ago

---

# Create Vault Transaction | Development | Squads Docs

Vault Transactions allow you to take actions from programs all across Solana, and execute them inside of your multisig.

To create one, you need the latest transaction index from your multisig account, a message with the instructions you want to execute, and the index of the vault you'd like to execute from. Additionally, you can also add `n` number of ephemeral signers, in case that extra signatures are required.

[](https://docs.squads.so/main/development/typescript/instructions/create-vault-transaction#example)

Example


-----------------------------------------------------------------------------------------------------------------

Copy

    import * as multisig from "@sqds/multisig";
    import { PublicKey, Connection, SystemProgram, TransactionMessage } 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>");
        
        // 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);
        
        const to = new PublicKey("<>");
        
        const transferInstruction = SystemProgram.transfer({
            // The transfer is being signed by the vault that's executing
            fromPubkey: vaultPda,
            toPubkey: to,
            lamports: 1 * LAMPORTS_PER_SOL
        });
        
        // Build a message with instructions we want to execute
        const testTransferMessage = new TransactionMessage({
            payerKey: vaultPda,
            recentBlockhash: (await connection.getLatestBlockhash()).blockhash,
            instructions: [transferInstruction],
        });
        
        const ix = await multisig.instructions.vaultTransactionCreate({
            multisigPda,
            transactionIndex,
            creator: member,
            vaultIndex: 0,
            ephemeralSigners: 0,
            transactionMessage: testTransferMessage,
            memo: "Our first transfer!"
        });
    }

### 

[](https://docs.squads.so/main/development/typescript/instructions/create-vault-transaction#notes)

Notes

*   Vault transactions are built with a TransactionMessage containing the instructions you want to execute
    
*   Proposal accounts must be created to successfully vote and execute vault transactions
    
*   For more information, see the [Vault Transaction](https://docs.squads.so/main/development/typescript/accounts/transactions#vault-transactions)
     section and [reference](https://docs.squads.so/main/development/reference/accounts#vault-transaction)
    .
    

[PreviousCreate Config Transaction](https://docs.squads.so/main/development/typescript/instructions/create-config-transaction)
[NextCreate Proposal](https://docs.squads.so/main/development/typescript/instructions/create-proposal)

Last updated 1 year ago

---

# Add Member | Development | Squads Docs

This instruction adds a member at the discretion of the [Config Authority](https://docs.squads.so/main/development/reference/accounts#multisig)
.

[](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions/add-member#example)

Example


------------------------------------------------------------------------------------------------------------------------------------

Copy

    import * as multisig from "@sqds/multisig";
    
    // Cluster Connection
    const connection = new Connection("<your rpc url>");
    
    // Fee payer is the a signer that pays the transaction fees
    const feePayer = Keypair.generate();
    
    // Derive the multisig PDA
    const multisigPda = multisig.getMultisigPda({
        // The createKey has to be a Public Key, see accounts reference for more info
        createKey,
    })[0];
    
    // Public Key of the new member
    const member = new PublicKey("");
    
    await multisig.rpc.multisigAddMember({
        connection,
        feePayer,
        // The public key of the multisig account
        multisigPda,
        // Specify the config authority Public Key if there is one, else set to null
        configAuthority: null,
        // Account paying for the rent of the additional account space needed by adding a member
        rentPayer: feePayer,
        newMember: {
            // Public Key of the new member to be added
            key: members.almighty.publicKey,
            // Permissions that the new member will have, check the reference for more info
            permissions: Permissions.all(),
        },
    });

### 

[](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions/add-member#notes)

Notes

*   Can only be used with a [Controlled Multisig](https://docs.squads.so/main/development/reference/controlled-multisigs)
    .
    

[PreviousControlled Multisig Instructions](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions)
[NextRemove Member](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions/remove-member)

Last updated 1 year ago

---

# Remove Member | Development | Squads Docs

This instruction removes a member at the discretion of the [Config Authority](https://docs.squads.so/main/development/reference/accounts#multisig)
.

[](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions/remove-member#example)

Example


---------------------------------------------------------------------------------------------------------------------------------------

Copy

    import * as multisig from "@sqds/multisig";
    
    // Cluster Connection
    const connection = new Connection( < your rpc url > );
    
    // Fee payer is the a signer that pays the transaction fees
    const feePayer = Keypair.generate();
    
    // Derive the multisig PDA
    const multisigPda = multisig.getMultisigPda({
        // The createKey has to be a Public Key, see accounts reference for more info
        createKey,
    })[0];
    
    // Public Key of the old member
    const oldMember = new PublicKey("");
    
    await multisig.rpc.multisigRemoveMember({
        connection,
        feePayer,
        // The public key of the multisig account
        multisigPda,
        // Specify the config authority Public Key if there is one, else set to null
        configAuthority: null,
        // Account paying for the rent of the additional account space needed by adding a member
        rentPayer: feePayer,
        oldMember,
        memo,
        // ProgramId of the Squads Program
        programId
        
    });

### 

[](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions/remove-member#notes)

Notes

*   Can only be used with a [Controlled Multisig](https://docs.squads.so/main/development/reference/controlled-multisigs)
    .
    

[PreviousAdd Member](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions/add-member)
[NextSet Rent Collector](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions/set-rent-collector)

Last updated 1 year ago

---

# Squads Actions and Blinks | Development | Squads Docs

### 

[](https://docs.squads.so/main/development/other/squads-actions-and-blinks#what-are-solana-actions)

What are Solana Actions?

[Solana Actions](https://solana.com/docs/advanced/actions#actions)
 are specification-compliant APIs that return transactions on the Solana blockchain to be previewed, signed, and sent across a number of various contexts, including QR codes, buttons + widgets, and websites across the internet.

Actions make it simple for developers to integrate the things you can do throughout the Solana ecosystem right into your environment, allowing you to perform blockchain transactions without needing to navigate away to a different app or webpage.

### 

[](https://docs.squads.so/main/development/other/squads-actions-and-blinks#what-are-blockchain-links-blinks)

What are blockchain links (blinks)?

[Blockchain links](https://solana.com/docs/advanced/actions#blinks)
 – or blinks – turn any Solana Action into a shareable, metadata-rich link. Blinks allow Action-aware clients (browser extension wallets, bots) to display additional capabilities for the user. On a website, a blink might immediately trigger a transaction preview in a wallet without going to a decentralized app; in Discord, a bot might expand the blink into an interactive set of buttons. This pushes the ability to interact onchain to any web surface that displays a URL.

### 

[](https://docs.squads.so/main/development/other/squads-actions-and-blinks#getting-started)

Getting Started

Install the [`@solana/actions` SDK](https://www.npmjs.com/package/@solana/actions)
 into your application:

Copy

    npm add @solana/actions

Check out both Solana’s [official docs](https://solana.com/docs/advanced/actions)
 and Dialect’s [dashboard](https://dashboard.dialect.to/actions)
. Once you’re familiar with blinks, you can use our SDK to start building with Squads inside of a blink. Here's an example of a blink using [Squads v4 SDK](https://github.com/joeymeere/squads-actions)
.

You can test your blink [here](https://dial.to/)
, and once you’re ready to deploy it to the world you can [apply for verification](https://airtable.com/appGlCDHyLzKnyljX/pagIjqCnWiA7jppHM/form)
 so the blink will render on X.

### 

[](https://docs.squads.so/main/development/other/squads-actions-and-blinks#ideas-to-build)

Ideas to build

Here are a few ideas from the team and community:

1.  **Create a Squad**
    
    *   Add corresponding keys, and a threshold, and deploy a Squad directly from X.
        
    
2.  **Squads Blink Bot**
    
    *   Deploy an X bot for a Squad that DMs members of the Squad when transactions are proposed.
        
    
3.  **Add Member**
    
    *   Specify a member key and permission levels, and propose to add a member with a blink.
        
    
4.  **Propose a transaction**
    
    *   Drop a base64 string and propose a transaction directly from a blink.
        
    
5.  **Propose a stake transaction**
    
    *   Allow certain validators to send pre-built stake transactions that can be proposed directly to your squad.
        
    
6.  **Add a Spending Limit**
    
    *   Create and configure spending limits via blinks.
        
    
7.  **Enable Rent Reclaim**
    
    *   Propose/execute a transaction to enable rent reclamation (or other configuration)
        
    

### 

[](https://docs.squads.so/main/development/other/squads-actions-and-blinks#resources)

Resources

*   [Solana's official docs](https://solana.com/docs/advanced/actions)
    
*   Dialect’s [dashboard](https://dashboard.dialect.to/actions)
    
*   Video tutorial on [How to Build Solana Actions](https://youtu.be/kCht01Ycif0)
    
*   Example of a blink using [Squads v4 SDK](https://github.com/joeymeere/squads-actions)
    

Find example code snippets on how to build several different Solana Actions:

*   [Deployed sample code snippets](https://solana-actions.vercel.app/)
    
*   [Source code for code snippets](https://github.com/solana-developers/solana-actions/tree/main/examples/next-js)
    

If you have any questions or encounter any issues, please reach out to us on [Discord](https://discord.com/invite/YPXz64TrKs)
.

[PreviousMigrating from MultisigCreate v1 to v2](https://docs.squads.so/main/development/other/migrating-from-multisigcreate-v1-to-v2)

Last updated 1 year ago

---

# Migrating from MultisigCreate v1 to v2 | Development | Squads Docs

Squads has recently made a new update to their program which introduced rent collection of account data for transactions that have been initiated through the Squads program.

Here's how to use the new Multisig Create V2 instruction.

[](https://docs.squads.so/main/development/other/migrating-from-multisigcreate-v1-to-v2#typescript)

Typescript


-------------------------------------------------------------------------------------------------------------------

Copy

        const creator = fundedKeypairExample();
    
        const createKey = Keypair.generate();
        
        const [multisigPda] = multisig.getMultisigPda({
          createKey: createKey.publicKey,
        });
        
      
        const programConfigPda = getProgramConfigPda({})[0];
    
        const programConfig =
          await multisig.accounts.ProgramConfig.fromAccountAddress(
            connection,
            programConfigPda
          );
    
        const configTreasury = programConfig.treasury;
    
        const tx = multisig.transactions.multisigCreateV2({
          blockhash: (await connection.getLatestBlockhash()).blockhash,
          treasury: configTreasury,
          createKey: createKey.publicKey,
          creator: creator.publicKey,
          multisigPda,
          configAuthority: null,
          timeLock: 0,
          threshold: 1,
          rentCollector: null,
          members: [\
            {\
              key: members.almighty.publicKey,\
              permissions: Permissions.all(),\
            },\
            {\
              key: members.almighty.publicKey,\
              permissions: Permissions.all(),\
            },\
          ],
          programId,
        });
    
        
        tx.sign([creator, createKey]);

[](https://docs.squads.so/main/development/other/migrating-from-multisigcreate-v1-to-v2#rust)

Rust


-------------------------------------------------------------------------------------------------------

Copy

    
            let rpc_client = RpcClient::new(rpc_url);
    
            let progress = ProgressBar::new_spinner().with_message("Sending transaction...");
            progress.enable_steady_tick(Duration::from_millis(100));
    
            let blockhash = rpc_client
                .get_latest_blockhash()
                .await
                .expect("Failed to get blockhash");
    
            let random_keypair = Keypair::new();
    
            let multisig_key = get_multisig_pda(&random_keypair.pubkey(), Some(&program_id));
    
            let program_config_pda = get_program_config_pda(Some(&program_id));
    
            let program_config = rpc_client
                .get_account(&program_config_pda.0)
                .await
                .expect("Failed to fetch program config account");
    
            let mut program_config_data = program_config.data.as_slice();
    
            let treasury = ProgramConfig::try_deserialize(&mut program_config_data)
                .unwrap()
                .treasury;
    
            let message = Message::try_compile(
                &transaction_creator,
                &[Instruction {\
                    accounts: MultisigCreateV2Accounts {\
                        create_key: random_keypair.pubkey(),\
                        creator: transaction_creator,\
                        multisig: multisig_key.0,\
                        system_program: system_program::id(),\
                        program_config: program_config_pda.0,\
                        treasury,\
                    }\
                    .to_account_metas(Some(false)),\
                    data: MultisigCreateV2Data {\
                        args: MultisigCreateArgsV2 {\
                            config_authority,\
                            members,\
                            threshold,\
                            time_lock: 0,\
                            memo: None,\
                            rent_collector,\
                        },\
                    }\
                    .data(),\
                    program_id,\
                }],
                &[],
                blockhash,
            )
            .unwrap();
    
            let transaction = VersionedTransaction::try_new(
                VersionedMessage::V0(message),
                &[\
                    &*transaction_creator_keypair,\
                    &random_keypair as &dyn Signer,\
                ],
            )
            .expect("Failed to create transaction");
    
            let signature = send_and_confirm_transaction(&transaction, &rpc_client).await?;
    

[PreviousWe're here to help](https://docs.squads.so/main/development/get-support/were-here-to-help)
[NextSquads Actions and Blinks](https://docs.squads.so/main/development/other/squads-actions-and-blinks)

Last updated 1 year ago

---

# Set Rent Collector | Development | Squads Docs

This instruction edits the rent collector at the discretion of the [Config Authority](https://docs.squads.so/main/development/reference/accounts#multisig)
.

[](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions/set-rent-collector#example)

Example


--------------------------------------------------------------------------------------------------------------------------------------------

Copy

    import * as multisig from "@sqds/multisig";
    
    // Cluster Connection
    const connection = new Connection( < your rpc url > );
    
    // Fee payer is the a signer that pays the transaction fees
    const feePayer = Keypair.generate();
    
    // Derive the multisig PDA
    const multisigPda = multisig.getMultisigPda({
        // The createKey has to be a Public Key, see accounts reference for more info
        createKey,
    })[0];
    
    const transactionIndex = 1n;
    
    const newRentCollector = Keypair.generate().publicKey;
    
    const signature = await multisig.rpc.multisigSetRentCollector({
          connection,
          multisigPda,
          feePayer,
          configAuthority: configAuthority.publicKey,
          newRentCollector,
          rentPayer: feePayer,
          programId,
          signers: [feePayer],
    });

### 

[](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions/set-rent-collector#notes)

Notes

*   Can only be used with a [Controlled Multisig](https://docs.squads.so/main/development/reference/controlled-multisigs)
    .
    

[PreviousRemove Member](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions/remove-member)
[NextAdd spending limit](https://docs.squads.so/main/development/typescript/instructions/controlled-multisig-instructions/add-spending-limit)

Last updated 1 year ago

---

# Developers | Squads Legacy (v3) | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FS1o2Povr4xazk58Mtoo3%2FDevelopers.png&width=1248&dpr=4&quality=100&sign=47a27c7f&sv=2)

This section is dedicated to teams and protocols that wish to manage their programs, native tokens, and validators with multisig. Additionally, advanced users can create arbitrary instructions through TX Builder, allowing them to perform actions with on-chain assets stored in or managed by their Squad or to interact with protocols and dapps not natively integrated inside Squads.

1.  [Programs](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/programs)
    
2.  [Token manager](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/token-manager)
    
3.  [Validators](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/validators)
    
4.  TX Builder
    

[PreviousTransactions](https://docs.squads.so/main/squads-legacy/navigating-your-squad/transactions)
[NextPrograms](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/programs)

Last updated 2 years ago

---

# Activating a Transaction | Squads Legacy (v3) | Squads Docs

In order for the mulltisig to approve or reject a transaction, the transaction must be activated by switching the status to "Active". Only the creator of a transaction can change the state to Active, and once activated it is no longer possible to change instruction data attached to the transaction.

Copy

      // the member/creator
      const creator = wallet.publicKey;
      
      // acitvate the tx
      await program.methods.activateTransaction()
               .accounts({
                    multisig,
                    transaction,
                    creator
               })
               .rpc();

[PreviousAdding Instructions](https://docs.squads.so/main/squads-legacy/development/anchor-idl/transactions/adding-instructions)
[NextApprove / Reject a Transaction](https://docs.squads.so/main/squads-legacy/development/anchor-idl/transactions/approve-reject-a-transaction)

---

# Swap | Squads Legacy (v3) | Squads Docs

Swaps on v3 are no longer supported. Please migrate to [https://app.squads.so/](https://app.squads.so/squads)
 for the optimal smart trading experience. If you have any questions, please reach out to us on [Discord](https://discord.com/invite/YPXz64TrKs)
.

[PreviousSolBlaze](https://docs.squads.so/main/squads-legacy/integrations/staking/solblaze)
[NextTensor](https://docs.squads.so/main/squads-legacy/integrations/tensor)

Last updated 1 year ago

---

# Owners and Settings | Squads Legacy (v3) | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2Fi2f1pGbSvIH2XfqLUx96%2FSquads%2520Info.png&width=1248&dpr=4&quality=100&sign=d8a48907&sv=2)

### 

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/owners-and-settings#add-remove-owners)

Add/remove owners

Owners are added to a Squad via their public key.

The "Owners" tab **allows Squad owners to:**

*   view owners of the Squad
    
*   initiate a transaction to add/remove an owner (by clicking on "Add owner" button or "Bin" icon)
    
*   Add nicknames to the wallet addresses ( saved on local storage, therefore, only visible to the person who adds a nickname)
    
*   copy the address of the owner
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F39wZLKNUVL4dsZpBuVSH%2Fowners.png&width=768&dpr=4&quality=100&sign=cf583eb5&sv=2)

Owners tab

### 

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/owners-and-settings#info)

Info

The "Info" tab displays the basic information about the Squad and **allows to:**

*   check the confirmation threshold and initiate a transaction to change it
    
*   copy the addresses of the Squad's vault and account
    
*   check the number of owners inside the Squad
    
*   change the Squad profile picture, name, or description
    
*   change the explorer used for the transactions inspection
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F8SDsO8pYeauhXkJjXaUH%2Finfo%2520tab.png&width=768&dpr=4&quality=100&sign=4080b855&sv=2)

Info tab

### 

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/owners-and-settings#threshold-parameter)

Threshold Parameter

The confirmation threshold is every Squad's essential parameter, which helps ensure that funds management is secured by multiple signatures required for every transaction.

The confirmation threshold represents how many multisig owners' confirmations will be required for a transaction to become executable. It can be adjusted at any point in time by initiating a transaction from the "Info" tab.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FoRpeZJtFrXlflcK6QtIG%2Finfo.png&width=768&dpr=4&quality=100&sign=d883ad0e&sv=2)

Change the confirmation threshold pop-up

[PreviousApps](https://docs.squads.so/main/squads-legacy/navigating-your-squad/apps)
[NextStaking](https://docs.squads.so/main/squads-legacy/integrations/staking)

Last updated 1 year ago

---

# Staking | Squads Legacy (v3) | Squads Docs

Users can stake their SOL holding with Solana Network directly from their Squad. Users can stake their SOL with any Solana validator (powered by Stakewiz), various liquid staking providers (Jito, Lido, Marinade, SolBlaze) and also stake DeadGod NFTs.

More info on staking:

1.  [Stakewiz](https://docs.squads.so/main/squads-legacy/integrations/staking/stakewiz)
    
2.  [JitoSOL](https://docs.squads.so/main/squads-legacy/integrations/staking/jitosol)
    
3.  [Lido](https://docs.squads.so/main/squads-legacy/integrations/staking/lido)
    
4.  [Marinade](https://docs.squads.so/main/squads-legacy/integrations/staking/marinade)
    
5.  [SolBlaze](https://docs.squads.so/main/squads-legacy/integrations/staking/solblaze)
    

[PreviousOwners and Settings](https://docs.squads.so/main/squads-legacy/navigating-your-squad/owners-and-settings)
[NextStakewiz](https://docs.squads.so/main/squads-legacy/integrations/staking/stakewiz)

Last updated 1 year ago

---

# Tensor | Squads Legacy (v3) | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FnKlZcG08XHpmANbyQxDT%2FTensor%2520art.png&width=1248&dpr=4&quality=100&sign=f7168f07&sv=2)

Squads users can buy and list their NFTs directly from their Squad using Tensor integration.

[](https://docs.squads.so/main/squads-legacy/integrations/tensor#what-is-tensor)

What is Tensor?


-----------------------------------------------------------------------------------------------------

Tensor is a fast-growing NFT marketplace and trading platform, which allows their users to buy NFTs from different marketplaces.

[](https://docs.squads.so/main/squads-legacy/integrations/tensor#how-to-buy-nfts-from-tensor)

How to buy NFTs from Tensor?


-------------------------------------------------------------------------------------------------------------------------------

**To buy the NFT directly from your Squad:**

1.  Navigate to the "Vault" tab and select the "NFT" section.
    
2.  Click on the "Buy" button, insert the link from Tensor and launch a transaction. Make sure you have enough funds in your Squad vault to purchase the NFT.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FFk7vBiAKSNGTKeYCt3Nk%2FTensor.png&width=768&dpr=4&quality=100&sign=636e5191&sv=2)

Buy NFT pop-up

Please note that you can only purchase NFTs that are directly listed on Tensor. You can filter out all other marketplaces. You can find a link button in the NFT card in the top right corner.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F8xSCWYiWpI5J5K3ETdTV%2FTensor%25202.png&width=768&dpr=4&quality=100&sign=d99410a5&sv=2)

Detailed transaction view

1.  Your NFT will appear inside the NFT gallery upon transaction execution.
    

[](https://docs.squads.so/main/squads-legacy/integrations/tensor#how-to-list-nfts-on-tensor-from-your-squad)

How to list NFTs on Tensor from your Squad?


-------------------------------------------------------------------------------------------------------------------------------------------------------------

1.  To list NFT, navigate to the "Vault" tab, select the "NFT" section and click on the NFT you would like to list.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FRUh6X1EArBBkiTftRqM8%2FTensor%25203.png&width=768&dpr=4&quality=100&sign=4349dbb4&sv=2)

NFT detailed view

1.  Once you are in the detailed NFT view, click on the "List" button, set a price and description (optional) and launch a transaction.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FAQ4806NezdUjefoCrUOc%2FTensor%25204.png&width=768&dpr=4&quality=100&sign=2cc7f6b5&sv=2)

List NFT pop-up

1.  Your NFT will be listed on Tensor and marked as "Listed" in the NFT gallery upon transaction execution.
    

**You can also change the price of the NFT you listed or delist it at any time. To do this:**

1.  Click on the NFT you would like to delist or which price you would like to change.
    
2.  To delist NFT click on the "Delist" button / to change the price click on the "Edit listing" button and launch a transaction.
    
3.  Your NFT will be delisted / the price of the NFT will be updated upon transaction execution.
    

[PreviousSwap](https://docs.squads.so/main/squads-legacy/integrations/swap)
[NextDialect](https://docs.squads.so/main/squads-legacy/integrations/dialect)

Last updated 1 year ago

---

# Bonfida | Squads Legacy (v3) | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FI0MfKOzl8XQ6N76Sbet9%2FSquads%2520Docs-2.png&width=1248&dpr=4&quality=100&sign=52622c3a&sv=2)

[](https://docs.squads.so/main/squads-legacy/integrations/bonfida#what-is-bonfida)

What is Bonfida?


--------------------------------------------------------------------------------------------------------

Bonfida is a protocol on Solana that created the "Solana Naming Service" or SNS. With SNS, you can create a domain name that links to your wallet address. This domain can be used as a replacement for sending and receiving payments, adding a social component to crypto.

[](https://docs.squads.so/main/squads-legacy/integrations/bonfida#how-do-squads-protocol-users-benefit-from-this-integration)

How do Squads Protocol users benefit from this integration?


----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

By abstracting away wallet addresses, everyday crypto activities such as sending & receiving crypto and accounting for on-chain transactions become a much easier process. Instead of needing to remember a long string of random letters and numbers, Squads Protocol users can simply enter .sol domains, simplifying the entire process.

[](https://docs.squads.so/main/squads-legacy/integrations/bonfida#how-to-send-crypto-to-.sol-domains)

How to send crypto to .sol domains?


----------------------------------------------------------------------------------------------------------------------------------------------

Sending crypto to .sol domains via Bonfida's SNS is simple. Simply enter the .sol domain instead of the wallet address.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F647R4y1DalpDMUnKGAtD%2Fbonfida.png&width=768&dpr=4&quality=100&sign=6bbdb611&sv=2)

Withdrawal pop-up

[PreviousDialect](https://docs.squads.so/main/squads-legacy/integrations/dialect)
[NextCoinflow](https://docs.squads.so/main/squads-legacy/integrations/coinflow)

---

# Transactions | Squads Legacy (v3) | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F3zGO4v1Hi8b9Gifs8Lex%2FSquads%2520Transactions.png&width=1248&dpr=4&quality=100&sign=27f44f72&sv=2)

The transaction list displays all the Squad transactions by date. Transactions are an essential part of any multisig and are used to validate every action, impacting Ownership, Vault, or Rules within a Squad.

### 

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/transactions#deposit-and-send-funds)

Deposit and send funds

Squads Protocol supports all SPL tokens as well as NFTs. Users can deposit and send funds from the vault by initiating a transaction, which needs to be approved by other owners in a Squad. Once the asset is deposited it will appear in the "Vault balance" section.

**To deposit funds:**

1.  Navigate to the "Vault" section, click on the "DOWN" arrow, and select the asset and amount.
    
2.  Click the deposit button.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2Fr8azKZoym7dRoWTjbzfc%2FTransactions%25201.png&width=768&dpr=4&quality=100&sign=dd0536e7&sv=2)

Deposit pop-up

**To send funds:**

1.  Navigate to the "Vault" section, click on the "UP" arrow, fill in the transaction details, and launch a transaction.
    
2.  Once the transaction hits the confirmation threshold, it can be executed by any owner of a Squad.
    
3.  Funds will be transferred upon the execution of the transaction.
    

Please note that when you create a transaction to send assets to an address that hasn't received this specific token before (for example, sending USDC to a newly created wallet that hasn't had USDC previously), you will pay an additional amount of 0.003 SOL from your personal wallet. This will cover the cost of creating [ATA](https://spl.solana.com/associated-token-account)
 in the destination wallet.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F1wZwhLrKL1aHuFI98R8i%2FTransactions%25202.png&width=768&dpr=4&quality=100&sign=2028ffa7&sv=2)

Withdrawal pop-up

### 

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/transactions#receive-funds)

Receive funds

In Squads, users can receive funds from outside parties like contractors, investors, or mercenaries by sharing the QR code or a Squad or its address.

**To receive funds:**

1.  Click on the "DOWN" arrow in the Squads profile section and open a "Receive" screen.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FXNoDpvfna86ZsVLppeSq%2FTransactions%25203.png&width=768&dpr=4&quality=100&sign=6c738c92&sv=2)

Receive pop-up

### 

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/transactions#sign-transactions)

Sign Transactions

Squad actions such as adding/removing a member, sending SPL tokens/NFTs, upgrading programs, etc., will trigger a transaction, which needs to be confirmed by the Squad according to its confirmation threshold.

The Squad member who initiates a transaction automatically confirms the transaction and is transferred to the "Transaction" screen.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FnlwdfNwdaZDf9SAHROgZ%2FTransactions%25204.png&width=768&dpr=4&quality=100&sign=b017b8fb&sv=2)

Detailed transaction view

Transactions also can be signed from the "Transactions" tab by clicking on the expand arrow in the right corner of each transaction.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FyZ7fFlDRPXNtPMlkKV7z%2FTransactions%25205.png&width=768&dpr=4&quality=100&sign=81c604da&sv=2)

Expanded transaction view

After the transaction is initiated it needs to meet the confirmation threshold, so the transaction can be executed or canceled. Owners need to confirm or reject the transaction by selecting the relevant option in the "Cast your vote" section.

Transactions can be signed/executed/canceled either by clicking on them and entering a detailed view or by expanding them inside of the "Transactions" section.

### 

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/transactions#execute-cancel-transactions)

Execute/Cancel Transactions

Upon reaching the confirmation threshold a transaction will change its state to "Ready for execution". From this state, a transaction can be executed by any owner within a Squad.

Please note that to execute a transaction, only one vote is needed, but in order to cancel one, a confirmation threshold must be reached.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FNZ4HprpTFbd3E6UDAGIE%2FTransactions%25206.png&width=768&dpr=4&quality=100&sign=dc624b80&sv=2)

Transactions "Ready for execution" detailed view

Transactions can be executed or canceled both from the detailed and expanded views.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FSCIAAeF4Mbt43qGceX0g%2FTransactions%25207.png&width=768&dpr=4&quality=100&sign=bcde80d&sv=2)

Transaction "Ready for execution" expanded view

[PreviousVault](https://docs.squads.so/main/squads-legacy/navigating-your-squad/vault)
[NextDevelopers](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers)

Last updated 1 year ago

---

# Create a Squad | Squads Legacy (v3) | Squads Docs

Creating a Squad can be completed in less than 30 seconds!

### 

[](https://docs.squads.so/main/squads-legacy/getting-started/create-a-squad#creating-a-squad)

**Creating a Squad**

1.  Connect a Solana wallet to the [v3.squads.so](https://v3.squads.so/squads)
     by clicking on the "Connect Wallet" button.
    

We support the **following wallets**:

*   Phantom
    
*   Backpack
    
*   Glow
    
*   Solflare
    
*   Coinbase Wallet
    
*   Ledger
    
*   Exodus
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F0UF3FwPY1QBdtjjChwtT%2FCreate%2520a%2520Squad%25201.png&width=768&dpr=4&quality=100&sign=2ca80ac4&sv=2)

Supported wallets

2\. After your wallet is connected, click the “Create Squad” button.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FMwNu89YHneTVuhTy5v7M%2FCreate%2520a%2520Squad%25202.png&width=768&dpr=4&quality=100&sign=ecb4cd92&sv=2)

Your Squads list

3\. Enter Squad details such as Squad name, profile picture, and description.

*   We support JPEG, PNG, or GIFs formats under 3MB.
    
*   The Squad's picture, name, and description can be changed after deployment.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FDeFPpS8A4eaIxBuSbqmI%2FCreate%2520a%2520Squad%25203.png&width=768&dpr=4&quality=100&sign=b597ad07&sv=2)

Squad details

4\. Add owners to your Squad by their public keys and set a confirmation threshold.

*   The confirmation threshold is the number of approvals necessary from Squad owners for transactions to be executed. In the example below, 2/3 of wallets on the multisig will need to approve for a transaction to be executed.
    
*   You can add an unlimited amount of initial owners, but we recommend keeping the amount below 20 for the optimal experience. After the initial set-up, each new owner will need to be approved by the Squad based on the confirmation threshold you configure. When all owners are added, review the information and click "Next."
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F5jyzx4YglzFTEF3xkbIy%2FCreate%2520a%2520Squad%25204.png&width=768&dpr=4&quality=100&sign=3165fa66&sv=2)

Squad owners and confirmation threshold set-up

5\. Review your Squad's details and if everything looks correct, click “Confirm”.

*   Squad deployment cost is approximately between 0.0025 - 0.0045 SOL depending on the amount of the initial owners (Network fees, not Squads Protocol ones).
    
*   The fee includes Solana rent fee and 0.001 SOL, which will be deposited into your Squad upon creation. This is done to make your Squad's address recognizable by individual wallets for sending assets.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FmOhvsW10cSWaRFxgH4HF%2FCreate%2520a%2520Squad%25205.png&width=768&dpr=4&quality=100&sign=57e1ea5c&sv=2)

Review your Squad screen

6\. You will be brought to the Squad upon creation. More info on navigating a Squad can be found in this [section](https://docs.squads.so/main/squads-legacy/navigating-your-squad/dashboard)
.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FwjvkLCoQXUFwD4a2bIK7%2FCreate%2520a%2520Squad%25206.png&width=768&dpr=4&quality=100&sign=47eaede8&sv=2)

Squad vault

[PreviousWhat's a Squad?](https://docs.squads.so/main/squads-legacy)
[NextDashboard](https://docs.squads.so/main/squads-legacy/navigating-your-squad/dashboard)

Last updated 1 year ago

---

# What's a Squad? | Squads Legacy (v3) | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F2217621825-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FgDRN91t7KCCGF3GOssvZ%252Fuploads%252FKwmlqULI1BvT6RmoUgqr%252Fsquads-legacy-v3.webp%3Falt%3Dmedia%26token%3D92e9e030-c6fb-478a-929c-1525d397d8d9&width=1248&dpr=4&quality=100&sign=f0eac47c&sv=2)

A Squad is a programmable multisig wallet, which allows teams to jointly manage their treasury (fungible tokens, NFTs) and developer assets (programs, tokens, validators).

*   Owners are added to a Squad by their wallet addresses (public keys). You can add an unlimited amount of initial owners. We recommend keeping the number of owners under 20 for the best experience;
    
*   Each Squad has a Vault where users can send, receive, & store assets and perform various operations with them;
    
*   Each Squad has a Program section where programs can be added and upgraded;
    
*   Each Squad has a Token manager section where tokens can be added, minted and burned;
    
*   Each Squad has a Validator section where validators can be managed;
    
*   Each Squad has a TX Builder section, which allows for creation of arbitrary instructions;
    
*   Every action in the Squad triggers a transaction that needs to be approved and executed by the owners of a Squad;
    
*   Squad deployment costs approx. 0.0025 - 0.0045 SOL (Solana network fees) depending on the amount of the initial owners;
    

[NextCreate a Squad](https://docs.squads.so/main/squads-legacy/getting-started/create-a-squad)

Last updated 1 year ago

---

# General | Squads Legacy (v3) | Squads Docs

**Why should I use Squads Protocol?**

If you are looking for an affordable and secure multisig to manage and store your on-chain assets and/or programs, Squads Protocol was built for you. We are suitable for teams, DAOs, subDAOs, and secure individuals looking for security and co-ownership features not provided by normal wallets.

**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.

**Which wallets does Squads Protocol support?**

We support Phantom, Backpack, Glow, Solflare, Exodus, Coinbase wallet, Ledger and Wallet connect. If you have a request for a wallet integration, please reach out to us directly.

**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 right 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 have created a Squad, but I don’t see it in the Squads list.**

If you have created a Squad and it does not appear in the Squads list, please wait a few minutes and refresh the page. The initial creation of a Squad can take up to 15 minutes to show up due to network performance.

**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), meaning there are no private keys associated with them. Please refer to [**this section**](https://solana.com/docs/core/pda)
 of Solana docs for more info on PDAs.

PDAs are addresses generated to be controlled only by one specific program. Squads’ vaults are owned and controlled by the Squads program. If you are looking to deploy a Squad and have control over the program, please reach out to us.

**Is Squads Protocol permissionless?**

Yes, Squads Protocol is permissionless to interact with. You can connect your wallet and create a Squad at any given point in time.

**Can I create a Squad and gate access to it with NFTs?**

We don’t yet support the creation of NFT-gated Squads; owners are added to a Squad via their public keys. If you are keen on having this feature integrated, please reach out to us directly.

[PreviousCoinflow](https://docs.squads.so/main/squads-legacy/integrations/coinflow)
[NextCosts of using Squads](https://docs.squads.so/main/squads-legacy/frequently-asked-questions/costs-of-using-squads)

Last updated 1 year ago

---

# Creators | Squads Legacy (v3) | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FaElhRL1fFBIEKAGsvLSX%2FSquads%2520Creators.png&width=1248&dpr=4&quality=100&sign=7dd2a02&sv=2)

Users can delegate the upgrade authority of their NFT projects to a Squad and securely store it inside the multisig.

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/creators#how-to-delegate-nft-upgrade-authority-to-a-squad)

**How to delegate NFT upgrade authority to a Squad?**


----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

To delegate your NFT collection upgrade authority into a Squad:

1.  Use your CLI wallet which currently holds upgrade authority.
    
2.  Delegate the authority to your Squad address.
    
3.  Once authority is delegated, you will see a collection inside the "Collections" section.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F9qm1oJ47g1m3swzPmNB6%2Fcreators%25201.png&width=768&dpr=4&quality=100&sign=c23871dd&sv=2)

Collections section

Please note that it is currently not possible to make changes to your NFT collection (change metadata, manage token formats, etc.) inside the multisig. You will need to transfer upgrade authority to your CLI wallet and make all the changes from there.

We are working on implementing the whole collection management flow inside the UI. You can reach out to us via [Twitter](https://twitter.com/SquadsProtocol?s=20)
 or [Discord](https://discord.gg/Qwhew4M4RS)
 if you need any assistance.

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/creators#how-to-transfer-upgrade-authority-from-a-squad)

How to transfer upgrade authority from a Squad?


--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

To transfer authority out of your Squad:

1.  Add your CLI wallet as an owner to your Squad (check [Owners and Settings](https://docs.squads.so/main/squads-legacy/navigating-your-squad/owners-and-settings)
     for more info on adding owners).
    
2.  Launch a transaction inside your CLI wallet to change the NFT upgrade authority.
    

Please note that due to technical limitations the maximum number of NFTs bundled in 1 transaction equals 255. With a large collection (e.g. 10k), approximately 40 transactions will be created inside the UI. Using the "Batch approve" button in the UI, you can sign them all at once.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FiMkR3MJQGx3NReBO4Bvw%2Fcreators%25202.png&width=768&dpr=4&quality=100&sign=383df79c&sv=2)

NFT transactions section

1.  Once you meet the confirmation threshold you will be able to execute the transactions.
    
2.  Execute transactions using your CLI wallet or a hot wallet through Squads UI.
    

Please be aware that due to technical limitations you won't be able to execute those transactions with your Ledger wallet. We recommend to use CLI wallet or hot wallet (e.g. Phantom, Backpack, Glow, etc.).

If you are signing transactions with a hot wallet you may need to rerun the execution a few times because of the deprecation of a block hash.

[PreviousTX Builder](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/tx-builder)
[NextApps](https://docs.squads.so/main/squads-legacy/navigating-your-squad/apps)

---

# Apps | Squads Legacy (v3) | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F6beY7Qu4AJnpiCxFYT43%2FSquads%2520Apps.png&width=1248&dpr=4&quality=100&sign=e12de3e9&sv=2)

Apps section allows users to interact with the featured protocols and dapps directly from their Squad.

Apps are using Squads iframe adapter, allowing to connect to featured protocols with a multisig as one would do with a traditional wallet. Each action within the App triggers a transaction to be approved and executed by the Squad owners.

**Currently the following Apps are available to users:**

1.  PsyFinance
    
2.  Solend
    
3.  Realms
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FOSV4jzxeRUQeWITGCJvb%2FApps%25201%2520%281%29.png&width=768&dpr=4&quality=100&sign=8dedbd08&sv=2)

Apps tab

**To connect to the App:**

1.  Click on the featured App to open it inside your Squad.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2Fl10ZfnBnfxskliQOMqQf%2FApps%25202%2520%281%29.png&width=768&dpr=4&quality=100&sign=5576fd34&sv=2)

PsyFinance App

2\. Click "Select wallet" button, your Squad vault will automatically appear in the selection list.

3\. Once the wallet is connected, you can perform actions inside the App. Any action will trigger a transaction that will appear in the "Transactions" tab.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FBSSirFAqdDU2I3a11Ti8%2F3.%2520TX%2520example.png&width=768&dpr=4&quality=100&sign=67c4798e&sv=2)

Transaction example

[PreviousCreators](https://docs.squads.so/main/squads-legacy/navigating-your-squad/creators)
[NextOwners and Settings](https://docs.squads.so/main/squads-legacy/navigating-your-squad/owners-and-settings)

Last updated 1 year ago

---

# Dialect | Squads Legacy (v3) | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FEb8u8Dis5oAWogBuOaYz%2FSquads%2520Docs-1.png&width=1248&dpr=4&quality=100&sign=870dc010&sv=2)

[](https://docs.squads.so/main/squads-legacy/integrations/dialect#what-is-dialect)

What is Dialect?


--------------------------------------------------------------------------------------------------------

Dialect is a smart messaging protocol for dApp notifications and wallet-to-wallet chat. Dialect is powering notifications and messaging for over 15 protocols on Solana.

[](https://docs.squads.so/main/squads-legacy/integrations/dialect#how-do-squads-protocol-users-benefit-from-this-integration)

How do Squads Protocol users benefit from this integration?


----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

We've integrated Dialect to enable web3 notifications directly within the Squads Protocol interface. Squad owners can opt-in to receive notifications regarding proposal updates, confirmation threshold changes, and owner additions/removals from a Squad. For more on Dialect, see their website [here](https://www.dialect.to/)
.

[](https://docs.squads.so/main/squads-legacy/integrations/dialect#how-to-set-up-notifications)

How to set up notifications?


--------------------------------------------------------------------------------------------------------------------------------

Users can receive on-chain notifications about actions in the Squads they are part of.

**To enable notifications:**

1.  Click on the "Bell" icon next to your wallet address.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F1kDdS37Gn46UaWdWE2Qs%2Fdialect%25201.png&width=768&dpr=4&quality=100&sign=6c8f3052&sv=2)

Dialect pop-up

2\. Click on "Sign Message" and sign the transaction in your wallet pop-up.

3\. Notifications will be appearing in the notifications feed.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FIc27iRePerbig6ymtVlR%2Fdialect%25202.png&width=768&dpr=4&quality=100&sign=9616401e&sv=2)

Notification feed

4\. You can also set up notifications for telegram and email in the settings.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FV4fhHvy5GFJSeu5wTpGs%2Fdialect%25203.png&width=768&dpr=4&quality=100&sign=b9333893&sv=2)

Notifications settings

[PreviousTensor](https://docs.squads.so/main/squads-legacy/integrations/tensor)
[NextBonfida](https://docs.squads.so/main/squads-legacy/integrations/bonfida)

Last updated 1 year ago

---

# Costs of using Squads | Squads Legacy (v3) | Squads Docs

### 

[](https://docs.squads.so/main/squads-legacy/frequently-asked-questions/costs-of-using-squads#how-much-does-it-cost-to-use-squads)

**How much does it cost to use Squads?**

Network fees can vary slightly depending on the action performed inside of a Squad. This happens due to differences in the weights of instructions, which require different spaces on the blockchain.

**Approximate** **network fees** for various actions inside Squads:

*   **Squads deployment fee -** 0.0025 - 0.0045 SOL depending on the initial amount of owners
    
*   **Sign transaction** - 0.000005 SOL
    
*   **Withdrawing SPL tokens** \- 0.0048 SOL
    
*   **Depositing SPL tokens** - 0.00001 SOL
    
*   **Depositing NFT** \- 0.00001 SOL
    
*   **Withdrawing NFT** - 0.005 SOL
    
*   **Add owner** \- 0.0057 SOL
    
*   **Remove owner** - 0.0050 SOL
    
*   **Change threshold** - 0.0050 SOL
    
*   **Add program** - 0.00301 SOL
    
*   **Buy NFT from Tensor** - 0.00298 SOL
    
*   **Rent NFT from the vault** - 0.00298 SOL
    
*   **Stake SOL with a validator** - 0.00976 SOL
    

[PreviousGeneral](https://docs.squads.so/main/squads-legacy/frequently-asked-questions/general)
[NextPDAs](https://docs.squads.so/main/squads-legacy/development/pdas)

Last updated 4 months ago

---

# Dashboard | Squads Legacy (v3) | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2Fn1YaZqkHXRRAQwVtS0Mp%2FSquads%2520Dashboard.png&width=1248&dpr=4&quality=100&sign=8a58b2bf&sv=2)

### 

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/dashboard#what-is-dashboard)

What is Dashboard?

Dashboard is the place where Squad owners can monitor all of their treasury and developer assets and can quickly access any of them in just one click.

### 

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/dashboard#what-can-i-monitor-with-it)

What can I monitor with it?

Dashboard consists of the following parts:

1.  **Vault** \- here you can see the total balance of your Squad and all SPL tokens currently inside your vault. (Learn more [Vault](https://docs.squads.so/main/squads-legacy/navigating-your-squad/vault)
    )
    
2.  **Managed assets -** here you can monitor all developer assets under your management:
    

a. Programs (learn more [Programs](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/programs)
)

b. Tokens (learn more [Token Manager](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/token-manager)
)

c. Validators (learn more [Validators](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/validators)
)

d. NFT collections (learn more [Creators](https://docs.squads.so/main/squads-legacy/navigating-your-squad/creators)
)

1.  **Transactions -** here you can see the number of active transactions and those waiting for execution. (Learn more [Transaction](https://docs.squads.so/main/squads-legacy/development/pdas/transaction)
    )
    
2.  **Info** - here you can find the information about your Squad threshold and when it was modified. It also provides you with the total number of owners in your Squad. (Learn more [Owners and Settings](https://docs.squads.so/main/squads-legacy/navigating-your-squad/owners-and-settings)
    )
    
3.  **Stake -** here you can see all of your staked assets (validator and liquid stake). (Learn more [Staking](https://docs.squads.so/main/squads-legacy/integrations/staking)
    )
    
4.  **NFT** - here you can see all of the collections and the number of NFTs you have in the NFT gallery. (learn more[NFTs](https://docs.squads.so/main/squads-legacy/navigating-your-squad/vault#nfts)
    )
    
5.  **"Learn more" section** - here you can explore additional content about platform features.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F92tzgL8vyfq5TbhyLJNq%2Fdashboard.jpg&width=768&dpr=4&quality=100&sign=e5f7133a&sv=2)

Dashboard tab

[PreviousCreate a Squad](https://docs.squads.so/main/squads-legacy/getting-started/create-a-squad)
[NextVault](https://docs.squads.so/main/squads-legacy/navigating-your-squad/vault)

Last updated 1 year ago

---

# Authorities | Squads Legacy (v3) | Squads Docs

Authority PDAs are responsible for signing the underlying CPIs executed by the multisig. Generally they should be seeded by a u32 starting from the default of 1 (the `authorityIndex`). The `authorityIndex` of a Transaction account will be used to generate the seeds necessary to perform the CPI. Most often you can simply use the `authorityIndex` of 1. For example, the Squads client uses an `authorityIndex` of 1 for all default PDAs (the vault, program upgrade authorities, etc).

Transactions must specify this `authorityIndex` upon creation, and all instructions attached to the Transaction should use the same authority PDA for any account that is designated as a signer.

_The_ `_authorityIndex_` _of 0 is reserved for internal multisig instructions, and should generally be avoided._

The Authority PDAs are derived as such:

Copy

    await anchor.web3.PublicKey.findProgramAddress([\
        anchor.utils.bytes.utf8.encode("squad"),\
        multisig.toBuffer(),\
        authorityIndex.toBuffer("le", 4),  // note authority index is an u32 (4 byte)\
        anchor.utils.bytes.utf8.encode("authority")\
    ], programId);

Note that the authorityIndex should be supplied to the function as a 4 byte little-endian buffer.

The format of deriving an authority is:

`["squad", multisig, authorityIndex, "authority"]`

[PreviousDerivation](https://docs.squads.so/main/squads-legacy/development/pdas/derivation)
[NextAnchor IDL](https://docs.squads.so/main/squads-legacy/development/anchor-idl)

---

# PDAs | Squads Legacy (v3) | Squads Docs

The PDAs used in Squads are interconnected and rigorously dependent on each other. The four core PDA types used in Squads are:

*   Multisig
    
*   Transaction
    
*   Instruction
    
*   [Authority](https://docs.squads.so/main/squads-legacy/development/authorities)
    

[PreviousCosts of using Squads](https://docs.squads.so/main/squads-legacy/frequently-asked-questions/costs-of-using-squads)
[NextMultisig](https://docs.squads.so/main/squads-legacy/development/pdas/multisig)

---

# Transactions | Squads Legacy (v3) | Squads Docs

Multisigs interact with the ecosystem via transactions. Transactions created for the multisig to act upon will have the following states: Draft, Active, ExecuteReady, Executed, Rejected, or Cancelled.

Each Transaction is ultimately executed by an authority PDA derived from the multisig. A transaction, regardless of how many instructions are attached to it, can only represent a single authority. Transactions are limited to having a maximum of 255 instructions.

[PreviousCreate a Multisig](https://docs.squads.so/main/squads-legacy/development/anchor-idl/create-a-multisig)
[NextCreate a Transaction](https://docs.squads.so/main/squads-legacy/development/anchor-idl/transactions/create-a-transaction)

---

# Coinflow | Squads Legacy (v3) | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F3dyg5qfHSJfaSiHBTs32%2FCoinflow.png&width=1248&dpr=4&quality=100&sign=e0005a07&sv=2)

Squads users can off-ramp assets directly to their bank accounts.

(Currently only for the US)

[](https://docs.squads.so/main/squads-legacy/integrations/coinflow#what-is-coinflow)

What is Coinflow?


-----------------------------------------------------------------------------------------------------------

Coinflow develops software bridging conventional finance & blockchain tech, enabling users to purchase digital assets & services using standard payment methods. With top-tier US bank collaborations, Coinflow provides instant 24/7 crypto off-ramping to user bank accounts.

[](https://docs.squads.so/main/squads-legacy/integrations/coinflow#how-to-off-ramp-assets-to-a-bank-account)

How to off-ramp assets to a bank account?


-----------------------------------------------------------------------------------------------------------------------------------------------------------

**To off-ramp assets to a business's bank account:**

1.  Navigate to the "Vault" tab and click on the "Off-ramp" button.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FaeenG1H4nQGcwMdvugJp%2Fvault%25209.png&width=768&dpr=4&quality=100&sign=27dac53f&sv=2)

Off-ramp feature

1.  Select "Business" in the pop-up.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F6hzsdJqubJSxnH08nxAw%2Fvault%252011.png&width=768&dpr=4&quality=100&sign=cea7af4c&sv=2)

Off-ramp feature

1.  Fill in the following info about your business:
    

*   Legal business name
    
*   US Tax ID number
    
*   Company website
    
*   Business address
    
*   Your name and e-mail
    

1.  Click submit. Coinflow will transfer funds to your bank account after processing your request.
    

**To off-ramp assets to your individual bank account:**

1.  Navigate to the vault tab and click on the "Off-ramp" button.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F6hzsdJqubJSxnH08nxAw%2Fvault%252011.png&width=768&dpr=4&quality=100&sign=cea7af4c&sv=2)

Off-ramp feature

1.  Select "Person" in the pop-up.
    
2.  Fill in the personal information:
    

*   Name and Last name
    
*   Address
    
*   Birthday
    
*   E-mail
    
*   Last 4 of SSN number
    

1.  Click "Complete verification". Coinflow will transfer funds to your bank account after processing your request.
    

[PreviousBonfida](https://docs.squads.so/main/squads-legacy/integrations/bonfida)
[NextGeneral](https://docs.squads.so/main/squads-legacy/frequently-asked-questions/general)

---

# Token Manager | Squads Legacy (v3) | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FICwMTbjDxXnawinljAf4%2FSquads%2520Token%2520Manager.png&width=1248&dpr=4&quality=100&sign=a80fa244&sv=2)

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/token-manager#overview)

Overview


-------------------------------------------------------------------------------------------------------------------

Users can mint, burn and manage authorities of their tokens inside the Squad using Token manager.

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/token-manager#how-to-create-a-token-from-a-squad)

How to create a token from a Squad?


------------------------------------------------------------------------------------------------------------------------------------------------------------------------

1.  Navigate to the "Token Manger" tab and click on the "+Add Token" button. Select the "Create Token" option inside the pop-up.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FJjtqLNj3xECs9onUgfo9%2FToken%25202.png&width=768&dpr=4&quality=100&sign=829df4ba&sv=2)

Add token pop-up

2\. Fill in the required data within the pop-up window. The data includes:

a. Token name

b. Token symbol

c. Token description (optional)

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FIU3sRWw8YcGcwJXnAI6z%2FToken%25204.png&width=768&dpr=4&quality=100&sign=dfbc8d3c&sv=2)

Add token pop-up

3\. Click "Next", insert token decimals and transaction description (optional), then click on the "Create" button to launch a transaction.

Please note that to create a new token, you will need a minimum of 0.003 SOL in your Squad vault to cover the cost of creating [ATA](https://spl.solana.com/associated-token-account)
 for this token.

4\. Your token will be created and appear inside the "Token Manager" tab upon transaction execution (more on transactions [here](https://docs.squads.so/main/squads-legacy/navigating-your-squad/transactions)
).

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/token-manager#how-to-mint-tokens-from-a-squad)

How to mint tokens from a Squad?


------------------------------------------------------------------------------------------------------------------------------------------------------------------

1.  Click on the "Token Manager" tab, locate the token which you would like to mint and click on the "Mint" button.
    
2.  Specify the amount of tokens you want to mint, insert a description (optional), and launch the transaction.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FeqThHkF4zlqY5lPsDqvc%2Ftoken%25208.png&width=768&dpr=4&quality=100&sign=dbe5a5e6&sv=2)

Transactions tab

3\. After the transaction has been executed, your token will appear in your Squad vault.

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/token-manager#how-to-burn-token-supply-from-a-squad)

How to burn token supply from a Squad?


------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

1.  Navigate to the "Token Manager" tab, locate the token which supply you want to burn and click on the "Burn" button.
    
2.  In the pop-up fill in the burn amount and insert the transaction description (optional). Click on the "Burn token" button to launch a transaction.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F8s2rKSM0NeDI2wzqKikp%2FToken%252010.png&width=768&dpr=4&quality=100&sign=32e52369&sv=2)

Burn Token pop-up

3\. The indicated token amount will be burned after the transaction has reached the confirmation threshold and been executed.

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/token-manager#how-to-transfer-token-authority-to-a-squad-and-from-it)

How to transfer token authority to a Squad and from it?


----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Users can transfer the token authority to the multisig if they already have the existing token. They can also transfer the token authority which belongs to the multisig to the external wallet at any time.

**To transfer the authority of an existing token to your multisig:**

1.  Navigate to the "Token Manager" tab. Click on the "+Add Token" button and select the "Transfer token authority to your Squad" option.
    
2.  Insert the current token authority address, copy and paste the code into your CLI. The CLI code should be run by the current authority. Then click “Change authority”.
    

**To transfer the token authority from your multisig:**

1.  Navigate to the "Token Manager" tab. Locate the token which authority you would like to transfer and click on the "Change Authority" button.
    
2.  Insert the new authority address and click "Transfer authority" to launch a transaction. The token authority will be transferred upon transaction execution.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F3g1YJ2hV2nEk542IuzRD%2Ftoken%252012.png&width=768&dpr=4&quality=100&sign=2e0cdb1d&sv=2)

Token authority transfer

[PreviousPrograms](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/programs)
[NextValidators](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/validators)

Last updated 2 years ago

---

# Loading the Program | Squads Legacy (v3) | Squads Docs

Before utilizing the Anchor methods associated with the Squads program, you'll need to instantiate the program. Ensure that you have properly setup an AnchorProvider, as well.

Copy

    const provider = new AnchorProvider(connection, wallet);
    // the squads-mpl program on both mainnet and devnet have the same address
    const squadsProgram = await Program.at("SMPLecH534NA9acpos4G6x7uf3LWbCAwZQE9e8ZekMu", provider);

[PreviousAnchor IDL](https://docs.squads.so/main/squads-legacy/development/anchor-idl)
[NextCreate a Multisig](https://docs.squads.so/main/squads-legacy/development/anchor-idl/create-a-multisig)

---

# Stakewiz | Squads Legacy (v3) | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F0xqLlTt3IUZH7ZCokUR9%2FSquads%2520Docs-1.png&width=1248&dpr=4&quality=100&sign=94099806&sv=2)

[](https://docs.squads.so/main/squads-legacy/integrations/staking/stakewiz#overview)

Overview


--------------------------------------------------------------------------------------------------

Users can stake their SOL holdings with the Solana Network validators directly from their Squad.

**To stake SOL:**

1.  Navigate to the "Staking" tab and select "Validator" section.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F6xUoRJkIm8zhnnlwssyX%2FValidator%25201.jpg&width=768&dpr=4&quality=100&sign=4694005c&sv=2)

"Validator" section

2\. Select the validator you wish to stake with and select the amount of SOL you want to stake. You can use a filter to rank the validators by the amount of SOL delegated to them, the estimated APY, or use the search field to find the specific validator.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FiOdkOiiJymqZ6ZAlkMys%2FValidator%25202.png&width=768&dpr=4&quality=100&sign=412d27e0&sv=2)

Stake pop-up

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. In this case, you will see your staked SOL amount in the "Activating" field on the dashboard.

3\. Insert the description (optional) and click on the "Stake" button and launch a transaction.

4\. Your SOL will start the activating period upon the transaction execution (more on the transactions [here](https://docs.squads.so/main/squads-legacy/navigating-your-squad/transactions)
). Once the new epoch starts, you will start earning rewards.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FzmuFDl6ii2qbN8U8AduC%2FValidator%25203.png&width=768&dpr=4&quality=100&sign=3ea9b39c&sv=2)

Transaction to stake SOL. Detailed view

5\. The "Staked" switcher in the "Validator" section allows you to check the staked SOL amount and ROI you are receiving.

**To unstake SOL:**

1.  Navigate to the "Staking" tab and select "Validator" section.
    
2.  Click on the "Staked" switcher and then click on the validator from which you wish to unstake your SOL.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FZTH3fEkS0ej953ajjzsm%2FValidator%25205.png&width=768&dpr=4&quality=100&sign=55d1b9f2&sv=2)

Unstake pop-up

3\. Insert the description (optional) and click the "Unstake" button to launch a transaction.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FkUFManPu76OTZkb4YhVm%2FValidator%25206.png&width=768&dpr=4&quality=100&sign=ce99320&sv=2)

Transaction to unstake SOL. Detailed view

Please note that due to the epoch's nature your unstaked SOL will be available for withdrawal after the deactivation.

4\. Your SOL will start the deactivation period upon the transaction execution (more on the transactions [here](https://docs.squads.so/main/squads-legacy/navigating-your-squad/transactions)
). The deactivation period finishes with the start of the new epoch.

5\. Once the deactivation period finishes, you will be able to withdraw your SOL. Navigate to the "Staked" switcher in the "Validator" section, click on the validator from which you are withdrawing the stake, and launch a transaction to complete the withdrawal.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F4JnX2W2CJF5F94AnZESy%2FValidator%25207.png&width=768&dpr=4&quality=100&sign=1cfd811d&sv=2)

Withdraw pop-up

6\. Your SOL will be returned to your vault upon transaction execution.

[PreviousStaking](https://docs.squads.so/main/squads-legacy/integrations/staking)
[NextJitoSOL](https://docs.squads.so/main/squads-legacy/integrations/staking/jitosol)

Last updated 1 year ago

---

# Derivation | Squads Legacy (v3) | Squads Docs

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FgzFA5dt3n4yGCFJV3wHG%2FPDA%2520Relationship.png&width=768&dpr=4&quality=100&sign=595e7d57&sv=2)

[PreviousInstruction](https://docs.squads.so/main/squads-legacy/development/pdas/instruction)
[NextAuthorities](https://docs.squads.so/main/squads-legacy/development/authorities)

---

# Executing | Squads Legacy (v3) | Squads Docs

Transactions that are in the `ExecuteReady` state can be executed by a multisig member. In order to execute the transaction, all of the accounts specified by the attached transactions instructions must be provided, and the parameter for the execute must include an array of accounts that map appropriately. For a more detailed explanation refer to the [README in the repository](https://github.com/Squads-Protocol/squads-mpl/blob/main/programs/squads-mpl/README.md#execute-a-mstransaction)
. Accounts should be ordered but also unique - this helps maximize the number of instructions that can be attached to a transaction.

The account array parameter provided should be a list that correlates to the attached accounts referenced in the execute method. The list should follow the format of \[ix1Account, ix1Program, ix1Account1, ix1Account2...\] where each array item is the index of the accounts given to the execute method.

To use our previous example of transferring out of the vault, we first fetch the transaction account and retrieve all the attached instructions.

Copy

    // retrieve the transaction we wish to execute
    const transactionAccount = await squadsProgram.account.msTransaction.fetch(transaction);
    
    // retrieve all of the attached instructions
    const instructions = await Promise.all([...new Array(transactionAccount.instructionIndex)].map(async (a, i) => {
            const ixIndex = new anchor.BN(i + 1);
            const [ix] = await getIxPDA(transaction, ixIndex, squadsProgram.programId);
            const ixAccount = await squadsProgram.account.msInstruction.fetch(ix);
            return {pubkey: ix, ixAccountData};
    }));
    

Now that we have all of the instruction accounts needed, we can put together our array list and specify the accounts needed for the execute method:

Copy

    // map all of the instructions and their keys into the following pattern
    // [ix, program, ...remaining_accounts]
    const ixKeys = instructions.map(({pubkey, ixAccountData}) => {
            const formattedKeys = ixAccount.keys.map((ixKey) => {
                return {
                    pubkey: ixKey.pubkey,
                    isSigner: false,
                    isWritable: ixKey.isWritable
                };
            });
    
            return [\
                {pubkey, isSigner: false, isWritable: false},\
                {pubkey: ixAccountData.programId, isSigner: false, isWritable: false},\
                ...formattedKeys\
            ];
            
        //squash them into a single list
        }).reduce((p, c) => p.concat(c), [])

Now we can remove duplicate keys and create the array parameter needed for the execute method:

Copy

    // these will be the accounts specified for the execute method
    //  [ix ix_account, ix program_id, key1, key2 ...]
    const keysUnique = ixKeys.reduce((prev, curr) => {
        const inList = prev.findIndex(a => a.pubkey.toBase58() === curr.pubkey.toBase58());
        // if its already in the list, and has same write flag
        if (inList >= 0 && prev[inList].isWritable === curr.isWritable) {
            return prev;
        } else {
            prev.push({pubkey: curr.pubkey, isWritable: curr.isWritable, isSigner: curr.isSigner});
            return prev;
        }
    }, []);
    
    // this will be the parameter for the execute
    const keyIndexArray = ixKeys.map(a => {
        return keysUnique.findIndex(k => {
            if (k.pubkey.toBase58() === a.pubkey.toBase58() && k.isWritable === a.isWritable) {
                return true;
            }
            return false;
        });
    });

Now you can call the execute method with the proper arguments:

Copy

    const executeIx = await program.methods.executeTransaction(Buffer.from(keyIndexArray))
            .accounts({multisig, transaction, member: wallet.publicKey})
            .instruction();
    
    // attache the formatted unique keys
    executeIx.keys = executeIx.keys.concat(keysUnique);
    
    // execute the transaction
    const execute = new anchor.web3.Transaction();
    execute.add(executeIx);
    wallet.sendAndConfirm(execute);

[PreviousApprove / Reject a Transaction](https://docs.squads.so/main/squads-legacy/development/anchor-idl/transactions/approve-reject-a-transaction)
[NextSDK](https://docs.squads.so/main/squads-legacy/development/sdk)

---

# Create a Multisig | Squads Legacy (v3) | Squads Docs

To create a multisig, first derive the address. The address is technically a [PDA](https://docs.solana.com/developing/programming-model/calling-between-programs#program-derived-addresses)
, and can be derived based off of the `createKey.` The `createKey` can be any public key (wallet, random, etc.), as long as its supplied as a [PublicKey](https://coral-xyz.github.io/anchor/ts/classes/web3.PublicKey.html)
 type.

Additionally, the `create` method will need an approval threshold and a list of keys to act as the members of the multisig (signers).

For example, to create a multisig based on a user's wallet address or a random key:

Copy

     // using a wallet to seed the multisig & address
     const createKey = wallet.publicKey;
     // or
     const createKey = anchor.web3.Keypair.generate().publicKey;
     
     // list of members/keys
     const membersList = [wallet.publicKey, otherKey1, otherKey2];
     // threshold
     const threshold = 2;
     
     // the multisig pda
     const multisig = await anchor.web3.PublicKey.findProgramAddress(
        anchor.utils.bytes.utf8.encode("squad"),
        createKey.toBuffer(),
        anchor.utils.bytes.utf8.encode("multisig")
     );
     
     // adjust to fit your Anchor provider or if using React useAnchorWallet() hook
     const creator = wallet.publicKey;
     
     // this will create a multisig with a threshold of 2/3, with three members
     await squadsProgram.methods.create(threshold, createKey, memberList)
              .accounts({
                 multisig,
                 creator,
               })
               .rpc();

Read the [section on PDAs](https://docs.squads.so/main/squads-legacy/development/pdas/multisig)
 for more information about the multisig PDA.

[PreviousLoading the Program](https://docs.squads.so/main/squads-legacy/development/anchor-idl/loading-the-program)
[NextTransactions](https://docs.squads.so/main/squads-legacy/development/anchor-idl/transactions)

---

# Anchor IDL | Squads Legacy (v3) | Squads Docs

The Squads MPL is built in Anchor, and can be found in the [Anchor Program Registry](https://www.apr.dev/program/SMPLecH534NA9acpos4G6x7uf3LWbCAwZQE9e8ZekMu)
. Developers can interact with the program using the standard TypeScript functionality outlined in the [Anchor TS Doc](https://coral-xyz.github.io/anchor/ts/index.html)
.

To get started, first make sure that the latest version of Anchor is added to your project.

Copy

    // if  using yarn
    yarn add @project-serum/anchor
    // if using npm
    npm install @project-serum/anchor

[PreviousAuthorities](https://docs.squads.so/main/squads-legacy/development/authorities)
[NextLoading the Program](https://docs.squads.so/main/squads-legacy/development/anchor-idl/loading-the-program)

---

# Vault | Squads Legacy (v3) | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FbfXjEXmWfXaLvrBOzsSh%2FSquads%2520Vault.png&width=1248&dpr=4&quality=100&sign=d102ea0&sv=2)

### 

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/vault#overview)

Overview

The "Vault" is at the core of every Squad and it allows:

*   any connected wallet to deposit fungible tokens and NFTs;
    
*   any owner to initiate a transaction to send tokens and NFTs to any Solana address which will trigger a transaction for the Squad to confirm;
    
*   any owner to save wallet addresses in their address book by contact names;
    
*   any owner to initiate a swap of Vault assets which will trigger a transaction for the Squad to confirm;
    
*   any owner to stake SOL from the Squad;
    
*   any owner to purchase and rent NFTs from the Squad;
    
*   anyone to view the Vault balances and recent transactions of the Squad;
    
*   anyone to copy an address of a Squad.
    

[https://youtu.be/gH1LCnnQ83cyoutu.be](https://youtu.be/gH1LCnnQ83c)

### 

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/vault#assets)

**Assets**

Squads support any SPL (Solana Program Library) tokens, which can be deposited into a Squad via a deposit button.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FrYzp2mQvqH8N0Je6O5Wp%2Fvault%25201.png&width=768&dpr=4&quality=100&sign=81141031&sv=2)

Squad vault

### 

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/vault#nfts)

**NFTs**

Squads support the storage of NFTs (Non-fungible tokens) in an NFT gallery. An owner can deposit up to 20 NFTs in one transaction. Withdrawals are limited to 15 NFTs per one transaction.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F1F4Zeyl1tSEUT9Um6knR%2Fvault%25202.png&width=768&dpr=4&quality=100&sign=dd420c69&sv=2)

NFT gallery

Users can switch their NFT gallery to the list view by clicking on the switcher next to the "Search" field.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F0VewmCtreeR2x7yWu3uD%2Fvault%25202.1.png&width=768&dpr=4&quality=100&sign=ce466e1f&sv=2)

NFT list view

### 

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/vault#recent-transactions)

Recent Transactions

All transactions which are done within a Squad will appear in the recent transactions tab.

The information about them **will include**:

*   Asset
    
*   Type (Deposit, send, buy)
    
*   Address of the wallet that performed the transaction
    
*   Date
    
*   Amount
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F8HTiYdlpEk4XxgCDFVKT%2Fvault%25203.png&width=768&dpr=4&quality=100&sign=e8c0113c&sv=2)

Recent transactions section

### 

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/vault#contacts)

Contacts

Any owner of a Squad can add a contact to a contact book to simplify the process of the funds withdrawal.

**To do this:**

1.  Click on the "plus" button in the contact section of the vault.
    
2.  Insert a name and public key.
    
3.  Click on the "approve" icon and sign a transaction in the wallet pop-up.
    
4.  To delete an address click on the "bin" icon and sign a transaction in the wallet pop-up.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2Fk27SxZPdeahBOYlD4jfq%2Fvault%25204.png&width=768&dpr=4&quality=100&sign=4a8e5bf4&sv=2)

Contacts section

[PreviousDashboard](https://docs.squads.so/main/squads-legacy/navigating-your-squad/dashboard)
[NextTransactions](https://docs.squads.so/main/squads-legacy/navigating-your-squad/transactions)

Last updated 1 year ago

---

# Multisig | Squads Legacy (v3) | Squads Docs

#### 

[](https://docs.squads.so/main/squads-legacy/development/pdas/multisig#multisig-addresses-and-accounts)

Multisig Addresses & Accounts

Each multisig created is referenced by an address that is a PDA. The PDA is derived from a `createKey` which is also saved in the multisig account for later derivation. The `createKey` can be random, or even a wallet's public key, but it is important to note this `createKey` so one can easily reference or fetch multisigs for later use.

The Multisig address is derived via the Solana Web3 function `findProgramAddress`, using the following seeds and format:

Copy

    anchor.web3.PublicKey.findProgramAddress([\
        anchor.utils.bytes.utf8.encode("squad"),\
        createKey.toBuffer(),\
        anchor.utils.bytes.utf8.encode("multisig")\
    ], programId)

The format for multisig PDAs is:

Copy

    ["squad", createKey, "multisig"]

For a more in-depth look at what data is being store on-chain for a multisig, you can inspect the [Ms struct in the Squads MPL repo](https://github.com/Squads-Protocol/squads-mpl/blob/main/programs/squads-mpl/src/state/ms.rs#L7)
.

[PreviousPDAs](https://docs.squads.so/main/squads-legacy/development/pdas)
[NextTransaction](https://docs.squads.so/main/squads-legacy/development/pdas/transaction)

---

# Instruction | Squads Legacy (v3) | Squads Docs

Instruction PDAs reference an on-chain account that stores information about instructions that are attached to a Transaction.

As with transaction PDAs, instruction PDAs also expect a numeric index relating to the number of instructions attached to a transaction. Every time an instruction is attached to a transaction, the `instructionIndex` will be bumped up by one. This provides a simple way to collect all instructions associated with a specific transaction. Deriving an instruction PDA requires a transaction PDA and the `transactionIndex`.

Copy

    await anchor.web3.PublicKey.findProgramAddress([\
        anchor.utils.bytes.utf8.encode("squad"),\
        transaction.toBuffer(),\
        instructionIndex.toBuffer("le", 1),  // note instruction index is an u8 (1 byte)\
        anchor.utils.bytes.utf8.encode("instruction")\
    ], programId);

Be sure to provide the `instructionIndex` as a single byte little-endian buffer.

The instruction PDA derivation format is as follows:

Copy

    ["squad", transaction, instructionIndex, "instruction"]

[PreviousTransaction](https://docs.squads.so/main/squads-legacy/development/pdas/transaction)
[NextDerivation](https://docs.squads.so/main/squads-legacy/development/pdas/derivation)

---

# Validators | Squads Legacy (v3) | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F4qmiqyh1eCGdYEdA5stG%2FSquads%2520Validators.png&width=1248&dpr=4&quality=100&sign=ffec3271&sv=2)

Users are able to manage validators directly from their Squad. The management of validators includes changing commissions, withdrawing rewards, and changing authorities.

### 

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/validators#adding-validators)

**Adding validators**

Users can transfer their validator withdraw authority to a Squad.

[https://www.youtube.com/watch?v=x7pY\_GdN4Wwwww.youtube.com](https://www.youtube.com/watch?v=x7pY_GdN4Ww)

**To transfer validator withdraw authority to a Squad:**

1.  Navigate to the "Validators" tab and click on the "+Add Validator" button.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FkhwfBnbEdGsstRkJeU78%2FValidators%25201.png&width=768&dpr=4&quality=100&sign=ddf37f20&sv=2)

Validators tab

2\. Fill out the name and validator ID and click on the "Next" button.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FvsSk0L04EMTvKYCerJ8k%2FValidators%25202.png&width=768&dpr=4&quality=100&sign=408bd267&sv=2)

Add a validator pop-up

3\. Set the validator withdraw authority and click on "Verify Authority". You can also transfer the authority using SAT (Safe Authority Transfer).

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F9yrjHuFrM9Ite6ccvmZK%2FValidators%25203.png&width=768&dpr=4&quality=100&sign=c3ca50b&sv=2)

Add a validator pop-up

For users who would want to perform the authority transfer in a safer way there is an option to make a Safe Authority Transfer (SAT).

SAT creates a transaction in the Squad, which needs to be signed by both Squad's Vault PDA and the current authority holder.

**To perform a Safe Authority Transfer (SAT):**

1.  Add your CLI wallet to the Squad. Check the [Owners and Setting](https://docs.squads.so/main/squads-legacy/navigating-your-squad/owners-and-settings)
     page for more info on how to add members.
    
2.  Click on the "Create SAT" button.
    
3.  Enter a description (optional) and run a transaction inside your Squad.
    
4.  Once the transaction meets the confirmation threshold, execute it with your CLI wallet, which you added to your Squad. More on transactions [here](https://docs.squads.so/main/squads-legacy/navigating-your-squad/transactions)
    .
    
5.  After the transaction is executed, the withdraw authority will be transferred to your Squad.
    

A validator withdraw authority can be reassigned to a different address via the UI or [Squads CLI tool](https://www.npmjs.com/package/@sqds/cli)
 after it has been transferred to a Squad.

### 

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/validators#managing-validators)

**Managing validators**

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2Fgp8362mCYCldNgc1hzVX%2FValidators%25204.png&width=768&dpr=4&quality=100&sign=d5acb85a&sv=2)

Validator pop-up

**To change commission:**

1.  Navigate to the "Validators" tab and select the validator which you would like to manage.
    
2.  Click on the "Change commission" button.
    
3.  Insert the new commission percentage, insert the description (optional) and launch a transaction.
    
4.  The validator commission will be updated upon transaction execution.
    

**To withdraw rewards:**

1.  Navigate to the "Validators" tab and select the validator from which you would like to withdraw rewards.
    
2.  Click on the "Withdraw Rewards" button.
    
3.  Insert the description (optional) and click on the "Withdraw" button to launch a transaction.
    
4.  Your rewards will appear in your Squad vault upon transaction execution.
    

**To change authority:**

1.  Navigate to the "Validators" tab and select the validator which authority you would like to change.
    
2.  Click on the "Change Authority" button.
    
3.  Insert the new address to which you would like to pass the authority. Insert the description (optional).
    
4.  Click on the "Initiate a transaction" button and launch a transaction. The authority will be transferred to the newly assigned address upon transaction execution.
    

Users can also leverage [Squads CLI tool](https://www.npmjs.com/package/@sqds/cli)
 to transfer validator withdraw authority from their Squad.

[PreviousToken Manager](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/token-manager)
[NextTX Builder](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/tx-builder)

---

# Transaction | Squads Legacy (v3) | Squads Docs

Transaction PDAs reference accounts where the transaction data is stored. Transaction accounts contain various low level information like the number of approvals, rejections, the transaction authority, etc.

Transaction PDAs are derived from the multisig PDA and the transaction index. The transaction index is an easy way to derive a list of transactions related to the multisig. When a new transaction account is created, the multisig will bump up the transaction index by one. The current transaction index can be found in the multisig account. A newly created multisig will have a starting transaction index of 0.

To find a transaction PDA using the Anchor Web3 library:

Copy

    await anchor.web3.PublicKey.findProgramAddress([\
        anchor.utils.bytes.utf8.encode("squad"),\
        multisig.toBuffer(),\
        transactionIndex.toBuffer("le", 4),\
        anchor.utils.bytes.utf8.encode("transaction")\
    ], programId);

Note that in the example, `transactionIndex` is supplied as a BN. You are free to supply the transaction index anyway you prefer, as long as the value provided to `findProgramAddress` is a little endian 4 byte buffer.

The format for deriving transaction PDAs is as follows:

Copy

    ["squad", multisig, transactionIndex, "transaction"]

[PreviousMultisig](https://docs.squads.so/main/squads-legacy/development/pdas/multisig)
[NextInstruction](https://docs.squads.so/main/squads-legacy/development/pdas/instruction)

---

# SDK | Squads Legacy (v3) | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FKoHOqQLymzbeVh7XH02t%2FSquads%2520SDK.png&width=1248&dpr=4&quality=100&sign=a96fb3a8&sv=2)

[](https://www.npmjs.com/package/@sqds/sdk)

![Cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FCRHd8Db5N8glaHfziswF%2FFrame%252072.png&width=490&dpr=4&quality=100&sign=f0aa46d&sv=2)

**Squads SDK**

You can find Squads SDK [here](https://www.npmjs.com/package/@sqds/sdk)
.

[](https://github.com/squads-protocol/sdk-examples)

![Cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FjrzDuP3nn1rF6Zsbqbvq%2FFrame%252071.png&width=490&dpr=4&quality=100&sign=c9847247&sv=2)

**SDK Examples**

You can find Squads SDK examples [here](https://github.com/squads-protocol/sdk-examples)
.

[](https://github.com/Squads-Protocol/squads-mpl/tree/main/sdk)

![Cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FjrzDuP3nn1rF6Zsbqbvq%2FFrame%252071.png&width=490&dpr=4&quality=100&sign=c9847247&sv=2)

**SDK Readme**

You can find SDK Readme [here](https://github.com/Squads-Protocol/squads-mpl/tree/main/sdk)
.

[PreviousExecuting](https://docs.squads.so/main/squads-legacy/development/anchor-idl/transactions/executing)

Last updated 1 year ago

---

# SolBlaze | Squads Legacy (v3) | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FkGKmCibU5qjakHQfLX3M%2FSolBlaze.png&width=1248&dpr=4&quality=100&sign=eb0140db&sv=2)

[](https://docs.squads.so/main/squads-legacy/integrations/staking/solblaze#overview)

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.

[](https://docs.squads.so/main/squads-legacy/integrations/staking/solblaze#what-is-bsol)

What is bSOL?


-----------------------------------------------------------------------------------------------------------

Users can stake their SOL holdings without locking them up with SolBlaze liquid staking. By staking with SolBlaze users receive bSOL which is issued 1:1 to their initial stake. bSOL then can be used to earn additional rewards through DeFI protocols, which can be accessed directly from the Squad via the ["Apps"](https://docs.squads.so/main/squads-legacy/navigating-your-squad/apps)
 section.

[](https://docs.squads.so/main/squads-legacy/integrations/staking/solblaze#how-to-stake-with-solblaze-stake-pool)

How to stake with SolBlaze Stake Pool?


-------------------------------------------------------------------------------------------------------------------------------------------------------------

**To stake SOL:**

1.  Navigate to the "Staking" tab and select "Liquid" section.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F21znfo59LozoG7hN63ye%2FStaking%2520liquid.jpg&width=768&dpr=4&quality=100&sign=83d4db2a&sv=2)

Liquid staking 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.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FmOuG2nztGmwjvJ3VfYVK%2Fstaking%2520liquid%2520solblaze.jpg&width=768&dpr=4&quality=100&sign=38c0373c&sv=2)

SolBlaze liquid staking pop-up

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](https://docs.squads.so/main/squads-legacy/navigating-your-squad/transactions)
) and will appear in the vault as the bSOL. Once the new epoch starts, you will start earning rewards.

[](https://docs.squads.so/main/squads-legacy/integrations/staking/solblaze#how-to-unstake-from-solblaze-stake-pool)

How to unstake from SolBlaze Stake Pool?


-----------------------------------------------------------------------------------------------------------------------------------------------------------------

**To unstake SOL:**

1.  Navigate to the "Staking" tab.
    
2.  Click on the "SolBlaze stake pool" block in the "Liquid" section.
    
3.  Click on the "Unstake" switcher and select the amount you wish to unstake.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FwgRBeKiuP6J3R5to0Opn%2Fstaking%2520liquid%2520solblaze%2520Unstake.jpg&width=768&dpr=4&quality=100&sign=4576396a&sv=2)

SolBlaze liquid staking pop-up

Please note that when unstaking you will receive a stake account in your custody, viewable in your Squad under the "Staked" switcher in the "Validator" section. Once in your Squad, you will need to manually deactivate the stake account.

4\. Launch the transaction to unstake, after the transaction is approved and executed you will see a new staked account appearing under the "Staked" switcher in the "Validator" section. You have now finished the withdrawal from the stake pool and need to unstake your SOL from the validator.

5\. Click on the "Staked" switcher in the "Validator" section and select the validator you wish to unstake from. Launch a transaction to unstake your SOL. Your SOL will be unstaked upon the transaction execution.

Please note that due to the epoch's nature your unstaked SOL will be available for withdrawal after the deactivation.

6\. Your SOL will start the deactivation period after it is unstaked. The deactivation period finishes with the start of the new epoch.

7\. Once the deactivation period finishes, you will be able to withdraw your SOL. Click on the "Staked" switcher inside the "Validator" section, click on the validator from which you are withdrawing the stake, and launch a transaction to complete the withdrawal.

8\. Once you execute the withdrawal transaction, your SOL will be displayed inside your vault.

[PreviousMarinade](https://docs.squads.so/main/squads-legacy/integrations/staking/marinade)
[NextSwap](https://docs.squads.so/main/squads-legacy/integrations/swap)

Last updated 1 year ago

---

# Approve / Reject a Transaction | Squads Legacy (v3) | Squads Docs

Active transactions can be voted on by the multisig key members to either approve or reject the transaction.

To approve a transaction, you can utilize the following:

Copy

    // where member is the wallet signing as a multisig member
    const member = wallet.publicKey;
    
    await program.methods.approveTransaction()
              .accounts({
                  multisig,
                  transaction,
                  member
               })
               .rpc();

Similarly, in order to reject a transaction, utilize the following:

Copy

    // where member is the wallet signing as a multisig member
    const member = wallet.publicKey;
    
    await program.methods.rejectTransaction()
            .accounts({
                 multisig,
                 transaction,
                 member
             })
             .rpc();

[PreviousActivating a Transaction](https://docs.squads.so/main/squads-legacy/development/anchor-idl/transactions/activating-a-transaction)
[NextExecuting](https://docs.squads.so/main/squads-legacy/development/anchor-idl/transactions/executing)

---

# Create a Transaction | Squads Legacy (v3) | Squads Docs

To create a transaction for the multisig to act upon first derive a PDA for the transaction. The transaction PDA is used to reference the account created, and will store some basic information about the transaction.

In addition to the PDA, creating a transaction also requires and authority index.

A complete example to create a new Transaction with the expected `transactionIndex`

Copy

    // fetch the multisig
    const multisigAccount = await squadsProgram.account.ms.fetch(multisig);
    
    // get the next expected transactionIndex
    const transactionIndex = new anchor.BN(multisigAccount.transactionIndex + 1);
    
    // get the transaction PDA
    const transaction = await anchor.web3.PublicKey.findProgramAddress(
        anchor.utils.bytes.utf8.encode("squad"),
        multisig.toBuffer(),
        transactionIndex.toBuffer("le", 4), // or .toArrayLike(Buffer, "le", 4) 
        anchor.utils.bytes.utf8.encode("transaction")
    );
    
    // get the public key of the payer/creator
    const creator = wallet.publicKey;
    
    await program.methods.createTransaction(1) //using authorityIndex of 1
       .accounts({
           multisig,    // the multisig PDA
           transaction, // the transaction PDA
           creator // the creator/payer of the transaction acccount
        })
        .rpc();

After being created, the transaction will remain in a `Draft` status, until it is activated by the member key that created it.

Refer to the [Transaction PDA section](https://docs.squads.so/main/squads-legacy/development/pdas/transaction)
 for more information about deriving the transaction PDA and [the Authority section](https://docs.squads.so/main/squads-legacy/development/authorities)
 for information about how authorities function within Squads.

[PreviousTransactions](https://docs.squads.so/main/squads-legacy/development/anchor-idl/transactions)
[NextAdding Instructions](https://docs.squads.so/main/squads-legacy/development/anchor-idl/transactions/adding-instructions)

---

# What is a multisig | Squads Docs

A multisig is a non-custodial solution where control over assets is not exercised by a single private key, but rather by multiple private keys. It can be thought of as a safe that requires multiple unique keys to open it and move the assets. That means that even if one of the keys is compromised, the assets remain secure (no single point of failure).

Squads Protocol, the autonomous finance layer on Solana, is a collection of onchain smart accounts. These smart accounts are what power Squads Multisig.

Multisigs are the most widely adopted use case of smart accounts. They have been around since the early days of Bitcoin and are widely used for the purposes of self-custody of crypto assets across blockchains.

Every Squad is a programmable multisig wallet at its core, which ensures that any transaction or action taken within Squads requires the approval of multiple team members. As a result, the risk of unauthorized or malicious activity is greatly reduced, as it becomes impossible for a single member to access and manipulate funds or trigger harmful transactions to the funds held within the multisig.

On top of that, multi-signature technology serves as a consensus mechanism allowing teams to make decisions over their treasury (tokens, NFTs) and developer assets (programs, tokens, validators) together in a decentralized manner.

[PreviousWelcome to Squads Multisig](https://docs.squads.so/main)
[NextWho we are - Squads Labs](https://docs.squads.so/main/basics/who-we-are-squads-labs)

Last updated 6 months ago

---

# Adding Instructions | Squads Legacy (v3) | Squads Docs

After creating a transaction it will be in the "Draft" status which allows the creator of the Transaction to attach one or multiple instructions.

Similarly to creating a transaction, each instruction attached to a transaction will have its corresponding data saved in an account represented by an [instruction PDA](https://docs.squads.so/main/squads-legacy/development/pdas/instruction)
.

Attaching an instruction will automatically bump up the instructionIndex, so when attaching an instruction ensure that the supplied instruction PDA is derived correctly (instructionIndex + 1).

Here is an example of creating a transaction and attaching an instruction, which will withdraw 1 SOL from the vault (authority) to a destination address:

Copy

    // fetch the multsig account to get the TX index
    const multisigAccount = await squadsProgram.account.fetch(multisig);
    
    // bump up the transactionIndex by 1 to seed the new tx address
    const transactionIndex = new anchor.BN(multsigAccount.transactionIndex + 1);
    // find the tx address/pda for the to-be-created transaction
    const [transaction] = await anchor.web3.PublicKey.findProgramAddress([\
        anchor.utils.bytes.utf8.encode("squad"),\
        multisig.toBuffer(),\
        transactionIndex.toBuffer("le", 4),\
        anchor.utils.bytes.utf8.encode("transaction")\
    ], squadsProgram.programId);
    
    // create the transaction account with the authorityIndex of 1
    const createIx = await program.methods.createTransaction(1)
        .accounts({
            multisig,
            transaction,
            creator: wallet.publicKey
        })
        .rpc();
    
    // use instructionIndex = 1, since this is the first and only ix
    const instructionIndex = new anchor.BN(1);
    // get the instruction address / PDA
    const [instruction] = await anchor.web3.PublicKey.findProgramAddress([\
        anchor.utils.bytes.utf8.encode("squad"),\
        transaction.toBuffer(),\
        instructionIndex.toBuffer("le", 1),\
        anchor.utils.bytes.utf8.encode("instruction")\
    ], squadsProgram.programId);
    
    // find the authority for the authorityIndex = 1
    const authorityIndex = anchor.BN(1);
    const [authority] = await anchor.web3.PublicKey.findProgramAddress([\
        anchor.utils.bytes.utf8.encode("squad"),\
        multisig.toBuffer(),\
        authorityIndex.toBuffer("le", 4),  // note authority index is an u32 (4 byte)\
        anchor.utils.bytes.utf8.encode("authority")\
    ], squadsProgram.programId);
    
    // define the instruction to withdraw funds from the authority/vault
    // and supply the authority
    const withdrawIx = anchor.web3.SystemProgram.transfer({
        fromPubkey: authority,
        lamports: anchor.web3.LAMPORTS_PER_SOL,
        toPubkey: destination // public key of where to send the SOL
    });
    
    // add the instruction to the transaction, using the withdrawIx as a parameter
    await program.methods.addInstruction(withdrawIx)
        .accounts({
            multisig,
            transaction,
            instruction,
            creator: wallet.publicKey
        })
        .rpc();
    

We now have a new transaction, with a single instruction attached to it.

[PreviousCreate a Transaction](https://docs.squads.so/main/squads-legacy/development/anchor-idl/transactions/create-a-transaction)
[NextActivating a Transaction](https://docs.squads.so/main/squads-legacy/development/anchor-idl/transactions/activating-a-transaction)

---

# JitoSOL | Squads Legacy (v3) | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F4UkT6j7llqzs4iq48dMd%2FSquads%2520Docs%2520%281%29.png&width=1248&dpr=4&quality=100&sign=a5d7d607&sv=2)

[](https://docs.squads.so/main/squads-legacy/integrations/staking/jitosol#overview)

Overview


-------------------------------------------------------------------------------------------------

Users can deposit their SOL holdings into Jito stake pool, which lets them earn staking rewards with the additional returns for MEV redistribution.

[](https://docs.squads.so/main/squads-legacy/integrations/staking/jitosol#what-is-jitosol)

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.

[](https://docs.squads.so/main/squads-legacy/integrations/staking/jitosol#what-is-mev)

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.

[](https://docs.squads.so/main/squads-legacy/integrations/staking/jitosol#how-to-stake-with-jito-stake-pool)

How to stake with Jito Stake Pool?


----------------------------------------------------------------------------------------------------------------------------------------------------

**To stake SOL:**

1.  Navigate to the "Staking" tab and select "Liquid" section.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F21znfo59LozoG7hN63ye%2FStaking%2520liquid.jpg&width=768&dpr=4&quality=100&sign=83d4db2a&sv=2)

Liquid staking 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.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FEKaAA3JXWIPqC90HNOfi%2Fstaking%2520liquid%2520jito.jpg&width=768&dpr=4&quality=100&sign=1b1f3593&sv=2)

Jito liquid staking pop-up

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](https://docs.squads.so/main/squads-legacy/navigating-your-squad/transactions)
) and will appear in the vault as the JitoSOL. Once the new epoch starts, you will start earning rewards.

[](https://docs.squads.so/main/squads-legacy/integrations/staking/jitosol#how-to-unstake-sol)

How to unstake SOL?


----------------------------------------------------------------------------------------------------------------------

**To unstake SOL:**

1.  Navigate to the "Liquid" section inside the "Staking" tab.
    
2.  Click on the "Jito stake pool" block.
    
3.  Click on the "Unstake" switcher and select the amount you wish to unstake.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FV29QeGGeeGFjm0Z8wrl4%2Fstaking%2520liquid%2520jito%2520Unstake.jpg&width=768&dpr=4&quality=100&sign=22063c2a&sv=2)

Jito liquid unstaking pop-up

Please note that when unstaking you will receive a stake account in your custody, viewable in your Squad under the "Staked" switcher in the "Validator" section. Once in your Squad, you will need to manually deactivate the stake account.

4\. Launch the transaction to unstake, after the transaction is approved and executed you will see a new staked account appearing under the "Staked" switcher in the "Validator" section. You have now finished the withdrawal from the stake pool and need to unstake your SOL from the validator.

5\. Click on the "Staked" switcher in the "Validator" section and select the validator you wish to unstake from. Launch a transaction to unstake your SOL. Your SOL will be unstaked upon the transaction execution.

Please note that due to the epoch's nature your unstaked SOL will be available for withdrawal after the deactivation.

6\. Your SOL will start the deactivation period after it is unstaked. The deactivation period finishes with the start of the new epoch.

7\. Once the deactivation period finishes, you will be able to withdraw your SOL. To do this click on the "Staked" switcher inside the "Validator" section, click on the validator from which you are withdrawing the stake, and launch a transaction to complete the withdrawal.

8\. Once you execute the withdrawal transaction, your SOL will be displayed inside your vault.

[PreviousStakewiz](https://docs.squads.so/main/squads-legacy/integrations/staking/stakewiz)
[NextLido](https://docs.squads.so/main/squads-legacy/integrations/staking/lido)

Last updated 1 year ago

---

# Marinade | Squads Legacy (v3) | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FboxggfD5emNQjttUmDVa%2FMarinade.png&width=1248&dpr=4&quality=100&sign=9e7e593e&sv=2)

[](https://docs.squads.so/main/squads-legacy/integrations/staking/marinade#overview)

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.

[](https://docs.squads.so/main/squads-legacy/integrations/staking/marinade#what-is-msol)

What is mSOL?


-----------------------------------------------------------------------------------------------------------

Marinade.Finance 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 directly from the Squad via the ["Apps"](https://docs.squads.so/main/squads-legacy/navigating-your-squad/apps)
 section.

[](https://docs.squads.so/main/squads-legacy/integrations/staking/marinade#how-to-stake-with-marinade-stake-pool)

How to stake with Marinade Stake Pool?


-------------------------------------------------------------------------------------------------------------------------------------------------------------

**To stake SOL:**

1.  Navigate to the "Staking" tab and select "Liquid" section.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F21znfo59LozoG7hN63ye%2FStaking%2520liquid.jpg&width=768&dpr=4&quality=100&sign=83d4db2a&sv=2)

Liquid staking 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.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FrpEOFVPCaPaGHxfX9ce7%2Fstaking%2520liquid%2520marinade.jpg&width=768&dpr=4&quality=100&sign=d0849cff&sv=2)

Marinade liquid staking pop-up

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](https://docs.squads.so/main/squads-legacy/navigating-your-squad/transactions)
) and will appear in the vault as the mSOL. Once the new epoch starts, you will start earning rewards.

[](https://docs.squads.so/main/squads-legacy/integrations/staking/marinade#how-to-unstake-from-marinade-stake-pool)

How to unstake from Marinade Stake Pool?


-----------------------------------------------------------------------------------------------------------------------------------------------------------------

**To unstake SOL:**

1.  Navigate to the "Staking" tab, click on the "Marinade stake pool" block and select "Unstake" switcher, then launch a transaction.
    
2.  Your mSOL will be successfully unstaked after the transaction is executed.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F94IcSEiMGh3aeDrzExYZ%2Fstaking%2520liquid%2520marinade%2520Unstake.jpg&width=768&dpr=4&quality=100&sign=582c3340&sv=2)

Marinade liquid staking pop-up

[PreviousLido](https://docs.squads.so/main/squads-legacy/integrations/staking/lido)
[NextSolBlaze](https://docs.squads.so/main/squads-legacy/integrations/staking/solblaze)

Last updated 1 year ago

---

# Welcome to Squads Multisig | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FsvVw0PsuM7jrUtEiRUGO%252FMain%2520banner.png%3Falt%3Dmedia%26token%3D5daf2346-88a0-4fa5-8880-f3f21b4922b3&width=1248&dpr=4&quality=100&sign=80dae27&sv=2)

### 

[](https://docs.squads.so/main#about-squads)

About Squads

Squads Multisig is a multisig platform to secure and manage Solana assets. With Squads, teams can deploy a multisig in a few clicks, configure it to satisfy their security and organizational requirements, and then use it to manage a wide range of onchain assets such as:

*   Treasury;
    
*   Program upgrade authorities;
    
*   Admin keys;
    
*   Tokens;
    
*   and Validators.
    

With Squads, our goal is to bring a traditional SaaS-like product experience to onchain asset management in a way that feels familiar and intuitive to both traditional and crypto-native businesses.

Squads achieves this by solving three core problems when it comes to managing onchain assets:

*   User experience - We have transformed a lot of the experiences that previously required developers to interact with the CLI into well-designed user flows all contained within an intuitive interface.
    
*   Security - Squads is built on top of Squads Protocol, Solana's autonomous finance layer. Each multisig's rules, security and workflows are enforced by Squads Protocol and Solana's 1,000+ global validators, not a centralized exchange, black box algorithm or trusted 3rd-party.
    
*   Transparency - We enhance transparency for teams by giving main stakeholders increased visibility and the ability to approve critical actions for project development. This is achieved by requiring multisig approvals for managing assets, making relevant data accessible and human-readable.
    

We provide teams with greater transparency, allowing for the main stakeholders to have more visibility and a way to approve actions critical for the development of their project by requiring multisig approvals for the management of assets, parsing a lot of the relevant data in our interface and making it human readable.

### 

[](https://docs.squads.so/main#squads-protocol)

Squads Protocol

Squads Protocol is the autonomous finance layer built on Solana.

It replaces legacy banking infrastructure and centralized servers with a blockchain-native operating system — delivering programmable payments, 24/7 USD liquidity, competitive yields, and security enforced by deterministic code, not corporate promises.

Trusted by over 350 teams and thousands of individuals, Squads Protocol secures more than $10 billion in assets and has processed over $3 billion in stablecoin transfers.

[NextWhat is a multisig](https://docs.squads.so/main/basics/what-is-a-multisig)

Last updated 6 months ago

---

# Rent Reclaim | Squads Docs

Solana charges rent when you execute a transaction with your multisig. This is because Squads creates onchain accounts to support the asynchronous multisig process during a transaction's life cycle. The rent charged is for storing this data onchain.

Once a Squads transaction is executed/canceled, these accounts are no longer needed. Rent Reclaim allows you to close these accounts and reclaim the associated rent. Once reclaimed, the transaction history will still be available and auditable via Solana’s ledger.

*   **Eligibility**: Transactions in finalized states (Executed, Canceled, Rejected)
    
*   **Process**: Close unnecessary accounts while maintaining transaction history onchain
    

### 

[](https://docs.squads.so/main/navigating-your-squad/transactions/rent-reclaim#enabling-rent-reclaim)

Enabling Rent Reclaim

1.  Navigate to the Settings page of your Squads account
    
2.  Enable Rent Reclaim (requires multisig threshold approval)
    

### 

[](https://docs.squads.so/main/navigating-your-squad/transactions/rent-reclaim#auto-rent-reclaim)

Auto Rent Reclaim

*   Optional feature to have in [Settings](https://docs.squads.so/main/navigating-your-squad/settings)
     once it is enabled
    
*   When turned on, it automatically reclaims rent upon transaction execution
    
*   Manual reclaim is required for Cancelled or Rejected transactions
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252Fqib8NtxZvUHx2uLUo0GP%252FScreenshot%25202024-06-26%2520at%252010.13.02%25E2%2580%25AFAM.png%3Falt%3Dmedia%26token%3D6ed754dc-3422-448d-aad2-c58aa3338f41&width=768&dpr=4&quality=100&sign=11d4cbd3&sv=2)

Auto rent reclaim settings

### 

[](https://docs.squads.so/main/navigating-your-squad/transactions/rent-reclaim#reclaim-destination)

Reclaim Destination

All reclaimed rent will be sent to the Reclaim Destination address. This address is preset to your Squad Vault but can be updated on the Settings page (requires threshold approval).

### 

[](https://docs.squads.so/main/navigating-your-squad/transactions/rent-reclaim#reclaim-rent)

Reclaim Rent

You can reclaim rent per transaction in the Transactions tab for any transaction with a finalized status (Executed, Canceled, Rejected). Any member of the Squad can reclaim rent without requiring multisig approval.

[PreviousBatch actions](https://docs.squads.so/main/navigating-your-squad/transactions/batch-actions)
[NextMembers](https://docs.squads.so/main/navigating-your-squad/members)

Last updated 1 year ago

---

# Who we are - Squads Labs | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FoVgGIIcpoFYrOUx7LH9B%252Fsquads%2520labs.png%3Falt%3Dmedia%26token%3Dff9d5e9f-3f74-4f44-add7-506365d46f68&width=1248&dpr=4&quality=100&sign=b6590dfe&sv=2)

[](https://docs.squads.so/main/basics/who-we-are-squads-labs#squads-labs)

Squads Labs


------------------------------------------------------------------------------------------

Squads Labs is a technology company that builds tools to enable efficient economic activity onchain.

Our mission is to grow the onchain economy by developing smart account technology and products that make it easy for businesses, teams and individuals to securely transact, manage and own digital assets.

Leveraging this smart account technology, we offer a product suite that includes Squads for enterprises and [Fuse](https://fusewallet.com/)
 for individuals.

We are trusted and used by over 250 teams in the ecosystem, such as Jupiter, Pyth, Raydium, Marginfi, Backpack, Drift, Helius, Kamino, Jito, Tensor, Helium and many others.

Our partners and investors include Electric Capital, RockawayX, Coinbase Ventures, L1D, Placeholder, Multicoin Capital, 6th Man Ventures, Jump Crypto, Collab+Currency, Delphi Digital, Reciprocal Ventures, Solana Ventures.

[PreviousWhat is a multisig](https://docs.squads.so/main/basics/what-is-a-multisig)
[NextSecurity](https://docs.squads.so/main/basics/security)

Last updated 12 months ago

---

# Fee Relayer | Squads Docs

The Squads Fee Relayer lets teams use their Squad as a paymaster to cover the transaction fees of all member transactions linked to their Squad.

This feature is made possible by [Turnkey](https://www.turnkey.com/)
, a private key infrastructure that allows the generation and management of private keys across blockchains through APIs without compromising on security.

The Fee Relayer is only accessible to users with a Squads Business or Enterprise plan. Learn more about our pricing and subscription plans [here](https://docs.squads.so/main/getting-started/pricing)
.

**To enable the Fee Relayer** for a Squad:

1.  Navigate to the Members page from the navigation tab on the left.
    
2.  Toggle the "Fee relayer" button;
    
3.  Your Squad will now pay the network fees for its members.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FuPCqTnCO8NuzhlsZUcXt%252FScreenshot%25202024-11-11%2520at%25207.31.32%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D2e64a77a-1723-44ad-9f8b-033ca7a0a556&width=768&dpr=4&quality=100&sign=50fc0701&sv=2)

Fee Relayer

You can deactivate the Fee Relayer at any point by switching off the toggle button either under the Settings or the Members page.

Note that if your Business subscription expires or if the Fee Relayer is removed from the members, it will automatically be deactivated.

If there is no SOL left in the Squad or that the Fee Relayer balance falls below 0.03 SOL, a message will appear under the Fee Relayer tab asking you to manually top up the Fee Relayer.

[PreviousPermissions](https://docs.squads.so/main/navigating-your-squad/members/permissions)
[NextTreasury](https://docs.squads.so/main/navigating-your-squad/treasury)

Last updated 1 year ago

---

# TX Builder | Squads Legacy (v3) | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FYYk2gCXhjgyZmW5dDwKZ%2FSquads%2520Tx%2520builder.png&width=1248&dpr=4&quality=100&sign=6e8bd44d&sv=2)

In Squad V3 users can create custom transactions and populate them with arbitrary instructions through the Transaction Builder to interact with any programs on Solana directly from a Squad.

**To create a draft custom transaction:**

1.  Navigate to the “TX Builder” tab and click “Create transaction”. If you already know the type of TX you want to create, just click on one of the templates.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FfdR1iR4OCcrZhV2cs2gF%2FTX%2520BUILDER%25201.png&width=768&dpr=4&quality=100&sign=2446ca17&sv=2)

TX Builder Tab

2\. After you click on "+Create transaction", you will be directed to the transaction screen. Here you can click on "Add instruction" to start crafting it or delete the draft if you don't need it anymore.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FhDPNf0kVobISZQGlIUnf%2FTX%2520BUILDER%25202.png&width=768&dpr=4&quality=100&sign=9160ec78&sv=2)

Transactions screen

All custom transactions are first saved as a draft, which needs to be populated with the instructions data before the launch. You can save your custom transaction after it is initiated.

3\. After clicking on "Add instruction" you will see a pop-up of available options. You can create a custom transaction to interact with:

a. Anchor programs (with IDL)

b. Solana programs (written in Rust)

c. Import a base58 encoded transaction

d. Validators (using predefined templates)

e. Switchboard program

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FalxMlzLx625gim7GSrNM%2FTX%2520BUILDER%25203.png&width=768&dpr=4&quality=100&sign=6dfc80d7&sv=2)

New custom transaction pop-up

**To populate the custom transaction draft for programs written in Anchor:**

1.  Click on the draft, click “Add instruction”, select the "Custom instruction" option.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FalxMlzLx625gim7GSrNM%2FTX%2520BUILDER%25203.png&width=768&dpr=4&quality=100&sign=6dfc80d7&sv=2)

Create new transaction pop-up

1.  Insert the program address and click "Next".
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FUq4CPfLL8jHSiCq4pzem%2FTX%2520BUILDER%25205.png&width=768&dpr=4&quality=100&sign=b65e6a88&sv=2)

Pop-up for programs written in Anchor

3\. Select the instruction from the list and click "Add instruction".

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FgZC9YPtnuFmYKxNcHvfS%2FTX%2520BUILDER%25206.png&width=768&dpr=4&quality=100&sign=c03d1272&sv=2)

Add instruction pop-up

4\. Populate the Accounts with the required data and click "Save draft". You can add another instruction inside the draft to run two custom instructions in one transaction. You can also add a name and description to the transaction.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FemBHDdw3w9ea51kBiAfi%2FTX%2520BUILDER%25207.png&width=768&dpr=4&quality=100&sign=1fc49397&sv=2)

Custom transaction

After you populate the draft with arbitrary instucrtions you can run a simulation to check if your transaction is assembled correctly.

1.  After you populate the transaction with instructions and run a simulation to verify that everything is correct, launch a transaction inside your Squad by clicking on "Initiate Transaction". The custom transaction with arbitrary instructions will be launched upon transaction execution. (More on transaction [execution](https://docs.squads.so/main/squads-legacy/navigating-your-squad/transactions#execute-cancel-transactions)
    ).
    

**To populate the custom transaction draft for programs written in Rust:**

1.  Click on the draft, click “Add instruction”, select the "Custom instruction" option.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FalxMlzLx625gim7GSrNM%2FTX%2520BUILDER%25203.png&width=768&dpr=4&quality=100&sign=6dfc80d7&sv=2)

New custom transaction pop-up

2\. Insert the program address and click "Add instruction".

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FdlLL0gL9kiKlKMDKxqyz%2FTX%2520BUILDER%25208.png&width=768&dpr=4&quality=100&sign=f9fa9a72&sv=2)

Add instruction pop-up

1.  Insert the account info and then populate the desired data options (Buffer or Raw). Then click "Save draft". You can add another instruction inside the draft to run two custom instructions in one transaction.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FIpxN9U7wTxbXsMk9bNhV%2FTX%2520BUILDER%25209.png&width=768&dpr=4&quality=100&sign=6104c24c&sv=2)

Transaction screen

After you populate the draft with arbitrary instucrtions you can run a simulation to check if your transaction is assembled correctly.

3\. After you populate the transaction with instructions and run a simulation to verify that everything is correct, launch a transaction inside your Squad by clicking on "Initiate Transaction". The custom transaction with arbitrary instructions will be launched upon transaction execution. (More on transaction [execution](https://docs.squads.so/main/squads-legacy/navigating-your-squad/transactions#execute-cancel-transactions)
).

**To populate the draft with instructions from base58 encoded transactions:**

1.  Click on the draft, click “Add instruction”, select the "Import base58 encoded tx" option.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FRyjjPg7dek48nArsfz5J%2FTX%2520BUILDER%252010.png&width=768&dpr=4&quality=100&sign=b5c520df&sv=2)

New custom transaction pop-up

1.  Insert the base58 encoded transaction, click "Next". Check the data and click "Add instruction".
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F415GgnsFj8Swtbp8gXbh%2FTX%2520BUILDER%252011.png&width=768&dpr=4&quality=100&sign=81df2766&sv=2)

Base58 encoded transaction pop-up

1.  After you have checked the data and run a simulation to verify that everything is correct, launch a transaction inside your Squad by clicking on "Initiate Transaction". A custom transaction with arbitrary instructions will be launched upon transaction execution (More on transaction [execution](https://docs.squads.so/main/squads-legacy/navigating-your-squad/transactions#execute-cancel-transactions)
    ).
    

**To interact with the validators and stake pools using predefined templates:**

1.  Click on "Add instruction".
    
2.  Select from the list the template you want to use: Stake program, Vote program, Stake Pool program, Switchboard program.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F4h766YjgUI0jXtQlKIZc%2FTX%2520BUILDER%252012.png&width=768&dpr=4&quality=100&sign=ec68f1f6&sv=2)

New custom transaction pop-up

The stake program template allows you to interact with validators to deactivate and withdraw staked SOL.

The vote program template allows you to change the withdraw authority, withdraw stake rewards, and change the commission of the validator.

The stake pool program template allows you to set the manager, fees, and funding authority of the stake pool.

Using Switchboard program template allows you to interact with Switchboard and create and manage feeds from a multisig.

3\. Populate any of the templates with the required data and launch a transaction. Once the transaction meets confirmation threshold and is executed, the interaction with the program will be made.

[PreviousValidators](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/validators)
[NextCreators](https://docs.squads.so/main/squads-legacy/navigating-your-squad/creators)

---

# Priority fees | Squads Docs

To ensure smooth transaction execution during high network activity:

*   You can access "Advanced Settings" to set custom priority fees.
    
*   Users can also check the network activity via the "Network Status" button in the top-right corner and adjust their Global Priority Fee.
    
*   This can be set to:
    
    *   Auto
        
    *   Ultra
        
    *   Custom
        
    

This applies to all Squads transactions (Initiation, Approval, and Execution)

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FuYeWmoEQsRFO5rs3V5NK%252Fimage.png%3Falt%3Dmedia%26token%3De9e7f175-e748-4256-ae40-f799aa95b4e0&width=768&dpr=4&quality=100&sign=9ea4ec77&sv=2)

Global Priority Fee

[PreviousTransactions](https://docs.squads.so/main/navigating-your-squad/transactions)
[NextBatch actions](https://docs.squads.so/main/navigating-your-squad/transactions/batch-actions)

Last updated 1 year ago

---

# Manage Members | Squads Docs

### 

[](https://docs.squads.so/main/navigating-your-squad/members/manage-members#adding-a-member)

**Adding a Member:**

1.  Click on the "Add member" button.
    
2.  Insert the public key of the member.
    
3.  Specify permissions for the member if you have a [**Squads Business** plan](https://docs.squads.so/main/getting-started/pricing)
     (More about "Permissions" here).
    
4.  You can optionally change the Squad threshold in the same transaction. If not, the threshold will remain the same with a new member added to the Squad.
    
5.  Click the "Initiate transaction" button.
    

Reminder: Adding members or changing the confirmation threshold will cancel all "Active" and "Ready" transactions in a Squad. Complete these transactions before making changes to your Squad threshold to avoid issues.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FLXow76uFsCrW3iyCW7vK%252FScreenshot%25202024-06-25%2520at%252011.08.39%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D1dc7f931-640c-419e-acbc-b0d72306e8c4&width=768&dpr=4&quality=100&sign=5bd42ab1&sv=2)

Add member pop-up

### 

[](https://docs.squads.so/main/navigating-your-squad/members/manage-members#removing-a-member)

**Removing a Member:**

1.  Click on the "Bin" icon on the member's card.
    
2.  Click "Initiate".
    
3.  The member will be removed from the Squad upon execution of the transaction.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FKBrLXqkIMbwyCxJH1Wme%252FScreenshot%25202024-06-26%2520at%25202.55.14%25E2%2580%25AFAM.png%3Falt%3Dmedia%26token%3De92a4591-a1c2-46ee-bd1c-43d72d6934ac&width=768&dpr=4&quality=100&sign=c8aa58d0&sv=2)

Remove member pop-up

[PreviousMembers](https://docs.squads.so/main/navigating-your-squad/members)
[NextPermissions](https://docs.squads.so/main/navigating-your-squad/members/permissions)

Last updated 1 year ago

---

# Lido | Squads Legacy (v3) | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FkzUIcHZebxmMLHN0AE7y%2FLido.png&width=1248&dpr=4&quality=100&sign=e8bc7cdc&sv=2)

[](https://docs.squads.so/main/squads-legacy/integrations/staking/lido#overview)

Overview


----------------------------------------------------------------------------------------------

Users can deposit their SOL holdings into Lido stake pool, which lets them earn staking rewards and receive stSOL token, which can be used to gain additional yield.

[](https://docs.squads.so/main/squads-legacy/integrations/staking/lido#what-is-stsol)

What is stSOL?


---------------------------------------------------------------------------------------------------------

Lido is a liquid staking solution that allows users to stake their SOL holdings without locking them up. With Lido, users receive stSOL tokens which are issued 1:1 to their initial stake. stSOL can then be used to earn additional rewards through DeFI protocols, which can be accessed directly from the Squad via the ["Apps"](https://docs.squads.so/main/squads-legacy/navigating-your-squad/apps)
 section.

[](https://docs.squads.so/main/squads-legacy/integrations/staking/lido#how-to-stake-with-lido-stake-pool)

How to stake with Lido Stake Pool?


-------------------------------------------------------------------------------------------------------------------------------------------------

**To stake SOL:**

1.  Navigate to the "Staking" tab and select "Liquid" section.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2F21znfo59LozoG7hN63ye%2FStaking%2520liquid.jpg&width=768&dpr=4&quality=100&sign=83d4db2a&sv=2)

Liquid staking section

2\. Click on the "Lido stake pool" block.

3\. Select the amount of SOL you wish to delegate to the pool and click "Deposit" button.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FJsNTmpFJLWcewKU4qeuy%2Fstaking%2520liquid%2520lido.jpg&width=768&dpr=4&quality=100&sign=19eff296&sv=2)

Lido liquid staking pop-up

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](https://docs.squads.so/main/squads-legacy/navigating-your-squad/transactions)
) and will appear in the vault as the stSOL. Once the new epoch starts, you will start earning rewards.

[](https://docs.squads.so/main/squads-legacy/integrations/staking/lido#how-to-unstake-from-lido-stake-pool)

How to unstake from Lido Stake Pool?


-----------------------------------------------------------------------------------------------------------------------------------------------------

**To unstake SOL:**

1.  To unstake your SOL, you can swap stSOL to SOL or any other token.
    
2.  Swaps on v3 are no longer supported. Please migrate your assets to [https://app.squads.so/](https://app.squads.so/squads)
     in order to swap your tokens.
    
3.  Once migrated, learn about swaps on v4 [here](https://docs.squads.so/main/navigating-your-squad/in-app-integrations/trade)
    .
    

If you have any questions, please reach out to us on [Discord](https://discord.com/invite/YPXz64TrKs)
.

[PreviousJitoSOL](https://docs.squads.so/main/squads-legacy/integrations/staking/jitosol)
[NextMarinade](https://docs.squads.so/main/squads-legacy/integrations/staking/marinade)

Last updated 1 year ago

---

# Contacts | Squads Docs

To streamline fund withdrawals, any Squad member can save addresses as contacts:

*   Click the "Contacts" icon in the "Treasury" section of the "Account" view.
    
*   Enter the contact's name and public key.
    
*   Approve and sign the transaction in the wallet pop-up. The address will saved as a contact.
    
*   To remove a contact, click the "Bin" icon and sign the transaction.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252F1y1pvobZwLAlDdRKwKzg%252FContacts.png%3Falt%3Dmedia%26token%3Dac6cd4f1-c6aa-4969-9a28-c947c699c0cd&width=768&dpr=4&quality=100&sign=f4f6bddb&sv=2)

Contacts pop-up

[PreviousManage assets](https://docs.squads.so/main/navigating-your-squad/treasury/manage-assets)
[NextAirdrop Checker](https://docs.squads.so/main/navigating-your-squad/treasury/airdrop-checker)

Last updated 1 year ago

---

# Programs | Squads Legacy (v3) | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FMCc9lBfRT92BTcTqaFA9%2FSquads%2520Programs.png&width=1248&dpr=4&quality=100&sign=80fa906e&sv=2)

For web3 native teams, the "Programs" section will be a part of the core operations of their Squad and it allows to:

*   Add programs
    
*   Upgrade Programs
    
*   Change authority of programs
    

### 

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/programs#create-and-add-programs)

Create and add programs

Users can add programs to manage and upgrade them directly from their Squad.

[https://youtu.be/TbVDUWZW0Sgyoutu.be](https://youtu.be/TbVDUWZW0Sg)

#### 

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/programs#create-programs)

Create programs

1.  Create and deploy a program using your CLI.
    

#### 

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/programs#add-programs)

Add programs

1.  Navigate to the "Programs" section within your Squad's vault. Then click on "Add Program_"._
    

2\. Enter the name and address of the program. Click "Next" and verify the transaction in the wallet pop-up.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FClk07FUk5fpvxiGcuBwQ%2Fprograms%25202.png&width=768&dpr=4&quality=100&sign=b81becef&sv=2)

Add program pop-up

3\. Set the program’s upgrade authority to the address provided: copy the program authority update code and paste it into your CLI. The CLI code should be run by the current authority. Then click “Verify authority”.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FNO7N7qmuNHXlOAF21EzX%2Fprograms%25203.1.png&width=768&dpr=4&quality=100&sign=a7057979&sv=2)

Add program pop-up

**NOTE:** If the current authority is managed by a DAO or wallet you may need to set the authority by other means using the provided upgrade authority.

For users who would want to perform the authority transfer in a safer way there is an option to make a Safe Authority Transfer (SAT).

SAT creates a transaction in the Squad, which needs to be signed by both Squad's Vault PDA and the current authority holder.

[https://youtu.be/tnllbW3yX14youtu.be](https://youtu.be/tnllbW3yX14)

**To perform a Safe Authority Transfer (SAT):**

1.  Add your CLI wallet to the Squad. Check the [Owners and Setting](https://docs.squads.so/main/squads-legacy/navigating-your-squad/owners-and-settings)
     page for more info on members addition.
    
2.  Click on the "Create SAT" button.
    
3.  Enter a description (optional) and run a transaction inside your Squad.
    
4.  Once the transaction meets the confirmation threshold, execute it with your CLI wallet, which you added into your Squad.
    
5.  Once the transaction is executed, your program authority will be transferred.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FnswS2za0VrHFNGt1yxY3%2Fprograms%25203.2.png&width=768&dpr=4&quality=100&sign=d7ae45e7&sv=2)

Safe Authority Transfer (SAT)

### 

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/programs#upgrade-a-program)

Upgrade a program

Once the program is added to a Squad it can be upgraded straight from your Squad.

[https://youtu.be/IQMkyslQy4Eyoutu.be](https://youtu.be/IQMkyslQy4E)

**To upgrade a program:**

1.  Deploy your upgrade to the buffer using the command below. (For Rust)
    

Copy

    solana program write-buffer <PROGRAM_FILEPATH>

For more information about writing intermediary buffer accounts refer to the link: [https://docs.solana.com/cli/deploy-a-program#using-an-intermediary-buffer-account](https://docs.solana.com/cli/deploy-a-program#using-an-intermediary-buffer-account)

2\. Click on the program from the list and then click on the "Add upgrade" button.

3\. Insert the details of the upgrade: name, buffer, and spill address, then click "Next" and approve the transaction in the wallet pop-up.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FZKeXVGcRrpDDBATa7Fp8%2Fprograms%25204.png&width=768&dpr=4&quality=100&sign=980dc9fc&sv=2)

Program upgrade pop-up

4\. Set the authority of the buffer to the provided address by copying a code in your CLI. Then click “Verify authority”.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2Fcontent.gitbook.com%2Fcontent%2FgDRN91t7KCCGF3GOssvZ%2Fblobs%2FjR2SUUMkwE3er6FN1Nmi%2Fprograms%25205.png&width=768&dpr=4&quality=100&sign=b84952cc&sv=2)

Program upgrade pop-up

5\. Click on the "Upgrade" button. A transaction will be created, after it meets the confirmation threshold and gets executed, a program upgrade will be deployed.

Using actions created by [Cardinal](https://www.cardinal.so/)
, you can automate the deployment of program upgrades directly from Github. Using those actions you can automatically build code, deploy it to a buffer and create a program upgrade transaction inside your Squad every time you make code changes to your program.

**For more details check:**

1.  [https://github.com/marketplace/actions/squads-program-upgrade](https://github.com/marketplace/actions/squads-program-upgrade)
    
2.  [https://github.com/cardinal-labs/solana-buffer-deploy-action](https://github.com/cardinal-labs/solana-buffer-deploy-action)
    

Squads users can also use [Nosana](https://nosana.io/)
 to create an automated deployment pipeline and streamline their deployment process.

**For more details check:**

1.  [https://docs.nosana.io/tutorials/solana-multisig.html#cleaning-up-canceled-deployments](https://docs.nosana.io/tutorials/solana-multisig.html#cleaning-up-canceled-deployments)
    

### 

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/programs#remove-a-program-from-ui)

Remove a program from UI

Users can remove programs that they no longer use from the UI and claim back the rent in SOL.

[https://youtu.be/QkOc78UqAYcyoutu.be](https://youtu.be/QkOc78UqAYc)

**To do this:**

1.  Navigate to the programs list and click on the "Bin" icon next to the program you want to delete.
    
2.  Insert a description (optional) and launch a transaction.
    
3.  A program will be deleted upon transaction execution.
    

This action does not affect the program or the buffer, it will only remove the program from the UI. It will also return the PDA rent (in SOL) of this account to your vault.

### 

[](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/programs#withdraw-program-upgrade-authority)

Withdraw program upgrade authority

Program authority can be changed directly from a Squad after a program was added to any other address if needed.

**To do this:**

1.  Click on the program from the programs list.
    
2.  Click on the "Change authority" button.
    
3.  Insert a new program authority address and initiate a transaction.
    
4.  Program authority will be changed upon transaction execution.
    

[PreviousDevelopers](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers)
[NextToken Manager](https://docs.squads.so/main/squads-legacy/navigating-your-squad/developers/token-manager)

---

# Batch actions | Squads Docs

To streamline operations, users can perform bulk approvals, rejections, or cancellations:

1.  Click the "Batch Actions" dropdown button.
    
2.  Select the desired transactions.
    
3.  Choose to approve, reject, or cancel at once.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FzW1TYyr8Ww69p67MeWlZ%252Fimage.png%3Falt%3Dmedia%26token%3D8509d132-60ce-46bd-b8a2-0f0eef67a55a&width=768&dpr=4&quality=100&sign=433e078b&sv=2)

Batch Actions

[PreviousPriority fees](https://docs.squads.so/main/navigating-your-squad/transactions/priority-fees)
[NextRent Reclaim](https://docs.squads.so/main/navigating-your-squad/transactions/rent-reclaim)

Last updated 1 year ago

---

# Limit Orders | Squads Docs

Limit Orders ensure asset trades occur at predetermined prices. Unlike Swaps, they don't require immediate execution, offering flexibility in volatile markets. This feature is valuable for:

*   Protecting assets from unfavorable price movements
    
*   Managing large trades with reduced risk
    
*   Executing complex trading strategies agreed upon by team members
    

Limit Orders eliminate surprises and failed executions, making them an ideal tool for enterprises managing substantial assets in dynamic market conditions.

[](https://docs.squads.so/main/navigating-your-squad/trade/limit-orders#how-to-place-limit-orders-directly-from-your-squads-account)

How to place Limit Orders directly from your Squads account:


------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

The Squads trading dashboard enables seamless trading of assets via Limit Orders.

1.  Go to the "Trading" section from the navigation bar on the left of the Squads app.
    
2.  Select the “Limit Order” tab and choose the account from which you want to place the Limit Order.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FvD7eZsspFw9JMNbmtF4j%252Fimage.png%3Falt%3Dmedia%26token%3D29529026-d9e6-466a-a237-fddf568123ae&width=768&dpr=4&quality=100&sign=9b8e9e00&sv=2)

"Limit Order" tab

1.  Select the pair you wish to trade (e.g. SOL for USDC) and the amount. Click the “Next” button.
    
2.  Review your transaction by checking the tokens, amounts, limit price, and expiry. Click the “Initiate” button to launch the transaction.
    

Once the transaction reaches the confirmation threshold and is executed, the Limit Order will be open and filled as soon as the set price is reached.

You can view the price of the token-pair you are trading (e.g. SOL-USDC) on the right-hand side of the “Trading” page.

A 0.25% fee is incurred for every Limit Order placed from the Squads app.

If you trade a token that hasn't been deposited into your Squads account before, you will require at least 0.003 SOL in your account. This amount covers the cost of creating an [ATA](https://spl.solana.com/associated-token-account)
 for the newly deposited token.

[](https://docs.squads.so/main/navigating-your-squad/trade/limit-orders#how-to-manage-open-limit-orders)

How to manage open Limit Orders:


----------------------------------------------------------------------------------------------------------------------------------------------

Once executed through your Squads account, your order appears in the "Open Position" section—providing a clear overview of all orders and their details. You can cancel unfilled orders at any time or expand any position to view detailed token charts.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FBXFbsXxDKvAqzQYRCaGV%252Fimage.png%3Falt%3Dmedia%26token%3D5f2f8a57-2122-4b36-867a-b8cf1a111bc6&width=768&dpr=4&quality=100&sign=ea0555e2&sv=2)

"Open Position" section

[PreviousTrade](https://docs.squads.so/main/navigating-your-squad/trade)
[NextSwaps](https://docs.squads.so/main/navigating-your-squad/trade/swaps)

Last updated 11 months ago

---

# On and Off-Ramp | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FGr2wY3ckT2VWYnQz0J07%252Fon%2520and%2520off%2520ramp.png%3Falt%3Dmedia%26token%3Dd9ba2045-aea1-4a61-8478-cef2ee7fcb2b&width=1248&dpr=4&quality=100&sign=45d18c9b&sv=2)

Squads users can on-ramp assets to their multisig and off-ramp assets to their bank accounts seamlessly using:

*   [Squads Virtual US Bank Account](https://docs.squads.so/main/getting-started/on-and-off-ramp/virtual-us-bank-account)
    : Receive payments in USD, which is seamlessly converted to USDC in your Squad account.
    
*   [Sphere](https://docs.squads.so/main/getting-started/on-and-off-ramp/sphere)
    : Seamless [on-ramping](https://docs.squads.so/main/getting-started/on-and-off-ramp/sphere#on-ramping-with-sphere-and-squads)
     and [off-ramping](https://docs.squads.so/main/getting-started/on-and-off-ramp/sphere#off-ramping-with-sphere-and-squads)
     of assets cost-effectively via Wire, ACH, and SEPA transfers for USD and EUR bank accounts.
    
*   [Coinflow](https://docs.squads.so/main/getting-started/on-and-off-ramp/coinflow-off-ramp)
    : Top-tier US bank collaborations and instant 24/7 crypto off-ramping to individuals and businesses with bank accounts in the US.
    
*   [Bridge](https://docs.squads.so/main/getting-started/on-and-off-ramp/bridge-off-ramp)
    : Off-ramp available to businesses with US or European bank accounts in most regions outside the OFAC sanctions list.
    

Additionally, Squads users can make USDC payouts to bank accounts of both businesses and individuals by leveraging third-party payouts, with funds arriving in either USD or EUR.

[PreviousCreate a Squad](https://docs.squads.so/main/getting-started/create-a-squad)
[NextVirtual US Bank Account](https://docs.squads.so/main/getting-started/on-and-off-ramp/virtual-us-bank-account)

Last updated 9 months ago

---

# Swaps | Squads Docs

Spot Swaps enable Squads users to execute swaps in a multisig setup based on the current price and market liquidity.

Any transaction in a multisig is inherently delayed because it needs approval from other Squad members. This delay can result in price changes or expired routes, which can cause the swap to fail.

[](https://docs.squads.so/main/navigating-your-squad/trade/swaps#how-to-swap-tokens)

How to Swap tokens:


-------------------------------------------------------------------------------------------------------------

1.  Go to the "Trading" section from the navigation bar on the left of the Squads app.
    
2.  Select the “Swap” tab and choose the account from which you want to swap assets.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FNrZrdZKaWiSZNgNkrtPY%252Fimage.png%3Falt%3Dmedia%26token%3Dbbc8ca04-babb-431d-aed0-b9a3a845c590&width=768&dpr=4&quality=100&sign=f53aa3c8&sv=2)

Spot Swaps

1.  Select the pair you wish to trade (e.g. SOL for USDC) and the amount.
    
2.  Configure the slippage tolerance by selecting one of the predefined options or inputting it manually (capped at a maximum of 15%).
    

Trade prices constantly change. Slippage tolerance is designed to determine the minimum amount of the receivable tokens. If the price of the receivable asset deviates above the slippage tolerance percentage, the transaction will fail to execute. In this case, the user will need to initiate a new swap or wait until the exchange rate comes back to the indicated slippage tolerance range.

1.  Check all the information related to your transaction, including:
    
    *   **Rate:** This shows the exchange rate for the selected route.
        
    *   **Slippage:** This shows the slippage tolerance percentage.
        
    *   **Price impact:** This measures how much the size of the trade is affecting the price.
        
    *   **Minimum received:** This is the minimum amount of tokens a user will receive upon transaction execution. It is based on the slippage tolerance.
        
    *   **AMM fees:** This is paid to the AMM for routing the swap.
        
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FbM5BLAmatj81ymwOAEb7%252Fimage.png%3Falt%3Dmedia%26token%3D8fb772da-9c18-44fc-a7aa-78539dfd62de&width=768&dpr=4&quality=100&sign=c2994bdd&sv=2)

Swap Information

1.  Click the “Next” button. Review your transaction by checking the tokens, amounts, slippage, and rate. Click the “Initiate” button to launch the transaction.
    

The swap is completed once the transaction reaches the confirmation threshold and is executed.

If you trade a token that hasn't been deposited into your Squads account before, you will require at least 0.003 SOL in your account. This amount covers the cost of creating an ATA for the newly deposited token.

[PreviousLimit Orders](https://docs.squads.so/main/navigating-your-squad/trade/limit-orders)
[NextStake](https://docs.squads.so/main/navigating-your-squad/stake)

Last updated 1 year ago

---

# Trade | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FaKQlIBaACvF2qgU77a51%252Fsquads%2520trade.png%3Falt%3Dmedia%26token%3D3f1ad411-3452-4f85-8f89-64037c24f5af&width=1248&dpr=4&quality=100&sign=24049fec&sv=2)

Using Squads Trade

[](https://docs.squads.so/main/navigating-your-squad/trade#how-do-squads-users-benefit-from-squads-trade)

How do Squads users benefit from Squads Trade?


-------------------------------------------------------------------------------------------------------------------------------------------------------------

Squads Trade offers deeper liquidity, optimized prices, and a great trading experience for Squads users. Users can execute:

1.  [Limit Orders](https://docs.squads.so/main/navigating-your-squad/trade/limit-orders)
    
2.  [Spot Swaps](https://docs.squads.so/main/navigating-your-squad/trade/swaps)
    

Squads Trade enables teams to trade tokens directly from their multisig—eliminating the need to withdraw funds to individual wallets, saving time and reducing operational risks. Squads Trade is currently powered by Jupiter, and more platforms will be integrated in the future.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FtN2R7aBptSrwJpbKF35i%252Fimage.png%3Falt%3Dmedia%26token%3Da9dfc452-870b-4ea0-8fe3-df8e2d5668d6&width=768&dpr=4&quality=100&sign=dfa2035d&sv=2)

Limit Orders vs Swaps

[](https://docs.squads.so/main/navigating-your-squad/trade#what-is-intent-based-trading)

What is Intent-based trading?


---------------------------------------------------------------------------------------------------------------------------

Squads Trade is built with the conviction that intent-based trading will soon dominate onchain markets.

Intent-based trading transcends single-exchange market orders by expressing what traders want to achieve rather than how to achieve it. This includes orders that execute across multiple venues, markets, and time horizons.

This provides superior price execution allowing traders to set their desired entry points and let automation handle execution when conditions align. Squads Trade will use intent-based trading to offer deeper liquidity, optimized prices and a seamless trading experience.

[PreviousPayments](https://docs.squads.so/main/navigating-your-squad/payments)
[NextLimit Orders](https://docs.squads.so/main/navigating-your-squad/trade/limit-orders)

Last updated 11 months ago

---

# Coin List Filter | Squads Docs

With unsolicited airdrops becoming more common, managing your onchain assets can feel like sorting through spam. To help, we’re introducing the Coin list filter, making it easier than ever to keep your treasury organized.

The Coin list filter puts you back in control, letting you automatically hide new coins and manually curate which coins appear in your treasury view.

### 

[](https://docs.squads.so/main/navigating-your-squad/settings/coin-list-filter#set-automatic-filtering)

Set Automatic Filtering

Enable the Coin list filter to automatically hide any new coins received from other wallets.

1.  Go to “Settings” on the left-hand menu.
    
2.  Switch to the “Other” tab, where you’ll find various Squads settings, including Rent reclaim, Fee Relayer, and the new Coin list filter.
    
3.  Choose your default visibility:
    
    1.  “Hide by default”: Automatically move all new incoming coins to a hidden assets list.
        
    2.  “Show by default”: Display all new incoming coins in your treasury.
        
    

### 

[](https://docs.squads.so/main/navigating-your-squad/settings/coin-list-filter#manually-hiding-and-unhiding-coins)

Manually Hiding & Unhiding Coins

You also have full control to manually hide or unhide specific coins at any time.

#### 

[](https://docs.squads.so/main/navigating-your-squad/settings/coin-list-filter#hide-a-coin)

Hide a coin

1.  Go to “Treasury” in the left-hand menu.
    
2.  Select the account where the coin is located.
    
3.  Find the coin, click the three-dot button, and select “Hide”.
    
4.  The coin will move to a “Hidden Assets” collapsible below all your other assets. From now onwards, the coin will not appear in your treasury when it is incoming; it will also not appear on your balance—preventing it from distorting your overall asset value.
    

#### 

[](https://docs.squads.so/main/navigating-your-squad/settings/coin-list-filter#unhide-a-coin)

Unhide a coin

1.  Navigate to the “Hidden Assets” collapsible.
    
2.  Locate the coin and click “Show Asset” to make it visible again. From now onwards, the coin will appear in your treasury when it is incoming; it will also appear on your overall asset balance.
    

### 

[](https://docs.squads.so/main/navigating-your-squad/settings/coin-list-filter#important-note)

Important Note

The Coin list filter only affects your Squads interface—your onchain accounts will still receive token airdrops.

[PreviousSpending Limits](https://docs.squads.so/main/navigating-your-squad/settings/spending-limits)
[NextPrivacy](https://docs.squads.so/main/navigating-your-squad/settings/privacy)

Last updated 5 months ago

---

# Privacy | Squads Docs

The Privacy mode allows teams to make their Squad visible only to its members. This means that even with the link to a Squad, non-members cannot view its details.

If activated, the only way for someone to view the details of a Squad is to be a member and sign a message to verify their wallet.

To ensure that members don't have to re-sign frequently, a session token is stored in the user's browser for 24 hours. If a member switches to another device, they must sign the message again to store a new session token on this second device.

To activate the Privacy mode for a Squad:

1.  Navigate to the Settings page;
    
2.  Toggle the "Privacy" button;
    
3.  Your Squad will now be viewable only by its members.
    

Your on-chain activity will still be visible on explorers. The privacy mode only prevents unauthorized viewing of a Squad's assets through the UI.

This feature will turn off automatically if the subscription has expired.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252Fun9QvVRhhtlxMx9MgpYQ%252Fimage.png%3Falt%3Dmedia%26token%3D2daea0a2-b6f4-4a0c-b3df-6c40fe948d59&width=768&dpr=4&quality=100&sign=cb97e661&sv=2)

Privacy settings

[PreviousCoin List Filter](https://docs.squads.so/main/navigating-your-squad/settings/coin-list-filter)
[NextTime Locks](https://docs.squads.so/main/navigating-your-squad/settings/time-locks)

Last updated 1 year ago

---

# Security | Squads Docs

Squads Multisig is built on Squads Protocol, the formally-verified autonomous finance layer on Solana, securing over $10 billion in value and more than $3 billion in stablecoin transfers. Squads Protocol is a collection of open source, immutable smart accounts that are powered by Solana's 1,000+ validators.

It replaces legacy banking infrastructure and centralized servers with a blockchain-native operating system — delivering programmable payments, 24/7 USD liquidity, competitive yields, and security enforced by deterministic code, not corporate promises.

### 

[](https://docs.squads.so/main/basics/security#onchain-and-open-sourced)

**Onchain and Open-sourced**

With self-custody at its core, Squads Protocol is built to be resistant to censorship and interference reinforced by thousands of nodes on Solana.

Squads Protocol's codebase is open-sourced (available to view [here](https://github.com/Squads-Protocol/v4)
) and the programs have been written in [Anchor](https://www.anchor-lang.com/)
, a framework for building secure Solana programs.

### 

[](https://docs.squads.so/main/basics/security#multiple-security-audits)

Multiple Security Audits

Our programs have undergone multiple security audits by leading security firms like OtterSec, Certora, Neodyme, etc. These are third-party reviews of our codebase to address vulnerabilities ensuring a neutral and in-depth assessment of the security of Squads Protocol.

You can find the security audits for both Squads Protocol v3 and v4 [here](https://docs.squads.so/main/security/security-audits)
.

### 

[](https://docs.squads.so/main/basics/security#formally-verified)

**Formally Verified**

A formal verification is a rigorous process used to prove that the protocol behaves as intended, ensuring reliability and security.

Squads Protocol v4 (powering [Squads](https://app.squads.so/)
) has undergone [two formal verifications](https://docs.squads.so/main/security/formal-verifications/squads-protocol-v4)
 to make sure it is robust.

### 

[](https://docs.squads.so/main/basics/security#immutable)

Immutable

We strongly believe that core primitives existing on open and permissionless networks should be made immutable as soon as practically possible. We are committed to making Squads Protocol programs immutable within months of public release.

Squads Protocol v3 (powering Squads Legacy) was the first multisig program on Solana and it has been [immutable since February 2023](https://x.com/SquadsProtocol/status/1628776620243963904?s=20)
.

Squads Protocol v4, launched in October 2023, has also been [immutable since November 2024](https://x.com/SquadsProtocol/status/1859947607671607443)
, unalterable by Squads Labs or any third party.

### 

[](https://docs.squads.so/main/basics/security#perpetual-bug-bounty-program)

**Perpetual Bug Bounty Program**

We also run a perpetual bug bounty program incentivizing proactive security checks by the community. Learn more about our program [here](https://docs.squads.so/main/security/bug-bounty)
.

* * *

Squads Protocol stands apart with a commitment to fully onchain, open-source security. This approach fosters accountability, allowing anyone to scrutinize and verify the security of Squads Protocol—a critical element for those seeking transparency and trust in their onchain asset management solutions.

If you have any more questions about security on Squads, reach out to us on [Discord](https://discord.com/invite/squadsprotocol)
.

[PreviousWho we are - Squads Labs](https://docs.squads.so/main/basics/who-we-are-squads-labs)
[NextQuickstart Guide](https://docs.squads.so/main/getting-started/quickstart-guide)

Last updated 6 months ago

---

# Sub-accounts | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252F6GwN263KlPo75sd3Q9Iq%252Fsub-accounts-solana-account-abstraction-multisig-wallet-solana-multi-signature-treasury-management-squads-platform-app.png%3Falt%3Dmedia%26token%3Ddae1f65c-a433-4328-9891-6beb08ba3e73&width=1248&dpr=4&quality=100&sign=bf0890f0&sv=2)

Sub-accounts are separate vaults that users can create to better manage their treasury assets such as payroll, marketing expenses, NFT holdings, etc.

Each sub-account has its own SPL address and inherits the multisig setup of its Squad.

Sub-accounts are only accessible to users with a Squads Business or Enterprise plan. Learn more about our pricing and subscription plans [here](https://docs.squads.so/main/getting-started/pricing)
.

### 

[](https://docs.squads.so/main/navigating-your-squad/treasury/sub-accounts#inside-a-sub-account-users-can)

**Inside a sub-account, users can:**

*   Initiate deposits, withdrawals, and swaps
    
*   Create contacts for quick access when withdrawing treasury assets
    
*   Check SPL tokens and NFTs held, as well as their respective weight in the overall account balance
    
*   Quickly stake their SOL holdings by clicking on the “Stake” button next to the SOL asset
    
*   Check the inflows and outflows of the sub-account
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FiZ0yr3SB0nN4apduRd12%252FAccounts%2520highlighted.png%3Falt%3Dmedia%26token%3D8b25fc4e-7091-4252-a6f5-c76b1ae689ed&width=768&dpr=4&quality=100&sign=89b59d16&sv=2)

Sub-accounts

[PreviousTreasury](https://docs.squads.so/main/navigating-your-squad/treasury)
[NextManage assets](https://docs.squads.so/main/navigating-your-squad/treasury/manage-assets)

Last updated 1 year ago

---

# Permissions | Squads Docs

Permissions are crucial for ensuring the secure and collaborative management of assets within your Squad. By leveraging permissions, users can establish granular levels of access for Squad members, thereby limiting the possibility of wrongdoing within a Squad.

Permissions are only accessible to users with a Squads Business or Enterprise plan. Learn more about our pricing and subscription plans [here](https://docs.squads.so/main/getting-started/pricing)
.

**Members in Squads have 3 types of roles:**

*   **Proposer** - only allows creating transactions in the Squad without allowing to vote or execute them
    
*   **Voter** - only allows signing transactions in the Squad without allowing to create or execute them.
    
*   **Executor** - only allows executing transactions in the Squad without allowing to create or sign transactions.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252Fd2JBpU0MXarT2yD7TPuS%252FPermissions.png%3Falt%3Dmedia%26token%3Ddab300d1-ce1b-4d37-8c2a-de0ed09ae3bc&width=768&dpr=4&quality=100&sign=cbece56d&sv=2)

Permissions

When members are added to a Squad during deployment, they are granted all three permissions. Permissions can be reassigned for existing members after the Squad deployment, and can be assigned for newly added members when launching a transaction to add them.

Please note that you must always have a sufficient amount of members with “Voter” and “Executor” permissions to successfully reach the confirmation threshold set for your Squad and execute the created transactions.

[PreviousManage Members](https://docs.squads.so/main/navigating-your-squad/members/manage-members)
[NextFee Relayer](https://docs.squads.so/main/navigating-your-squad/members/fee-relayer)

Last updated 1 year ago

---

# Treasury | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FsNbhgxhAvwxWaj2Gy5VS%252Ftreasury.png%3Falt%3Dmedia%26token%3De8af6278-42c8-46d1-bc01-78a54e2725c9&width=1248&dpr=4&quality=100&sign=99ddc953&sv=2)

The Treasury page in Squads enables users to:

*   See the cumulative balance of all accounts including the amount of assets (SPL and NFTs)
    
*   Check the number of validators with whom they staked their SOL holdings.
    
*   [Create Sub-accounts](https://docs.squads.so/main/navigating-your-squad/treasury/sub-accounts)
     (only for [Squads Business and Enterprise](https://docs.squads.so/main/getting-started/pricing)
     users)
    
*   [Manage assets — Initiate withdrawals, deposits, swaps, and off-ramps](https://docs.squads.so/main/navigating-your-squad/treasury/manage-assets)
    
*   [Add and manage contacts](https://docs.squads.so/main/navigating-your-squad/treasury/contacts)
    
*   [Browse NFTs stored in different accounts](https://docs.squads.so/main/navigating-your-squad/treasury/manage-assets#nfts)
    
*   [Check eligibility for airdrops](https://docs.squads.so/main/navigating-your-squad/treasury/airdrop-checker)
    
*   Navigate to specific accounts for detailed management
    

The Treasury consists of “Accounts” that are separate vaults (sub-accounts) with unique addresses. Each one is a separate [PDA (Program Derived Address)](https://solanacookbook.com/core-concepts/pdas.html#facts)
. These separate vaults allow teams to organize their treasury assets efficiently

### 

[](https://docs.squads.so/main/navigating-your-squad/treasury#supported-assets)

**Supported assets**

Squads supports:

*   Any SPL (Solana Program Library) tokens, including tokens under the Token2022 standard;
    
*   NFTs, including pNFT and cNFT standards.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FeIo9rmXpILii4oh1YZdn%252FTreasury%2520general%2520view.png%3Falt%3Dmedia%26token%3D85bf16e0-9e36-4f39-a287-5196c99a50c3&width=768&dpr=4&quality=100&sign=ed78a242&sv=2)

Treasury tab

[PreviousFee Relayer](https://docs.squads.so/main/navigating-your-squad/members/fee-relayer)
[NextSub-accounts](https://docs.squads.so/main/navigating-your-squad/treasury/sub-accounts)

Last updated 1 year ago

---

# Airdrop Checker | Squads Docs

Users can use the Aidrop Checker to verify their Squads account's eligibility for current and future airdrops:

*   Located below the coins list on the Treasury page
    
*   Allows eligible users to claim airdrops directly through the Squads app
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FGuH3XKyxK1jOOqNF5Mus%252Fimage.png%3Falt%3Dmedia%26token%3D389b9289-d59d-4a14-a498-f029185c2897&width=768&dpr=4&quality=100&sign=3f4cf256&sv=2)

[PreviousContacts](https://docs.squads.so/main/navigating-your-squad/treasury/contacts)
[NextPayments](https://docs.squads.so/main/navigating-your-squad/payments)

Last updated 1 year ago

---

# Create a Squad | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FUL3ENfcj0UFjnsKyOCvy%252Fnew%2520header.png%3Falt%3Dmedia%26token%3Dcbb69224-5422-4711-a720-3f1b225bd126&width=1248&dpr=4&quality=100&sign=b6ec2142&sv=2)

Creating a Squad

1.  Head over to [app.squads.so](https://app.squads.so/)
     and connect your Solana wallet by clicking the "Connect Wallet" button.
    

The app will automatically detect the compatible Solana wallets you have installed and show them in the "Connect your wallet" pop-up. If you do not have a wallet, you can also create and use a Squads account with your email via [TipLink](https://docs.squads.so/main/navigating-your-squad/in-app-integrations/tiplink)
.

Ledger Connect is not supported. If you're using a Ledger, connect through Phantom or Solflare wallets instead. Enable Blind Signing on your Ledger device to ensure successful transaction signing.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FU3APeqFjR83MhZ0XfoxP%252FScreenshot%25202024-06-25%2520at%252010.31.31%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D00870f3d-ff0b-4e25-b68d-2d718174aa01&width=768&dpr=4&quality=100&sign=2b809f16&sv=2)

Select wallet pop-up

1.  After connecting your wallet, click on the "Create a Squad" button.
    
2.  Enter your Squad's details (can be modified later):
    
    1.  Squad name
        
    2.  Profile picture (JPEG, PNG, or GIF formats, under 3MB)
        
    3.  Description (optional, limited to 64 characters)
        
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FHnv2S1X9QEGbet7DlFKf%252FSquad%2520details-1.png%3Falt%3Dmedia%26token%3D7f308bda-38e4-43b7-9b72-c58b02d66787&width=768&dpr=4&quality=100&sign=40e59b2e&sv=2)

Squad details

1.  Add members to your Squad with their public keys and set a confirmation threshold.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FtikeOqdeT8hcOq3vSHrS%252F3%2520theshold%29.png%3Falt%3Dmedia%26token%3D75a920b5-dc60-416f-b3c6-900a5d04fbec&width=768&dpr=4&quality=100&sign=d092f1e9&sv=2)

Squad members and confirmation threshold setup

The confirmation threshold determines the number of approvals required from Squad members for transaction execution. For example, a 2/3 threshold means two out of three wallets must approve a transaction for it to be executed.

Avoid setting the threshold at 1/1 signatures as it creates a single point of failure. Similarly, setting the threshold at maximum capacity may lead to access issues if control over one wallet is lost.

You can add up to 10 initial members. Additional members can be added after the Squad is created, subject to multisig approval based on the set confirmation threshold. Review the information once all members are added and click "Next".

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252F99jv57R1mIaoD5ddmr6W%252FReview%2520%28The%2520Squad%2520-%2520name%252C%2520team%2520funds%2520-%2520description%252C%2520photo%2520-%2520Squads%2520logo%29.png%3Falt%3Dmedia%26token%3Ddb07e9b4-1ea7-4580-aac6-1a70662b6cef&width=768&dpr=4&quality=100&sign=8b918a8e&sv=2)

Summary of your Squad's details

1.  On the final review screen, click "Confirm" to create your Squad. Once created, you can use the "Share" button in the pop-up to share the Squad URL with your team members.
    

Deploying a Squads multisig requires a small amount of SOL to cover a one-time 0.1 SOL deployment fee, 0.001 SOL to fund your Squads account, and ~0.0018 SOL in network rent for account deployment.

1.  Upon creation, you'll be directed to the "Treasury" tab. For guidance on navigating your Squads dashboard, please refer to the [Dashboard section](https://docs.squads.so/main/navigating-your-squad/dashboard)
    .
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252Fis6cXN22fVlIhZFWYzKi%252FTreasury%2520page%2520%28empty%2520treasury%252C%25200.03%2520dollar%2520balance%252C%25200.001%2520SOL%252C%25201%2520asset%29.png%3Falt%3Dmedia%26token%3Db0b6a438-c300-49b8-b9ae-61e8f86677f7&width=768&dpr=4&quality=100&sign=853bf826&sv=2)

Treasury tab

[PreviousQuickstart Guide](https://docs.squads.so/main/getting-started/quickstart-guide)
[NextOn and Off-Ramp](https://docs.squads.so/main/getting-started/on-and-off-ramp)

Last updated 4 months ago

---

# Payments | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FKWTdu0ROBYm9TPKbhKcm%252Fpayments%2520cover.png%3Falt%3Dmedia%26token%3D82040e2c-b2c5-40be-93eb-ede1a6fea686&width=1248&dpr=4&quality=100&sign=b62cf&sv=2)

Squads Payments is the next step in streamlining onchain payments.

The first iteration of Squads Payments introduces a “Recipients” feature to create, track, and manage recurring payments—eliminating manual entry and saving teams valuable time. Users only need to input recipient details, amounts, and payout schedules once. The system generates reminders and pre-filled payments at scheduled intervals, reducing administrative overhead and manual errors.

The “Send” feature on the “Dashboard” tab remains ideal for one-time transfers, while the “Recipients” feature is optimized for recurring transactions like payroll

Squads Payments is available to all Squads App subscribers, including [Business and Enterprise plans](https://docs.squads.so/main/getting-started/pricing)
.

Accessing the Payments tab requires sign-in authentication for public and private Squads, ensuring that sensitive payment data stays private.

### 

[](https://docs.squads.so/main/navigating-your-squad/payments#how-to-create-a-recurring-payment)

How to create a recurring payment:

1.  Head to the Payments tab, select “Add Recipient” and enter their details (name, address, email, position, tags).
    
2.  Specify details about the payment schedule by entering:
    
    *   Token and amount;
        
    *   Date of first payment
        
    *   End (specific date or after a particular number of payments)
        
    *   Frequency (weekly, biweekly, or monthly on a specific date)
        
    

The account you choose to make the payment from can be changed later.

1.  Review the details and click “Add” to create the payment.
    

### 

[](https://docs.squads.so/main/navigating-your-squad/payments#tracking-recurring-payments)

Tracking Recurring Payments

Everything you need to manage your recurring payments is available in the Payments tab. A new recipient is added to the “Recipients” overview five days before the first recurring payment. Each Recipient entry can have one of three statuses related to the recurring payment:

*   **Due:** the status updates to Due five days before payment is due.
    
*   **Overdue:** the status updates from Due to Overdue if a transaction has not been initiated, approved, and executed for a scheduled payment.
    
*   **Paid:** the status updates from Due or Overdue to Paid once the payment transaction has been initiated, approved, and executed.
    

Each recipient entry has all the important details like name, position, amount, periodicity, payment status, and tags for filtering with ease. Users can click on any Recipient entry to view more or edit that Recipient’s details and view the related payment history.

### 

[](https://docs.squads.so/main/navigating-your-squad/payments#managing-recurring-payments)

Managing recurring payments

Initiate and approve payments by selecting recipients with a “Due” status from the “Recipients” overview. After initiation, the related transaction will appear in the “Transactions” tab for final approval and execution based on your Squad's threshold.

Use the “Skip” function to bypass specific payments while maintaining the Recipient's regular payment schedule, and view finalized payments (meaning the recurring payment period is over) in the “Archive” folder for future reference.

#### 

[](https://docs.squads.so/main/navigating-your-squad/payments#how-to-pay-an-invoice)

How to pay an invoice:

1.  Select all the Recipients you want to pay in the Payments tab.
    

You can only select recipients (up to 15 at once) who are paid from the same subaccount.

1.  Click “Review” to continue and review the payments before executing.
    
2.  Once reviewed, click the “Approve” button to initiate the transaction. After initiation, the transaction can be approved and executed from the Transactions tab once the minimum confirmation threshold is met.
    

[PreviousAirdrop Checker](https://docs.squads.so/main/navigating-your-squad/treasury/airdrop-checker)
[NextTrade](https://docs.squads.so/main/navigating-your-squad/trade)

Last updated 1 year ago

---

# Sphere | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252F5zbDZdgyzuOXiF2EXJK9%252Fsphere.png%3Falt%3Dmedia%26token%3Df150822b-00cd-4ed2-a9ed-e8436dbc93b5&width=1248&dpr=4&quality=100&sign=585dc4e6&sv=2)

[](https://docs.squads.so/main/getting-started/on-and-off-ramp/sphere#what-is-sphere)

What Is Sphere?


----------------------------------------------------------------------------------------------------------

Sphere is a payments platform that bridges traditional finance and the onchain economy by streamlining the on-and off-ramping process.

[](https://docs.squads.so/main/getting-started/on-and-off-ramp/sphere#how-do-squads-users-benefit-from-this-integration)

How do Squads users benefit from this integration?


--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

You can now on-ramp assets to your Squads wallet and off-ramp to fiat in a secure and cost-effective way. This is enabled seamlessly via Wire, ACH, and SEPA transfers for both USD and EUR bank accounts.

[](https://docs.squads.so/main/getting-started/on-and-off-ramp/sphere#on-ramping-with-sphere-and-squads)

On-Ramping with Sphere & Squads


---------------------------------------------------------------------------------------------------------------------------------------------

Before using Sphere, make sure to set up an account and connect your bank account [here](https://spherepay.co/)
.

To on-ramp crypto with Sphere:

1.  Create a new Wire, ACH, or SEPA on-ramp on Sphere.
    
2.  When setting up a new on-ramp, select the bank account you'd like to send fiat from, choose Solana as the destination network, paste in your Squads vault address, and then select “Use Wallet”.
    
3.  Next, fill out the on-ramp form and click “Initiate”—your transfer will now be processed. Note that the transfer will either be processed automatically or you'll get wire instructions to manually complete the deposit.
    

On-ramp crypto to Squads

[](https://docs.squads.so/main/getting-started/on-and-off-ramp/sphere#off-ramping-with-sphere-and-squads)

Off-Ramping with Sphere & Squads


-----------------------------------------------------------------------------------------------------------------------------------------------

You can off-ramp from crypto to fiat in a single Squads transaction using [Sphere Offload](https://x.com/sphere_labs/status/1793691417480704456)
.

1.  In the “Payouts” section on Sphere, select the “Bank accounts” tab.
    
2.  Next, navigate to the bank account you'd like to off-ramp to and click the three dots in the “Actions” column, select “Generate wallet address” for the Solana network, and then click “Confirm”.
    
3.  In a couple of seconds, you should see “View wallets” in the “Linked wallets” column. Click on it. From the pop-up you'll be able to copy the Solana wallet address that is linked to your bank account—add it to your Squads contact book and use it whenever you'd like to off-ramp crypto to fiat.
    

Off-ramp crypto from Squads

Streamline the off-ramping process by creating a Spending Limit. For example, you can specify that your CTO can transfer USDC 1,000 per week to the off-ramp address without the standard Squads-required multisig approval.

[](https://docs.squads.so/main/getting-started/on-and-off-ramp/sphere#transfer-types)

Transfer types


---------------------------------------------------------------------------------------------------------

Sphere supports Wire, ACH, and SEPA transfers for both USD and EUR bank accounts.

Currently, Sphere only supports USD and EUR bank accounts—regardless in which jurisdiction the issuing bank is located in. This applies to e.g. multi-currency accounts (e.g. Wise/Revolut), and e.g. an Indonesian with a USD account.

[](https://docs.squads.so/main/getting-started/on-and-off-ramp/sphere#fees)

Fees


-------------------------------------------------------------------------------------

### 

[](https://docs.squads.so/main/getting-started/on-and-off-ramp/sphere#on-ramp)

On-ramp

1) Bank fees for sending Wire, ACH, or SEPA

2) 0.1% conversion fee (USD to USDC) and (EUR to USDC)

3) Solana network fee for sending funds to a Sphere-generated wallet address

### 

[](https://docs.squads.so/main/getting-started/on-and-off-ramp/sphere#off-ramp)

Off-Ramp

1) Solana network fee for sending funds to a Sphere-generated wallet address

2) 0.1% conversion fee (USDC to USD) and (USDC to EUR)

3) Bank fees for receiving Wire, ACH, or SEPA

[](https://docs.squads.so/main/getting-started/on-and-off-ramp/sphere#jurisdictions)

Jurisdictions


-------------------------------------------------------------------------------------------------------

Sphere supports transactions to any USD and EUR bank account that is located in a non-high-risk country, according to OFAC/FATF.

Unsupported countries/regions are [listed here](https://intercom.help/spherepay/en/articles/9516473-which-countries-can-i-use-sphere-from)
.

[PreviousVirtual US Bank Account](https://docs.squads.so/main/getting-started/on-and-off-ramp/virtual-us-bank-account)
[NextCoinflow Off-ramp](https://docs.squads.so/main/getting-started/on-and-off-ramp/coinflow-off-ramp)

Last updated 1 year ago

---

# Direct Staking | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FVoKROZr21blMiEgMD8nQ%252Fstakewiz.png%3Falt%3Dmedia%26token%3D784ca4af-720e-40d7-bfbd-158e0b60e2f0&width=1248&dpr=4&quality=100&sign=9ca029be&sv=2)

[](https://docs.squads.so/main/navigating-your-squad/stake/direct-staking#overview)

Overview


-------------------------------------------------------------------------------------------------

Users can stake their SOL holdings with Solana validators directly from their Squad.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FJdOn4JqrLKNrAai1qx4d%252FScreenshot%25202024-05-14%2520at%25205.15.32%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D3653b032-abaf-4086-979f-cc2e8bd62abe&width=768&dpr=4&quality=100&sign=2bf632bd&sv=2)

Validator Staking

**To stake SOL:**

1.  Navigate to the "Staking" tab and select "Validator" section.
    
2.  Select the validator you wish to stake with and select the amount of SOL you want to stake. You can use a filter to rank the validators by the amount of SOL delegated to them, the estimated APY, or use the search field to find the specific validator.
    

Staking happens in epochs that last approximately 3 days. If you stake during an ongoing epoch, you will start earning staking rewards after the start of the next epoch.

1.  Once you have selected a validator to stake with, click on the "Stake" button and launch a transaction.
    
2.  Your SOL will be staked upon the transaction execution. Once the new epoch starts, you will start earning rewards.
    
3.  The "Staked" switcher in the "Validator" section allows you to check the staked SOL amount and ROI you are receiving.
    

**To unstake SOL:**

1.  Navigate to the "Staking" tab and select the "Validator" section.
    
2.  Click on the "Staked" switcher and then click on the validator from which you wish to unstake your SOL.
    

3\. Click the "Unstake" button to launch a transaction.

Your unstaked SOL will be available for withdrawal **only** after the end of the epoch.

1.  Your SOL will start the deactivation period upon the transaction execution. The deactivation period finishes with the start of the new epoch.
    
2.  Once the deactivation period finishes, you will be able to withdraw your SOL. Navigate to the "Staked" switcher in the "Validator" section, click on the validator from which you are withdrawing the stake, and launch a transaction to complete the withdrawal.
    
3.  Your SOL will be returned to your vault upon transaction execution.
    

[PreviousStaking with Squads](https://docs.squads.so/main/navigating-your-squad/stake/staking-with-squads)
[NextLiquid Staking](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking)

Last updated 1 year ago

---

# Reporting and Accounting | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FiorTofNoKr0YFDozlHAU%252Freport.png%3Falt%3Dmedia%26token%3D74dd7c69-6316-4faf-a55f-602ace6d84d3&width=1248&dpr=4&quality=100&sign=d648b9c0&sv=2)

Users can use tools compatible with Squads to streamline their reporting and compliance processes:

*   [Request Finance](https://docs.squads.so/main/navigating-your-squad/reporting-and-accounting/request-finance)
    : Manage and automate accounting workflows;
    
*   [Integral](https://docs.squads.so/main/navigating-your-squad/reporting-and-accounting/integral)
    : Bookkeeping, treasury management, tax compliance, and auditing processes.
    

If you have any questions, reach out to [\[email protected\]](https://docs.squads.so/cdn-cgi/l/email-protection#026563707067767642717366712c6b6d)
 to learn more.

[PreviousCompatible Apps](https://docs.squads.so/main/navigating-your-squad/squadsx/compatible-apps)
[NextRequest Finance](https://docs.squads.so/main/navigating-your-squad/reporting-and-accounting/request-finance)

Last updated 5 months ago

---

# Stake | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FuFXJnbVyF9cpf4SNFq2f%252Fstake.png%3Falt%3Dmedia%26token%3D1f59e127-546f-4b68-a20c-f01fec4911a6&width=1248&dpr=4&quality=100&sign=7585f49&sv=2)

Staking is the best way to earn yield on your assets. Squads users can stake their SOL right from within the Squads app.

How to Stake inside the Squads app

Users can stake their SOL with any Solana validator (powered by Stakewiz), various liquid staking providers (fuseSOL, Jito, Marinade, SolBlaze, marginfi), Marinade Native, and the Squads Validator:

1.  [Staking with Squads](https://docs.squads.so/main/navigating-your-squad/stake/staking-with-squads)
    
2.  [Direct](https://docs.squads.so/main/navigating-your-squad/stake/direct-staking)
    
3.  [Liquid](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking)
    
4.  [Marinade Native](https://docs.squads.so/main/navigating-your-squad/stake/marinade-native)
    

[PreviousSwaps](https://docs.squads.so/main/navigating-your-squad/trade/swaps)
[NextStaking with Squads](https://docs.squads.so/main/navigating-your-squad/stake/staking-with-squads)

Last updated 1 year ago

---

# Commands | Development | Squads Docs

The following is an overview of commands available to interact with the Squads V4 program via CLI.

Overview

1.  Supported wallets
    
2.  Commands
    
    *   Create config transaction
        
    *   Execute config transaction
        
    *   Create multisig
        
    *   Vote on proposals
        
    *   Reclaim Vault Transaction rent
        
    *   Create new Vault Transaction
        
    *   Execute Vault Transaction
        
    

[](https://docs.squads.so/main/development/cli/commands#id-1.-supported-wallets)

1\. Supported wallets


-----------------------------------------------------------------------------------------------------------

The Squads CLI has exactly the same wallet support as the Solana CLI, meaning it supports file system wallets as well as Ledger hardware wallets.

#### 

[](https://docs.squads.so/main/development/cli/commands#file-system-wallets)

File system wallets

You can easily use your local filesystem wallet by using it as the "keypair" argument in commands.

Copy

    squads-multisig-cli example-command --keypair /path/to/keypair.json

This specifies the path of the Keypair that you want to use to sign a CLI transaction.

#### 

[](https://docs.squads.so/main/development/cli/commands#ledger-support)

Ledger support

To use a Ledger with the Squads CLI, just specify the Ledger device URL in the "keypair" argument.

Copy

    squads-multisig-cli example-command --keypair usb://ledger

This will use the default derivation path of your Ledger.

Copy

    squads-multisig-cli example-command --keypair usb://ledger/BsNsvfXqQTtJnagwFWdBS7FBXgnsK8VZ5CmuznN85swK?key=0/0

This specifies a custom derivation path. You can read more about it [here](https://docs.solana.com/wallet-guide/hardware-wallets/ledger)
.

[](https://docs.squads.so/main/development/cli/commands#id-2.-commands)

2\. Commands


-----------------------------------------------------------------------------------------

### 

[](https://docs.squads.so/main/development/cli/commands#config-transaction-create)

Config Transaction Create

#### 

[](https://docs.squads.so/main/development/cli/commands#description)

Description

Creates a new configuration proposal transaction for a specific action.

#### 

[](https://docs.squads.so/main/development/cli/commands#syntax)

Syntax

Copy

    config-transaction-create --rpc-url <RPC_URL> --program-id <PROGRAM_ID> --keypair <KEYPAIR_PATH> --multisig-pubkey <MULTISIG_PUBLIC_KEY> --action <ACTION> [--memo <MEMO>]

#### 

[](https://docs.squads.so/main/development/cli/commands#parameters)

Parameters

*   `--rpc-url <RPC_URL>`: (Optional) The URL of the Solana RPC endpoint. Defaults to mainnet if not specified.
    
*   `--program-id <PROGRAM_ID>`: (Optional) The ID of the multisig program. Defaults to a standard ID if not specified.
    
*   `--keypair <KEYPAIR_PATH>`: Path to your keypair file.
    
*   `--multisig-pubkey <MULTISIG_PUBLIC_KEY>`: The public key of the multisig account.
    
*   `--action <ACTION>`: The action to execute. Format depends on the action type.
    
*   `--memo <MEMO>`: (Optional) A memo for the transaction.
    

#### 

[](https://docs.squads.so/main/development/cli/commands#examples)

Examples

1.  **Add a New Member:**
    
    Copy
    
        config-transaction-create --keypair /path/to/keypair.json --multisig-pubkey <MULTISIG_PUBLIC_KEY> --action "AddMember <NEW_MEMBER_PUBLIC_KEY> <PERMISSIONS>"
    
    Adds a new member to the multisig configuration with specified permissions. Permissions: 1: Initiate only 7: All permissions (Initiate, Approve, Execute)
    
2.  **Remove a Member:**
    
    Copy
    
        config-transaction-create --keypair /path/to/keypair.json --multisig-pubkey <MULTISIG_PUBLIC_KEY> --action "RemoveMember <MEMBER_PUBLIC_KEY>"
    
    Removes an existing member from the multisig configuration.
    
3.  **Change Threshold:**
    
    Copy
    
        config-transaction-create --keypair /path/to/keypair.json --multisig-pubkey <MULTISIG_PUBLIC_KEY> --action "ChangeThreshold <NEW_THRESHOLD>"
    
    Changes the threshold number of signatures required for executing multisig transactions.
    
4.  **Set Time Lock:**
    
    Copy
    
        config-transaction-create --keypair /path/to/keypair.json --multisig-pubkey <MULTISIG_PUBLIC_KEY> --action "SetTimeLock <TIME_LOCK_VALUE>"
    
    Sets a time lock for the multisig account.
    
5.  **Add Spending Limit:**
    
    Copy
    
        config-transaction-create --keypair /path/to/keypair.json --multisig-pubkey <MULTISIG_PUBLIC_KEY> --action "AddSpendingLimit <CREATE_KEY> <VAULT_INDEX> <MINT> <AMOUNT> <PERIOD> <MEMBERS> <DESTINATIONS>"
    
    Adds a spending limit to the multisig account.
    
6.  **Remove Spending Limit:**
    
    Copy
    
        config-transaction-create --keypair /path/to/keypair.json --multisig-pubkey <MULTISIG_PUBLIC_KEY> --action "RemoveSpendingLimit <SPENDING_LIMIT_PUBKEY>"
    
    Removes an existing spending limit from the multisig account.
    
7.  **Set Rent Collector:**
    
    Copy
    
        config-transaction-create --keypair /path/to/keypair.json --multisig-pubkey <MULTISIG_PUBLIC_KEY> --action "SetRentCollector <NEW_RENT_COLLECTOR_PUBKEY>"
    
    Sets a new rent collector for the multisig account.
    

### 

[](https://docs.squads.so/main/development/cli/commands#config-transaction-execute)

Config Transaction Execute

#### 

[](https://docs.squads.so/main/development/cli/commands#description-1)

Description

Executes a proposed transaction for a multisig configuration change. This command is used to execute configuration transactions once they have reached threshold.

#### 

[](https://docs.squads.so/main/development/cli/commands#syntax-1)

Syntax

Copy

    config-transaction-execute --rpc-url <RPC_URL> --program-id <PROGRAM_ID> --keypair <KEYPAIR_PATH> --multisig-pubkey <MULTISIG_PUBLIC_KEY> --transaction-index <TRANSACTION_INDEX>

#### 

[](https://docs.squads.so/main/development/cli/commands#parameters-1)

Parameters

*   `--rpc-url <RPC_URL>`: (Optional) The URL of the Solana RPC endpoint. Defaults to mainnet if not specified.
    
*   `--program-id <PROGRAM_ID>`: (Optional) The ID of the multisig program. Defaults to a standard ID if not specified.
    
*   `--keypair <KEYPAIR_PATH>`: Path to your keypair file.
    
*   `--multisig-pubkey <MULTISIG_PUBLIC_KEY>`: The public key of the multisig account.
    
*   `--transaction-index <TRANSACTION_INDEX>`: The index of the transaction to be executed.
    

#### 

[](https://docs.squads.so/main/development/cli/commands#example-usage)

Example Usage

Copy

    config-transaction-execute --keypair /path/to/keypair.json --multisig-pubkey <MULTISIG_PUBLIC_KEY> --transaction-index 1

### 

[](https://docs.squads.so/main/development/cli/commands#multisig-create)

Multisig Create

#### 

[](https://docs.squads.so/main/development/cli/commands#description-2)

Description

Creates a new multisig with initial members and threshold configuration.

#### 

[](https://docs.squads.so/main/development/cli/commands#syntax-2)

Syntax

Copy

    multisig-create --rpc-url <RPC_URL> --program-id <PROGRAM_ID> --keypair <KEYPAIR_PATH> --config-authority <CONFIG_AUTHORITY> --members <MEMBER_1> <MEMBER_2> ... --threshold <THRESHOLD>

#### 

[](https://docs.squads.so/main/development/cli/commands#parameters-2)

Parameters

*   `--rpc-url <RPC_URL>`: (Optional) The URL of the Solana RPC endpoint. Defaults to mainnet if not specified.
    
*   `--program-id <PROGRAM_ID>`: (Optional) The ID of the multisig program. Defaults to a standard ID if not specified.
    
*   `--keypair <KEYPAIR_PATH>`: Path to your keypair file.
    
*   `--config-authority <CONFIG_AUTHORITY>`: (Optional) Address of the Program Config Authority.
    
*   `--members <MEMBER_...>`: List of members' public keys, separated by spaces.
    
*   `--threshold <THRESHOLD>`: The threshold number of signatures required for executing multisig transactions.
    

**Notes**

*   Stacking permissions for a single member requires adding up the permission mappings. For example, a member with full permissions (Proposer, Voter, Executor) would use a value of 7.
    
*   The permission types map to the following:
    
    *   Proposer - 1
        
    *   Voter - 2
        
    *   Executor - 4
        
    *   All of the above - 7
        
    

#### 

[](https://docs.squads.so/main/development/cli/commands#example-usage-1)

Example Usage

1.  **Creating a Multisig with Two Members:**
    
    Copy
    
        multisig-create --keypair /path/to/keypair.json --members "Member1PubKey,Permission1" "Member2PubKey,Permission2" --threshold 2
    
    Creates a new multisig account with two members and a threshold of 2.
    
2.  **Creating a Multisig with Config Authority:**
    
    Copy
    
        multisig-create --keypair /path/to/keypair.json --config-authority <CONFIG_AUTHORITY_PUBKEY> --members "Member1PubKey,Permission1" "Member2PubKey,Permission2" --threshold 1
    
    Initializes a multisig account with a specified config authority and a threshold of 1.
    

### 

[](https://docs.squads.so/main/development/cli/commands#proposal-vote)

Proposal Vote

#### 

[](https://docs.squads.so/main/development/cli/commands#description-3)

Description

Casts a vote on a proposed transaction proposal. This command allows a member of a multisig to approve, reject, or cancel a transaction proposal.

#### 

[](https://docs.squads.so/main/development/cli/commands#syntax-3)

Syntax

Copy

    proposal-vote --rpc-url <RPC_URL> --program-id <PROGRAM_ID> --keypair <KEYPAIR_PATH> --multisig-pubkey <MULTISIG_PUBLIC_KEY> --transaction-index <TRANSACTION_INDEX> --action <ACTION> [--memo <MEMO>]

#### 

[](https://docs.squads.so/main/development/cli/commands#parameters-3)

Parameters

*   `--rpc-url <RPC_URL>`: (Optional) The URL of the Solana RPC endpoint. Defaults to mainnet if not specified.
    
*   `--program-id <PROGRAM_ID>`: (Optional) The ID of the multisig program. Defaults to a standard ID if not specified.
    
*   `--keypair <KEYPAIR_PATH>`: Path to your keypair file.
    
*   `--multisig-pubkey <MULTISIG_PUBLIC_KEY>`: The public key of the multisig account.
    
*   `--transaction-index <TRANSACTION_INDEX>`: The index of the transaction to vote on.
    
*   `--action <ACTION>`: The vote action to cast (Approve, Reject, Cancel).
    
*   `--memo <MEMO>`: (Optional) A memo for the vote.
    

#### 

[](https://docs.squads.so/main/development/cli/commands#example-usage-2)

Example Usage

1.  **Approving a Transaction:**
    
    Copy
    
        proposal-vote --keypair /path/to/keypair.json --multisig-pubkey <MULTISIG_PUBLIC_KEY> --transaction-index 1 --action Approve
    
    Casts an approval vote for the transaction at index 1 in the specified multisig account.
    
2.  **Rejecting a Transaction:**
    
    Copy
    
        proposal-vote --keypair /path/to/keypair.json --multisig-pubkey <MULTISIG_PUBLIC_KEY> --transaction-index 1 --action Reject
    
    Casts a rejection vote for the transaction at index 1.
    
3.  **Cancelling a Transaction:**
    
    Copy
    
        proposal-vote --keypair /path/to/keypair.json --multisig-pubkey <MULTISIG_PUBLIC_KEY> --transaction-index 1 --action Cancel
    
    Cancels the transaction at index 1 in the multisig account.
    

### 

[](https://docs.squads.so/main/development/cli/commands#vault-transaction-accounts-close)

Vault Transaction Accounts Close

#### 

[](https://docs.squads.so/main/development/cli/commands#description-4)

Description

Closes the proposal and transaction accounts associated with a specific Vault Transaction. The rent will be returned to the multisigs "rent\_collector".

#### 

[](https://docs.squads.so/main/development/cli/commands#syntax-4)

Syntax

Copy

    vault-transaction-accounts-close --rpc-url <RPC_URL> --program-id <PROGRAM_ID> --keypair <KEYPAIR_PATH> --multisig-pubkey <MULTISIG_PUBLIC_KEY> --transaction-index <TRANSACTION_INDEX> --rent-collector <RENT_COLLECTOR_PUBKEY>

#### 

[](https://docs.squads.so/main/development/cli/commands#parameters-4)

Parameters

*   `--rpc-url <RPC_URL>`: (Optional) The URL of the Solana RPC endpoint. Defaults to mainnet if not specified.
    
*   `--program-id <PROGRAM_ID>`: (Optional) The ID of the multisig program. Defaults to a standard ID if not specified.
    
*   `--keypair <KEYPAIR_PATH>`: Path to your keypair file.
    
*   `--multisig-pubkey <MULTISIG_PUBLIC_KEY>`: The public key of the multisig account.
    
*   `--transaction-index <TRANSACTION_INDEX>`: The index of the transaction whose accounts are to be closed.
    
*   `--rent-collector <RENT_COLLECTOR_PUBKEY>`: The public key of the account responsible for collecting rent.
    

#### 

[](https://docs.squads.so/main/development/cli/commands#example-usage-3)

Example Usage

Copy

    vault-transaction-accounts-close --keypair /path/to/keypair.json --multisig-pubkey <MULTISIG_PUBLIC_KEY> --transaction-index 1 --rent-collector <RENT_COLLECTOR_PUBKEY>

In this example, the command closes the transaction accounts for the transaction at index 1 in the specified multisig account and collects rent using the provided rent collector public key.

### 

[](https://docs.squads.so/main/development/cli/commands#vault-transaction-create)

Vault Transaction Create

#### 

[](https://docs.squads.so/main/development/cli/commands#description-5)

Description

Creates a new vault transaction with a custom transaction message.

#### 

[](https://docs.squads.so/main/development/cli/commands#syntax-5)

Syntax

Copy

    vault-transaction-create --rpc-url <RPC_URL> --program-id <PROGRAM_ID> --keypair <KEYPAIR_PATH> --multisig-pubkey <MULTISIG_PUBLIC_KEY> --vault-index <VAULT_INDEX> --transaction-message <TRANSACTION_MESSAGE> [--memo <MEMO>]

#### 

[](https://docs.squads.so/main/development/cli/commands#parameters-5)

Parameters

*   `--rpc-url <RPC_URL>`: (Optional) The URL of the Solana RPC endpoint. Defaults to mainnet if not specified.
    
*   `--program-id <PROGRAM_ID>`: (Optional) The ID of the multisig program. Defaults to a standard ID if not specified.
    
*   `--keypair <KEYPAIR_PATH>`: Path to your keypair file.
    
*   `--multisig-pubkey <MULTISIG_PUBLIC_KEY>`: The public key of the multisig account.
    
*   `--vault-index <VAULT_INDEX>`: The index of the vault where the transaction is being created.
    
*   `--transaction-message <TRANSACTION_MESSAGE>`: The message or payload of the transaction.
    
*   `--memo <MEMO>`: (Optional) A memo for the transaction.
    

#### 

[](https://docs.squads.so/main/development/cli/commands#example-usage-4)

Example Usage

Copy

    vault-transaction-create --keypair /path/to/keypair.json --multisig-pubkey <MULTISIG_PUBLIC_KEY> --vault-index 1 --transaction-message [1, 2, 3, 5, 5, 6, 7, 8]

In this example, a new transaction with the specified message is proposed in the multisig vault at vault index 1.

### 

[](https://docs.squads.so/main/development/cli/commands#vault-transaction-execute)

Vault Transaction Execute

#### 

[](https://docs.squads.so/main/development/cli/commands#description-6)

Description

Executes a transaction once the proposal has reached threshold.

#### 

[](https://docs.squads.so/main/development/cli/commands#syntax-6)

Syntax

Copy

    vault-transaction-execute --rpc-url <RPC_URL> --program-id <PROGRAM_ID> --keypair <KEYPAIR_PATH> --multisig-pubkey <MULTISIG_PUBLIC_KEY> --transaction-index <TRANSACTION_INDEX>

#### 

[](https://docs.squads.so/main/development/cli/commands#parameters-6)

Parameters

*   `--rpc-url <RPC_URL>`: (Optional) The URL of the Solana RPC endpoint. Defaults to mainnet if not specified.
    
*   `--program-id <PROGRAM_ID>`: (Optional) The ID of the multisig program. Defaults to a standard ID if not specified.
    
*   `--keypair <KEYPAIR_PATH>`: Path to your keypair file.
    
*   `--multisig-pubkey <MULTISIG_PUBLIC_KEY>`: The public key of the multisig account.
    
*   `--transaction-index <TRANSACTION_INDEX>`: The index of the transaction to be executed.
    

#### 

[](https://docs.squads.so/main/development/cli/commands#example-usage-5)

Example Usage

Copy

    vault-transaction-execute --keypair /path/to/keypair.json --multisig-pubkey <MULTISIG_PUBLIC_KEY> --transaction-index 1

This example executes the transaction at index 1 in the specified multisig.

[PreviousInstallation](https://docs.squads.so/main/development/cli/installation)
[NextWe're here to help](https://docs.squads.so/main/development/get-support/were-here-to-help)

Last updated 8 months ago

---

# Key aspects of using a multisig | Squads Docs

By using a multisig, it is important to acknowledge certain concepts. Here are some points to have in mind when using a multisig:

*   **Loss of Private Keys**. Always keep a backup of your private keys added as members to your multisig. If a key is lost, it could impact the multisig operations if a specific number of signatures are needed to reach the threshold.
    
*   **Single Point of Failure with Keys**. For added security, consider storing keys in different secure locations. Otherwise a single breach can compromise the whole set up.
    
*   **Threshold.** Be sure everyone in the multisig understands the number of signatures required for transactions, so you always have the needed approvals.
    
*   **No Succession Planning.** If keyholders become unavailable (e.g., due to accident, death), without a plan for transition, funds may be locked forever.
    
*   **Transfer of Funds to Wrong Address.** Funds should always be sent to the multisig vault account, and not the multisig account address. Due to the design of the Squads Protocol program, funds deposited to the multisig account may not be recovered.
    
*   **Config Authority**. If the config\_authority of a multisig is compromised, an attacker can change multisig settings, potentially reducing the required threshold for transaction execution or instantly being able to remove and add new members (changing config\_authority ownership is only possible programatically and is subject to threshold requirements).
    
*   **SVM Forks**. If the underlying SVM compatible blockchain undergoes a fork and a user had sent funds to the orphaned chain, the state of the blockchain may not interpret the owner of funds to be original one.
    
*   **Time Locks**. While setting time locks be certain of the duration you are comfortable with so your funds remain accessible when needed.
    
*   **SOL for Network Fees**. Always ensure multisig participants maintain a minimum balance of the native token needed for transaction fees.
    

[PreviousWhat if the Squads app goes down](https://docs.squads.so/main/additional-resources/what-if-the-squads-app-goes-down)

Last updated 1 year ago

---

# Sending assets to/from centralized exchange (CEXs) | Squads Docs

Each Squads address represents a special account on the Solana blockchain referred to as "PDA". As a result, some exchanges may have limitations in fully supporting asset transfers to or from Squads multisigs, with these restrictions varying by region.

Please refer to the following list if you plan to use Squads frequently with centralized exchanges:

Exchange

Receive (from Squads multisig)

Deposit (into Squads multisig)

Coinbase

Binance

Kraken

Backpack

OKX

Swissborg

Bybit

Bitget

Please proceed with caution and test with small amounts whenever you're sending assets to/from a CEX. If you have any questions, please reach out to us on [Discord](https://discord.com/invite/YPXz64TrKs)
.

[PreviousCosts of using Squads](https://docs.squads.so/main/additional-resources/costs-of-using-squads)
[NextSquads on Mobile](https://docs.squads.so/main/additional-resources/squads-on-mobile)

Last updated 10 months ago

---

# Developers assets | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FcmuT5QoAmoum28wlcHmr%252Fdev%2520assets.png%3Falt%3Dmedia%26token%3Dd210780f-37e1-4169-bd22-a1c3184c6c76&width=1248&dpr=4&quality=100&sign=72bb0d00&sv=2)

This section is dedicated to teams and protocols that wish to manage their programs, native tokens, and validators with multisig.

Additionally, advanced users can create arbitrary instructions through the Transaction Builder, allowing them to perform actions with on-chain assets stored in or managed by their Squad, as well as to interact with protocols not natively integrated within Squads.

1.  [Programs](https://docs.squads.so/main/navigating-your-squad/developers-assets/programs)
    
2.  [Validators](https://docs.squads.so/main/navigating-your-squad/developers-assets/validators)
    
3.  [Token Manager](https://docs.squads.so/main/navigating-your-squad/developers-assets/token-manager)
     (available to all Squads App subscribers, including [Business and Enterprise plans](https://docs.squads.so/main/getting-started/pricing)
    )
    
4.  [Transaction Builder](https://docs.squads.so/main/navigating-your-squad/developers-assets/transaction-builder)
    

[PreviousMarinade Native](https://docs.squads.so/main/navigating-your-squad/stake/marinade-native)
[NextPrograms](https://docs.squads.so/main/navigating-your-squad/developers-assets/programs)

Last updated 1 year ago

---

# Staking with Squads | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FdelFMVzaENcnJT5dbyaJ%252Fsquads.png%3Falt%3Dmedia%26token%3D60ec4583-84c3-46eb-9b91-653dc3ce29cd&width=1248&dpr=4&quality=100&sign=903717f0&sv=2)

Users can stake their SOL with the Squads Validator directly from the Squads app.

Stake your SOL with the Squads Validator in the "Staking" tab by following the steps provided in [Direct Staking](https://docs.squads.so/main/navigating-your-squad/stake/direct-staking)
.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FwTeExTu6ulnX6LqkI5DT%252FSquads%2520Validator.png%3Falt%3Dmedia%26token%3Deb4ccfea-edc8-41ae-bd5f-ec396fb6584e&width=768&dpr=4&quality=100&sign=3b45eb3&sv=2)

Squads Validator in the Staking Tab

[PreviousStake](https://docs.squads.so/main/navigating-your-squad/stake)
[NextDirect Staking](https://docs.squads.so/main/navigating-your-squad/stake/direct-staking)

Last updated 1 year ago

---

# Members | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FhLVcPHAOJzyIakfNefH2%252Fmembers.png%3Falt%3Dmedia%26token%3D1e5ea549-a0b0-46d6-817e-ccc96feb2ee2&width=1248&dpr=4&quality=100&sign=114dc0f2&sv=2)

The "Members" tab allows Squad members to:

*   View Squad members
    
*   Initiate transactions to add or remove members
    
*   Rename wallet addresses of members (locally saved, visible only to the person who modified the name)
    
*   Navigate to members' Twitter profiles (if linked via [SNS](https://docs.squads.so/main/navigating-your-squad/integrated-apps/sns)
    )
    

Read more about adding, removing and managing members [here](https://docs.squads.so/main/navigating-your-squad/members/manage-members)
.

[Business and Enterprise plan](https://docs.squads.so/main/getting-started/pricing)
 users can also:

*   Set [permissions](https://docs.squads.so/main/navigating-your-squad/members/permissions)
     for members
    
*   Turn on the [Fee Relayer](https://docs.squads.so/main/navigating-your-squad/members/fee-relayer)
    
*   Add the [SquadsX browser extension](https://docs.squads.so/main/navigating-your-squad/squadsx)
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252Fsjhw1WAC6uwtxf5c2xem%252FScreenshot%25202024-11-13%2520at%25205.51.37%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3De836768f-e1f2-4a0f-85c8-95e858855692&width=768&dpr=4&quality=100&sign=d1d3b391&sv=2)

Members Page

[PreviousRent Reclaim](https://docs.squads.so/main/navigating-your-squad/transactions/rent-reclaim)
[NextManage Members](https://docs.squads.so/main/navigating-your-squad/members/manage-members)

Last updated 1 year ago

---

# Marinade Native | Squads Docs

Users can stake SOL with Marinade Native directly from the Squads app. The strategy automatically rebalances the stake across the 140 best-performing validators and has no smart contract exposure as users retain full custody of their SOL and stake accounts.

**To stake SOL through Marinade Native:**

1.  Navigate to the Treasury page.
    
2.  Locate the "Stake" button and click on it.
    
3.  Insert the SOL amount you want to stake and click on "Stake" to initiate a transaction.
    
4.  Your SOL will be staked upon the transaction execution. Once the new epoch starts, you will start earning rewards.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252Fg8z3NBYa7oIV7IjQPwPx%252FScreenshot%25202023-12-15%2520at%252012.09.49.png%3Falt%3Dmedia%26token%3D9fe3d12b-fa03-4486-b31c-82660ef5b6f9&width=768&dpr=4&quality=100&sign=75234e45&sv=2)

Locate the "Stake" button

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FcZlnPXGvBMvLWLlKDWQR%252FScreenshot%25202023-12-15%2520at%252012.08.37.png%3Falt%3Dmedia%26token%3D8484b9ba-9bcc-4389-afa4-1c2faa89393b&width=768&dpr=4&quality=100&sign=598f2876&sv=2)

Stake SOL with Marinade Native

**To unstake SOL:**

1.  Navigate to the "Staking" tab and select the "Validator" section.
    
2.  Click on the "Staked" switcher and then click on the Marinade Native block.
    
3.  Click the "Unstake" button to initiate a transaction.
    

Your unstaked SOL will be available for withdrawal **only** after the end of the epoch.

1.  Your SOL will start the deactivation period upon the transaction execution. The deactivation period finishes with the start of the new epoch.
    
2.  Once the deactivation period finishes, you will be able to withdraw your SOL. Navigate to the "Staked" switcher in the "Validator" section, click on the Marinade Native block, and launch a transaction to complete the withdrawal.
    
3.  Your SOL will be returned to your vault upon transaction execution.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FtDqBrGh5J5yhl7WDqt1S%252FScreenshot%25202023-12-15%2520at%252012.30.17.png%3Falt%3Dmedia%26token%3D24e80a51-6c81-4dd3-acb8-168ccf81ba88&width=768&dpr=4&quality=100&sign=c5a29ecf&sv=2)

Unstake your SOL from Marinade Native

[PreviousLiquid Staking](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking)
[NextDevelopers assets](https://docs.squads.so/main/navigating-your-squad/developers-assets)

Last updated 1 year ago

---

# Virtual US Bank Account | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FLgxaWlD23wJY7cdWaKJJ%252Fvirtual%2520US.png%3Falt%3Dmedia%26token%3Dcddf0ecb-dfe8-4f4b-adda-511fd06f68fb&width=1248&dpr=4&quality=100&sign=ed75df53&sv=2)

Powered by [Bridge](https://www.bridge.xyz/)
, users can now set up virtual US bank accounts to receive payments in USD, which is seamlessly converted to USDC in their Squad account.

1.  [How It Works](https://docs.squads.so/main/getting-started/on-and-off-ramp/virtual-us-bank-account#how-it-works)
    
2.  [Transfer Limits](https://docs.squads.so/main/getting-started/on-and-off-ramp/virtual-us-bank-account#transfer-limits)
    
3.  [User Eligibility](https://docs.squads.so/main/getting-started/on-and-off-ramp/virtual-us-bank-account#user-eligibility)
    

### 

[](https://docs.squads.so/main/getting-started/on-and-off-ramp/virtual-us-bank-account#how-it-works)

How It Works

With a virtual US bank account, receiving USD payments as USDC in your Squads account is simple:

*   Automatic USD-to-USDC conversion
    
*   No need for multiple platforms or transfers
    
*   Avoid costly on-ramp fees
    

Senders use familiar USD bank transfers, while you receive USDC in your Squad account—all for a minimal 0.1% conversion fee.

### 

[](https://docs.squads.so/main/getting-started/on-and-off-ramp/virtual-us-bank-account#transfer-limits)

Transfer Limits

**US residents**

*   From your business bank account: no limit
    
*   From individuals: not supported
    
*   From businesses: no limits
    
*   From payroll platforms such as Deel, Gusto, and Upwork: no limits
    

**Non-US residents**

*   From your business bank account: no limits
    
*   From individuals: $4,000 per transaction
    
*   From businesses: no limits
    
*   From payroll platforms such as Deel, Gusto, and Upwork: no limits
    

### 

[](https://docs.squads.so/main/getting-started/on-and-off-ramp/virtual-us-bank-account#user-eligibility)

User Eligibility

**Availability**

Virtual US bank accounts are available for users in most of the US, Canada, Europe, Australia, UAE, Japan, India and many other countries around the world.

**Restrictions**

For US businesses, virtual US bank accounts are not available to those with principal residential or operating addresses in New York and Alaska. Also, virtual US bank accounts are not available to businesses with principal residential or operating addresses in the countries listed below.

*   Afghanistan
    
*   Albania
    
*   Algeria
    
*   Bangladesh
    
*   Belarus
    
*   Central African Republic
    
*   China
    
*   Cuba
    
*   Democratic Republic of the Congo
    
*   Eritrea
    
*   Ethiopia
    
*   Gaza Strip
    
*   Iran
    
*   Iraq
    
*   Kenya
    
*   Kosovo
    
*   Lebanon
    
*   Libya
    
*   Mali
    
*   Morocco
    
*   Myanmar
    
*   Nepal
    
*   Nicaragua
    
*   Niger
    
*   North Korea
    
*   North Macedonia
    
*   Pakistan
    
*   Qatar
    
*   Russian Federation
    
*   Slovenia
    
*   Somalia
    
*   South Sudan
    
*   Sudan
    
*   Syria
    
*   Ukraine
    

[PreviousOn and Off-Ramp](https://docs.squads.so/main/getting-started/on-and-off-ramp)
[NextSphere](https://docs.squads.so/main/getting-started/on-and-off-ramp/sphere)

Last updated 3 months ago

---

# Spending Limits | Squads Docs

Spending limits allow Squad members to move a certain amount of assets from the treasury without requiring full Squad approval.

**To add a Spending Limit:**

1.  Navigate to the "Settings" tab.
    
2.  Click the "Add Spending Limit" button.
    
3.  Specify the parameters and click the "Initiate" button.
    

**Spending limit parameters include:**

1.  **Account:** The account from which a member will be able to withdraw funds.
    
2.  **Token and max amount:** Specify the token and its maximum withdrawal amount. Currently, a member can set only one token per spending limit.
    
3.  **Time frame:** The period during which the spending limit is active. The amount available for withdrawal will be reset at the beginning of a new time frame period. If a member sets "None," the spending limit will be active until the full token amount is withdrawn.
    
4.  **Destination:** Wallet addresses for fund withdrawals (multiple can be added).
    

After setting a spending limit, it can be viewed on the member's card or in the "Settings" tab for editing.

Make sure you regularly monitor active spending limits to ensure they align with your operations. Reserve them for trusted members and update them frequently to reflect organizational changes or if a member leaves the project.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FLgOzxVWWWzPrY32UT9bi%252Fimage.png%3Falt%3Dmedia%26token%3D70cbd1b1-b95c-407b-9cd4-e0781f19dff9&width=768&dpr=4&quality=100&sign=24edce54&sv=2)

Spending limits settings

[PreviousSettings](https://docs.squads.so/main/navigating-your-squad/settings)
[NextCoin List Filter](https://docs.squads.so/main/navigating-your-squad/settings/coin-list-filter)

Last updated 1 year ago

---

# Integral | Squads Docs

[](https://docs.squads.so/main/navigating-your-squad/reporting-and-accounting/integral#what-is-integral)

What is Integral?


-------------------------------------------------------------------------------------------------------------------------------

[Integral](https://integral.xyz/)
 is a powerful accounting and treasury tool for crypto trams. It is used for streamlining bookkeeping, treasury management, tax compliance, and auditing processes.

[](https://docs.squads.so/main/navigating-your-squad/reporting-and-accounting/integral#how-do-squads-users-benefit-from-integral)

How do Squads users benefit from Integral?


---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Once Squads users have set up an account on Integral, they can seamlessly integrate their Squads App address by copying and pasting it into the platform.

This integration provides a comprehensive overview of all your onchain activities — giving you access to detailed insights that enable you to effortlessly meet your compliance requirements and maintain accurate records of your onchain transactions.

If you have any questions, reach out to [\[email protected\]](https://docs.squads.so/cdn-cgi/l/email-protection#731412010116070733000217005d1a1c)
 to learn more.

[PreviousRequest Finance](https://docs.squads.so/main/navigating-your-squad/reporting-and-accounting/request-finance)
[NextFAQs](https://docs.squads.so/main/additional-resources/faqs)

Last updated 11 months ago

---

# Costs of using Squads | Squads Docs

### 

[](https://docs.squads.so/main/additional-resources/costs-of-using-squads#network-fees)

**Network fees**

Network fees can vary slightly depending on the action performed inside a Squad. This happens due to differences in the weights of instructions, which require different spaces on the blockchain.

*   **Withdrawing SPL tokens** \- 0.0051 SOL
    
*   **Withdrawing NFT** - 0.0104 SOL
    
*   **Stake SOL with a liquid provider** - 0.0094 SOL
    
*   **Stake SOL with a validator** - 0.0106 SOL
    
*   **Add member** \- 0.0037 SOL
    
*   **Remove member** - 0.0044 SOL
    
*   **Change threshold** - 0.0042 SOL
    
*   **Create time lock** - 0.0069 SOL
    
*   **Create a Spending limit** - 0.0076 SOL
    
*   **Enable the fee relayer -** 0.0681 SOL
    

Transactions executed with Squads have higher network fees than wallets like Phantom and Backpack because Squads uses [smart accounts](https://squads.so/blog/smart-account-basics-why-smart-accounts-will-power-the-onchain-economy)
 to enforce multisig logic. Smart accounts require more computation and storage than traditional non-programmable accounts. A portion of these fees are due to [network rent](https://solana.com/docs/core/fees#rent:~:text=the%20fees%20paid.-,Rent%20%23,-The%20fee%20deposited)
 (related to storage) which can be recouped using our [Rent Reclaim](https://docs.squads.so/main/navigating-your-squad/transactions#rent-reclaim)
 feature. All fees are charged by the Solana network; Squads does not charge fees on transactions except the [Limit Order](https://docs.squads.so/main/navigating-your-squad/trade/limit-orders)
 fees shown below.

### 

[](https://docs.squads.so/main/additional-resources/costs-of-using-squads#platform-fees)

**Platform fees**

**Squads Deployment Fee** \- 0.1 SOL

**Limit Orders** - 0.25%

[**Squads Business Plan**](https://docs.squads.so/main/getting-started/pricing)
 (optional) - $49 per month

[PreviousAdvanced Security Best Practices](https://docs.squads.so/main/additional-resources/advanced-security-best-practices)
[NextSending assets to/from centralized exchange (CEXs)](https://docs.squads.so/main/additional-resources/sending-assets-to-from-centralized-exchange-cexs)

Last updated 4 months ago

---

# Request Finance | Squads Docs

[](https://docs.squads.so/main/navigating-your-squad/reporting-and-accounting/request-finance#what-is-request-finance)

What is Request Finance?


----------------------------------------------------------------------------------------------------------------------------------------------------

Request Finance is an all-in-one finance platform for crypto and fiat operations making it easy for teams to manage and automate accounting workflows for their business. It offers accounting features to help keep your team organized:

*   All-in-one dashboard: Create, track, and reconcile invoices and produce and download reports on transactions, cash flow, and journal entries in one unified dashboard
    
*   Transactions automation: Create rules and categorize your transactions effortlessly using automation, all in one place
    
*   Multi-platform support: Import transactions from 80+ networks, 20+ exchanges, and 100+ wallets
    
*   Software integration: Effortlessly sync with popular tools such as QuickBooks and Xero
    

[](https://docs.squads.so/main/navigating-your-squad/reporting-and-accounting/request-finance#how-do-squads-users-benefit-from-request)

How do Squads users benefit from Request?


--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Teams can now connect their Squads account to Request Finance to create, manage, and pay invoices seamlessly.

Using [SquadsX](https://docs.squads.so/main/navigating-your-squad/squadsx)
, teams can connect their Squads account to Request Finance to:

*   Create and manage professional invoices that automatically sync with Squads for streamlined payment approval and execution
    
*   Monitor approval and payment status through Request Finance's “Billing” dashboard, with direct links to Squads transactions for complete payment visibility.
    

[](https://docs.squads.so/main/navigating-your-squad/reporting-and-accounting/request-finance#how-to-get-started)

How to get started?


------------------------------------------------------------------------------------------------------------------------------------------

Squads users can get started with a 2-month free trial of Request Finance using [this link](https://www.request.finance/partners/squads)
.

Using Request Finance with Squads

If you have any questions, reach out to [\[email protected\]](https://docs.squads.so/cdn-cgi/l/email-protection#224543505047565662515346510c4b4d)
 to learn more.

[PreviousReporting and Accounting](https://docs.squads.so/main/navigating-your-squad/reporting-and-accounting)
[NextIntegral](https://docs.squads.so/main/navigating-your-squad/reporting-and-accounting/integral)

Last updated 11 months ago

---

# Time Locks | Squads Docs

Time locks allow Squad members to defer the execution of approved transactions for a set period of time.

*   Time locks apply globally to all Squad transactions once set.
    
*   "Active" transactions and "Ready" transactions for changing Squad settings initiated before the time lock will change to a "Canceled" state upon activation.
    
*   Available periods: 1 hour, 1 day, 1 week, Custom (in seconds), None (disables the time lock).
    

To create a time lock:

1.  Navigate to the "Settings" tab.
    
2.  Select the desired time lock period and initiate a transaction.
    
3.  The time lock activates upon transaction execution.
    

Choose a time lock duration that balances security with accessibility of funds. Avoid excessively long periods (e.g. 1 month) if regular asset management is expected.

[PreviousPrivacy](https://docs.squads.so/main/navigating-your-squad/settings/privacy)
[NextIntegrated apps](https://docs.squads.so/main/navigating-your-squad/integrated-apps)

Last updated 1 year ago

---

# SquadsX | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FE0PuunqQgeIBNOm4QIhC%252Fsolana-multisig-wallet-squadsx-smart-contract-wallet-solana-account-abstraction-multisig-aa-squads-wallet-extension-multisig-transactions.png%3Falt%3Dmedia%26token%3D4f3a07e9-d401-41df-8fab-7ca6875524df&width=1248&dpr=4&quality=100&sign=29b9845d&sv=2)

The Squads browser extension, SquadsX, is one of the products available to all Squads App subscribers, including [Business and Enterprise plans](https://docs.squads.so/main/getting-started/pricing)
.

SquadsX is used to connect your Squad to Solana apps. Learn how to get started with the extension and explore what possibilities it opens:

1.  [Get Started](https://docs.squads.so/main/navigating-your-squad/squadsx/start-using-squadsx)
    
2.  [Compatible Apps and Use Cases](https://docs.squads.so/main/navigating-your-squad/squadsx/compatible-apps)
    

SquadsX is still in beta, bugs or compatibility issues may occur.

[PreviousSafe](https://docs.squads.so/main/navigating-your-squad/integrated-apps/safe)
[NextStart using SquadsX](https://docs.squads.so/main/navigating-your-squad/squadsx/start-using-squadsx)

Last updated 1 year ago

---

# What if the Squads app goes down | Squads Docs

[](https://docs.squads.so/main/additional-resources/what-if-the-squads-app-goes-down#squads-backup-kit)

Squads Backup Kit


------------------------------------------------------------------------------------------------------------------------------

In the unlikely event that the Squads app would be unavailable for a long period, we have put in place multiple options to allow users to access their assets:

1\. Squads minimal UI

2\. CLI Tool

3\. SDK

This is an open-source interface that allows you to interact with the Squads program where your assets sit. You can fork it and host it locally to access your Squads account(s) and then, for instance, withdraw your assets.

The Squads minimal UI can be found on our official GitHub: [https://github.com/Squads-Protocol/public-v4-client](https://github.com/Squads-Protocol/public-v4-client)

Note that this UI primarily focuses on emergency actions (e.g. withdrawing funds or programs) in case the Squads main app is inaccessible for too long. We do not encourage using it as your main app as it is not optimized and far from the experience you get on app.squads.so.

Another way to interact with your Squads account(s) is through the Command-line interface (CLI) we have built. The Squads CLI has exactly the same wallet support as the Solana CLI, which means it supports file system wallets as well as Ledger hardware wallets.

This CLI can be used from any computer terminal to access your assets stored on Squads.

For a walk through on how to install and use the Squads CLI, follow this guide: [https://docs.squads.so/main/v/development/squads-cli/installation](https://docs.squads.so/main/v/development/squads-cli/installation)

Additionally, we also have an SDK for those ready to build their own simple UI to interact with the Squads program and access their assets that way rather than via the official Squads app.

The Squads SDK can be found here: [https://www.npmjs.com/package/@sqds/multisig](https://www.npmjs.com/package/@sqds/multisig)

Interacting with an SDK requires developer knowledge and is best suited for technical users. If you have limited technical skills or need quick access to your assets, we recommend using the Squads minimal UI or the CLI tool

Remember, all your assets are stored in the Squads multisig program onchain, and Squads Labs never has control over your funds nor can access them.

In the unlikely event that Squads Labs ceases operations or the main UI becomes inaccessible, your assets remain secure. Only you have the authority to move them using your private key/wallet.

[PreviousSquads on Mobile](https://docs.squads.so/main/additional-resources/squads-on-mobile)
[NextKey aspects of using a multisig](https://docs.squads.so/main/additional-resources/key-aspects-of-using-a-multisig)

Last updated 1 month ago

---

# SNS | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FQdUPny2zB7PCdCdL652L%252Fsns.png%3Falt%3Dmedia%26token%3D33bbafbf-242c-4032-80b4-3c00f937c598&width=1248&dpr=4&quality=100&sign=f2187f35&sv=2)

[](https://docs.squads.so/main/navigating-your-squad/integrated-apps/sns#what-is-sns)

What is SNS?


-------------------------------------------------------------------------------------------------------

[SNS](https://www.sns.id/)
 is a protocol on Solana that created the "Solana Naming Service". With SNS, you can create a .sol domain name that links to your wallet address. SNS domains can be used as a replacement to classic SPL addresses for receiving crypto transfers on Solana.

[](https://docs.squads.so/main/navigating-your-squad/integrated-apps/sns#how-do-squads-users-benefit-from-this-integration)

How do Squads users benefit from this integration?


-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

By abstracting away wallet addresses, everyday crypto activities such as sending & receiving crypto and accounting for on-chain transactions become a much easier process. Instead of needing to remember a long string of random letters and numbers, Squads Protocol users can simply enter .sol domains, simplifying the entire process.

[](https://docs.squads.so/main/navigating-your-squad/integrated-apps/sns#how-to-send-cryptos-to-.sol-domains)

How to send cryptos to .sol domains?


-------------------------------------------------------------------------------------------------------------------------------------------------------

Sending crypto to .sol domains via SNS is simple. Simply enter the .sol domain instead of the wallet address.

[PreviousRange](https://docs.squads.so/main/navigating-your-squad/integrated-apps/range)
[NextSafe](https://docs.squads.so/main/navigating-your-squad/integrated-apps/safe)

Last updated 1 year ago

---

# Range | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FRiEk6OZ5nduBr9hq2cpt%252FRange%25202.jpeg%3Falt%3Dmedia%26token%3D83a23344-99bb-44a6-9298-a06303e25cd2&width=1248&dpr=4&quality=100&sign=32d45b22&sv=2)

[](https://docs.squads.so/main/navigating-your-squad/integrated-apps/range#what-is-range)

What is Range?


-------------------------------------------------------------------------------------------------------------

Range is a security platform designed to protect you from scams, hacks, and unintended mistakes that could compromise the integrity of your Squads account.

We chose Range for its accuracy, speed, and proven track record with leading organizations such as the Solana Foundation, Etherfuse, Agant, and Perena.

[](https://docs.squads.so/main/navigating-your-squad/integrated-apps/range#how-do-squads-users-benefit-from-this-integration)

How do Squads users benefit from this integration?


-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

By integrating Range's simulation API, we can provide clearer explanations of how transactions will impact your Squad and flag potentially risky or malicious transactions in real-time—before they are signed.

In this context, Range is particularly helpful for non-technical users who e.g. might be tricked by a custom instruction granting access to funds or changing the authority of a program.

[PreviousTipLink](https://docs.squads.so/main/navigating-your-squad/integrated-apps/tiplink)
[NextSNS](https://docs.squads.so/main/navigating-your-squad/integrated-apps/sns)

Last updated 10 months ago

---

# Squads on Mobile | Squads Docs

The Squads app can also be used on mobile devices via in-app browsers of mobile wallets like:

*   Phantom;
    
*   Backpack;
    
*   Solfare, and more.
    

### 

[](https://docs.squads.so/main/additional-resources/squads-on-mobile#connecting-to-squads-on-mobile)

Connecting to Squads on mobile:

1.  Open the browser tab on your mobile wallet. Go to [app.squads.so](https://app.squads.so/)
     and click the "Connect" button.
    
2.  Connect your wallet and you will be redirected to your default Squad's dashboard.
    

If you have a Squad on Squads Protocol v3, go to [v3.squads.so](https://v3.squads.so/squads)
 on your wallet browser to access your Squads.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252Fk6WNzoe69YU6rSqPGqtO%252Fimage.png%3Falt%3Dmedia%26token%3Db04cfa9b-bcc9-4031-bffb-585cc949e2f5&width=768&dpr=4&quality=100&sign=59fa06fc&sv=2)

Squads on mobile

The Squads app on the Solana Saga mobile device is built on top of Squads Protocol v3 and is actively maintained. Please migrate to [app.squads.so](https://app.squads.so/squads)
 for the optimal mobile experience.

[PreviousSending assets to/from centralized exchange (CEXs)](https://docs.squads.so/main/additional-resources/sending-assets-to-from-centralized-exchange-cexs)
[NextWhat if the Squads app goes down](https://docs.squads.so/main/additional-resources/what-if-the-squads-app-goes-down)

Last updated 1 year ago

---

# Dashboard | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FISpPseFuRGeHqQCnxq1c%252Fdashboard.png%3Falt%3Dmedia%26token%3Dd889d69d-8436-4b4e-9f0f-c51bbf36fb76&width=1248&dpr=4&quality=100&sign=6a5562b2&sv=2)

The Dashboard helps you monitor all your assets and operations and perform quick actions like token swaps or transaction approvals.

### 

[](https://docs.squads.so/main/navigating-your-squad/dashboard#breakdown-of-the-dashboard-tab)

Breakdown of the Dashboard tab

#### 

[](https://docs.squads.so/main/navigating-your-squad/dashboard#overview-section)

Overview Section

This section provides a comprehensive overview of your Squad:

*   **Squad Information**: View essential details such as your Squad's address, approval threshold, and member count.
    
*   **Quick Actions**:
    
    *   Send funds (to external wallets, between sub-accounts, or initiate [off-ramp](https://docs.squads.so/main/getting-started/on-and-off-ramp)
        )
        
    *   Deposit assets
        
    *   Swap tokens (powered by [Jupiter](https://docs.squads.so/main/navigating-your-squad/trade)
        )
        
    
*   **Treasury Performance**: Track historical data on your Squad's asset performance.
    
*   **Sub-accounts**: Get an overview of each sub-account, including stored SPL tokens and NFTs.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FhRc0skrGlenGdXZUO3FQ%252FDashboard-1.png%3Falt%3Dmedia%26token%3D7d6306d5-7fa1-4bad-80ec-e2c421009647&width=768&dpr=4&quality=100&sign=5b95e789&sv=2)

Overview section

#### 

[](https://docs.squads.so/main/navigating-your-squad/dashboard#limit-orders)

**Limit Orders**

Monitor and manage your Squad's trading activities:

*   View currently open limit orders;
    
*   Access the history of all previous orders.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FZ9DP8xNaRQzRQd4NBxlu%252FScreenshot%25202024-06-27%2520at%25201.44.34%25E2%2580%25AFAM.png%3Falt%3Dmedia%26token%3D009cb7bb-6356-4aaa-9a74-1302b78ef716&width=768&dpr=4&quality=100&sign=af10b933&sv=2)

Limit order section

#### 

[](https://docs.squads.so/main/navigating-your-squad/dashboard#streams-from-streamflow)

**Streams from Streamflow**

For users who have set up vesting plans on Streamflow: track ongoing and outgoing streams linked to your Squads multisig.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FiRWUTRNUSMZa20Ekpiiq%252Fimage.png%3Falt%3Dmedia%26token%3D2525ed66-cd6f-46b7-9f3f-4482cb2120a9&width=768&dpr=4&quality=100&sign=704e22a1&sv=2)

Streams section

#### 

[](https://docs.squads.so/main/navigating-your-squad/dashboard#active-transactions)

**Active transactions**

Stay on top of your Squad's operations:

*   View active and ready transactions
    
*   Execute transactions directly from this section
    

#### 

[](https://docs.squads.so/main/navigating-your-squad/dashboard#inflows-and-outflows)

**Inflows and Outflows**

Keep track of your Squad's financial movements with a detailed history of all deposits and withdrawals

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FJeRr8RQmU0co6ytDDTPO%252FDashboard-2.png%3Falt%3Dmedia%26token%3Dac88c93b-9512-4fdf-9de4-7791ed8e8940&width=768&dpr=4&quality=100&sign=179028e1&sv=2)

Active transactions, inflows and outflows sections

#### 

[](https://docs.squads.so/main/navigating-your-squad/dashboard#stake)

**Stake**

Manage your staked SOL:

*   See the amount of SOL deposited and its current state (staked/unstaked)
    
*   View a breakdown of liquid stake providers and validators used for staking
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252F7kwF2LFY621xYtJoeLlh%252FDashboard-3.png%3Falt%3Dmedia%26token%3D4069749d-80e5-4eca-a22e-e0023f9d1e58&width=768&dpr=4&quality=100&sign=af92f427&sv=2)

Stake section

#### 

[](https://docs.squads.so/main/navigating-your-squad/dashboard#managed-assets)

**Managed assets**

Oversee all developer assets delegated to your Squad:

*   Programs,
    
*   Validators,
    
*   Tokens,
    
*   and NFT collections.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FtvFfJpwAlGvu8hVCrK2h%252FDashboard-4.png%3Falt%3Dmedia%26token%3D4da7f70d-7b98-4175-80ce-127a127228ab&width=768&dpr=4&quality=100&sign=bf29cfec&sv=2)

Managed assets section

[PreviousPricing](https://docs.squads.so/main/getting-started/pricing)
[NextTransactions](https://docs.squads.so/main/navigating-your-squad/transactions)

Last updated 1 year ago

---

# Pricing | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FpDmV3le4wpVTCMo1GCYW%252Fsub.png%3Falt%3Dmedia%26token%3Daa471164-2a73-42c6-b808-56df0734f2b3&width=1248&dpr=4&quality=100&sign=25a1c126&sv=2)

Squads offers a three-tier model that makes the Squads App accessible for all teams building and transacting onchain. Our pricing aligns with our mission to accelerate the onchain economy and reflects our business model driven by scalable software and our conviction in crypto's exponential growth.

### 

[](https://docs.squads.so/main/getting-started/pricing#plans)

Plans

Here is our three-tier model:

Basic

Pro

Enterprise

#### 

[](https://docs.squads.so/main/getting-started/pricing#usd0-per-month)

$0 per month

Enterprise-grade security for a one-time 0.1 SOL deployment fee.

*   A secure smart account with unlimited members
    
*   [Basic treasury management](https://docs.squads.so/main/getting-started/treasury-management-overview)
    
*   [Squads Trade](https://docs.squads.so/main/navigating-your-squad/trade)
    
*   [Staking](https://docs.squads.so/main/navigating-your-squad/stake)
    
*   [Program management](https://docs.squads.so/main/navigating-your-squad/developers-assets/programs)
    
*   [Batch actions](https://docs.squads.so/main/navigating-your-squad/transactions/batch-actions)
    
*   [Developer transaction builder](https://docs.squads.so/main/navigating-your-squad/developers-assets/transaction-builder)
    
*   [Validator management](https://docs.squads.so/main/navigating-your-squad/developers-assets/validators)
    
*   [Ul privacy](https://docs.squads.so/main/navigating-your-squad/settings/privacy)
    

#### 

[](https://docs.squads.so/main/getting-started/pricing#usd49-per-month)

$49 per month

Gain access to everything in Basics, plus features that help you accelerate your business and scale your onchain operations:

*   [Permissions](https://docs.squads.so/main/navigating-your-squad/members/permissions)
    
*   [Payments](https://docs.squads.so/main/navigating-your-squad/payments)
    
*   [Sub-accounts](https://docs.squads.so/main/navigating-your-squad/treasury/sub-accounts)
    
*   [SquadsX browser extension](https://docs.squads.so/main/navigating-your-squad/squadsx)
    
*   [Fee relayer](https://docs.squads.so/main/navigating-your-squad/members/fee-relayer)
    
*   [Token Management](https://docs.squads.so/main/navigating-your-squad/developers-assets/token-manager)
    

Users can access the Squads Pro plan and all its features for free for 30 days.

#### 

[](https://docs.squads.so/main/getting-started/pricing#custom-pricing)

Custom Pricing

Our Enterprise plan is a tailor-made offering for your business with custom implementations, dedicated support, and onboarding. Gain access to everything in Pro, plus:

*   Unlimited smart accounts
    
*   Assisted onboarding
    
*   Premium 24/7 support
    
*   Reporting and compliance integrations
    

Please reach out to [\[email protected\]](https://docs.squads.so/cdn-cgi/l/email-protection#741315060611000034070510075a1d1b)
 to learn more.

If you have an active subscription based on our legacy subscription offering, we will extend your account access under the new Squads Pro plan terms based on the remaining time and amount you’ve paid. If you prefer a refund of the remaining time period or have any questions please reach out to [\[email protected\]](https://docs.squads.so/cdn-cgi/l/email-protection#036462717166777743707267702d6a6c)
 or message us on [Twitter](https://x.com/SquadsProtocol)
.

### 

[](https://docs.squads.so/main/getting-started/pricing#how-to-subscribe-to-the-squads-pro-plan)

**How to subscribe to the Squads Pro Plan**

1.  Go to the "Subscriptions" page.
    
2.  Choose the "Pro" plan option and select the preferred payment method. You get the first 30 days of Squads Pro for free.
    
3.  When you subscribe, a [spending limit](https://docs.squads.so/main/navigating-your-squad/settings/spending-limits)
     worth $49 in USDC is created, enabling us to pull this amount from your Squads vault at the start of each month.
    

If there’s insufficient USDC in your Squad on the first of the month, you’ll have 7 days to fund your account. After that, subscription features will no longer be accessible.

[PreviousTreasury Management Overview](https://docs.squads.so/main/getting-started/treasury-management-overview)
[NextDashboard](https://docs.squads.so/main/navigating-your-squad/dashboard)

Last updated 4 months ago

---

# Integrated apps | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252F4TNnmEgTs7jBGVAi9wtp%252Fintegrated%2520apps.png%3Falt%3Dmedia%26token%3Daad196c6-5f54-4ba5-8de0-17cecca15a44&width=1248&dpr=4&quality=100&sign=57e50a5b&sv=2)

1.  [Sending assets & creating an account with email](https://docs.squads.so/main/navigating-your-squad/integrated-apps/tiplink)
     - Powered by TipLink
    
2.  [Transaction Risk Scanner](https://docs.squads.so/main/navigating-your-squad/integrated-apps/range)
     - Powered by Blowfish
    
3.  [.sol domains](https://docs.squads.so/main/navigating-your-squad/integrated-apps/sns)
     - Powered by Bonfida
    
4.  [Adding Safe wallet](https://docs.squads.so/main/navigating-your-squad/integrated-apps/safe)
     - In Partnership with Safe
    

[PreviousTime Locks](https://docs.squads.so/main/navigating-your-squad/settings/time-locks)
[NextTipLink](https://docs.squads.so/main/navigating-your-squad/integrated-apps/tiplink)

Last updated 11 months ago

---

# Transactions | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FCLGLypg2TbmsKZLo8Gmy%252Ftransactions.png%3Falt%3Dmedia%26token%3D5372e815-4d49-4cea-8971-27cfc1ae6958&width=1248&dpr=4&quality=100&sign=d886cfd0&sv=2)

How transactions work inside Squads

### 

[](https://docs.squads.so/main/navigating-your-squad/transactions#how-transactions-work-inside-squads)

How transactions work inside Squads

Transactions are a key element of the Squads platform. They are initiated whenever a Squad member performs an action requiring approval from other members.

#### 

[](https://docs.squads.so/main/navigating-your-squad/transactions#transaction-states)

Transaction States

Transactions can exist in one of three states:

1.  **Active**: Pending signatures from other Squad members to reach the confirmation threshold.
    
2.  **Ready**: Confirmation threshold met; the transaction is now executable.
    
3.  **Canceled**: Transaction terminated by Squad members or due to changes in Squad parameters.
    

### 

[](https://docs.squads.so/main/navigating-your-squad/transactions#transactions-tab)

**Transactions tab**

The "Transactions" tab provides a chronological display of all Squad transactions. It enables users to:

*   Change [priority fees](https://docs.squads.so/main/navigating-your-squad/transactions/priority-fees)
     for transactions
    
*   Use [batch actions](https://docs.squads.so/main/navigating-your-squad/transactions/batch-actions)
     to execute transactions in bulk
    
*   [Reclaim rent](https://docs.squads.so/main/navigating-your-squad/transactions/rent-reclaim)
     for executed transactions
    
*   [Approve/reject transactions](https://docs.squads.so/main/navigating-your-squad/transactions#how-to-approve-reject-transactions)
    
*   [Execute/cancel transactions](https://docs.squads.so/main/navigating-your-squad/transactions#how-to-execute-cancel-transactions)
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FWlkgQFajp2e2FM3pB66t%252FTransactions%2520list.png%3Falt%3Dmedia%26token%3D726fed9a-287c-4eea-ae95-dca18cdc3b2e&width=768&dpr=4&quality=100&sign=f4111917&sv=2)

Transactions tab

### 

[](https://docs.squads.so/main/navigating-your-squad/transactions#how-to-approve-reject-transactions)

**How to approve/reject transactions**

Any action (e.g., member management, token transfers, program upgrades) initiates a transaction in the "Ready" state. It only executes once the Squad's confirmation threshold is met. The initiating member automatically confirms the transaction.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FGU9MTgahZSGBisLFMoc9%252FActive%2520tx%2520epxanded%2520NEW.png%3Falt%3Dmedia%26token%3D4ce4c1eb-c5ef-4c52-839c-b9165f7e2ede&width=768&dpr=4&quality=100&sign=dd548f31&sv=2)

Active transaction. Expanded view

Other members can approve or reject transactions by:

*   Expanding the transaction in the list view
    
*   Clicking "See details" for a comprehensive view
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FqQSnWC1GgEadvc3RJiZw%252FTransaction%2520detailed%2520active.png%3Falt%3Dmedia%26token%3D80f57d79-4fe9-4c04-84e0-d5ed14b97b63&width=768&dpr=4&quality=100&sign=d6cb9d3d&sv=2)

Detailed view

### 

[](https://docs.squads.so/main/navigating-your-squad/transactions#how-to-execute-cancel-transactions)

**How to execute/cancel transactions**

Once the confirmation threshold is met, a transaction in the "Ready" state can be executed or canceled based on the signatures of other Squad members.

*   **Execution**: Once the confirmation threshold is met, any Squad member can execute the "Ready" transaction.
    
*   **Cancellation**: Requires reaching the confirmation threshold for canceling the transaction.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FcA8ykGSRVMs27WAJdnnn%252FReady%2520tx.png%3Falt%3Dmedia%26token%3D2979dcee-47c9-41eb-864c-f0b1f291c7bc&width=768&dpr=4&quality=100&sign=2b126c30&sv=2)

"Ready" transaction

Learn how to export your transactions as a CSV in our guide here.

[PreviousDashboard](https://docs.squads.so/main/navigating-your-squad/dashboard)
[NextPriority fees](https://docs.squads.so/main/navigating-your-squad/transactions/priority-fees)

Last updated 5 months ago

---

# Bridge Off-Ramp | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FlE6ClCpbIUVlikgJuv0g%252Fbridge%2520xyz.png%3Falt%3Dmedia%26token%3D8c6f75b3-0911-44f6-8c66-68e0f7a740b3&width=1248&dpr=4&quality=100&sign=a3f683a1&sv=2)

Squads users can now seamlessly off-ramp USDC to their business bank account with multiple options through [Bridge](https://www.bridge.xyz/)
 Off-Ramp.

1.  [How It Works](https://docs.squads.so/main/getting-started/on-and-off-ramp/bridge-off-ramp#how-it-works)
    
2.  [Options And Fees](https://docs.squads.so/main/getting-started/on-and-off-ramp/bridge-off-ramp#options-and-fees)
    
3.  [User Eligibility](https://docs.squads.so/main/getting-started/on-and-off-ramp/bridge-off-ramp#user-eligibility)
    

### 

[](https://docs.squads.so/main/getting-started/on-and-off-ramp/bridge-off-ramp#how-it-works)

How It Works

To access Bridge Off-Ramp:

*   Navigate to your Dashboard
    
*   Select "Send"
    
*   Choose "Off-ramp"
    
*   Select "Bridge"
    
*   Complete the KYB process to verify eligibility
    

### 

[](https://docs.squads.so/main/getting-started/on-and-off-ramp/bridge-off-ramp#options-and-fees)

Options And Fees

Multiple transfer methods are available.

**Wire Transfer**

*   Fee: $20 + 0.5%
    
*   Settlement: Within 1 business day (fastest option)
    

**ACH Same Day**

*   Fee: $1 + 0.5%
    
*   Settlement: Within 1 business day
    

**Standard ACH**

*   Fee: $0.50 + 0.5%
    
*   Settlement: 2-3 business days
    

**SEPA Transfer**

*   Fee: $1.00 + 0.5%
    
*   Settlement: 1-5 business days
    

### 

[](https://docs.squads.so/main/getting-started/on-and-off-ramp/bridge-off-ramp#user-eligibility)

User Eligibility

**Availability**

Bridge Off-Ramp services are currently limited to business entities through a dedicated KYB verification. Individual user verification (KYC) is not supported at this time. Geographically, Bridge Off-Ramp is available to most users in the US, Canada, UK, and Europe. **Restrictions** For US residents, the service is unavailable for those with principal resident or operating addresses in New York, Florida, Alaska, and Louisiana. Bridge Off-Ramp is also not available for those with principal resident or operating addresses in the countries listed below.

*   Afghanistan
    
*   Albania
    
*   Algeria
    
*   Bangladesh
    
*   Belarus
    
*   Central African Republic
    
*   China
    
*   Cuba
    
*   Democratic Republic of the Congo
    
*   Eritrea
    
*   Ethiopia
    
*   Gaza Strip
    
*   Iran
    
*   Iraq
    
*   Kenya
    
*   Kosovo
    
*   Lebanon
    
*   Libya
    
*   Mali
    
*   Morocco
    
*   Myanmar
    
*   Nepal
    
*   Nicaragua
    
*   Niger
    
*   North Korea
    
*   North Macedonia
    
*   Pakistan
    
*   Qatar
    
*   Russian Federation
    
*   Slovenia
    
*   Somalia
    
*   South Sudan
    
*   Sudan
    
*   Syria
    
*   Ukraine
    
*   Venezuela
    
*   West Bank
    
*   Yemen
    
*   Zimbabwe
    

[PreviousCoinflow Off-ramp](https://docs.squads.so/main/getting-started/on-and-off-ramp/coinflow-off-ramp)
[NextThird-Party Payouts](https://docs.squads.so/main/getting-started/on-and-off-ramp/third-party-payouts)

Last updated 9 months ago

---

# Transaction Builder | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252F1uRLQK1TAnofweADPe87%252Ftx%2520builder.png%3Falt%3Dmedia%26token%3D430b7674-f55e-4afc-9f73-339ae17ca951&width=1248&dpr=4&quality=100&sign=2cb0a158&sv=2)

Users can create custom transactions and populate them with arbitrary instructions using the Transaction Builder. This allows them to interact directly with any programs on Solana from a Squad.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252F1XL4MbYaq5EfgNQfasQ4%252FTransaction%2520builder.png%3Falt%3Dmedia%26token%3D015f55b0-4438-47b9-9b97-689ab2d5ce86&width=768&dpr=4&quality=100&sign=1ecf8046&sv=2)

TX Builder tab

### 

[](https://docs.squads.so/main/navigating-your-squad/developers-assets/transaction-builder#how-to-create-a-custom-transaction-draft)

**How to create a custom transaction draft**

**To create a custom transaction draft:**

1.  Go to the "TX Builder" tab and click the "Create transaction" button. If you already know the type of transaction you want to create, click on one of the templates.
    
2.  Choose the type of transaction you would like to create:
    
    *   Anchor programs (with IDL)
        
    *   Solana programs (written in Rust)
        
    *   Import a base58 encoded transaction
        
    *   Validators (using predefined templates)
        
    *   Switchboard program
        
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FWWAtRDSzsEjyB2x2ahI3%252FTransaction%2520builder-1.png%3Falt%3Dmedia%26token%3D1c67fffe-9eb5-4354-8ddb-f3590aaf17da&width=768&dpr=4&quality=100&sign=d6b76dce&sv=2)

Select transaction type

All custom transactions are initially saved as drafts and need to be populated with instructions data before launching. You can save your custom transaction after initiation for future reuse.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252Fn7a9vfjJ5BcZja2eyAm1%252FTransaction%2520builder-2.png%3Falt%3Dmedia%26token%3D658fc7ac-e2ff-4429-ba05-776e600ca85d&width=768&dpr=4&quality=100&sign=bcf056fe&sv=2)

Transaction draft

1.  Once you've selected the type, you'll be taken to the draft screen where you can add instructions to the transaction.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252F37FMvzW5TxpjdqYIE8rJ%252FTransaction%2520builder-8.png%3Falt%3Dmedia%26token%3D0109ebbc-6acb-453c-8562-3774c42f4fc9&width=768&dpr=4&quality=100&sign=af7a448d&sv=2)

Populated transaction draft

### 

[](https://docs.squads.so/main/navigating-your-squad/developers-assets/transaction-builder#how-to-populate-custom-transaction-drafts-with-instructions)

How to populate custom transaction drafts with instructions

**To populate a custom transaction draft for programs written in Anchor:**

1.  To add a custom instruction, click on the draft and select "Add instruction" from the dropdown menu.
    
2.  Choose the "Custom instruction" option and enter the program address. Click "Next".
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252F29uyKQn5eEx0K4QAW9Io%252FTransaction%2520builder-3.png%3Falt%3Dmedia%26token%3D92232be4-ade3-4b0b-937f-49ce15c5afe3&width=768&dpr=4&quality=100&sign=83eaf39d&sv=2)

Anchor transaction

1.  Select the desired instruction from the list and click "Add instruction".
    
2.  Fill out the required information in the Accounts section and click "Save draft". If necessary, you can add additional instructions to the draft to run multiple custom instructions in one transaction. You can also provide a name and description for the transaction.
    

After you populate the draft with arbitrary instructions you can run a simulation to check if your transaction is assembled correctly.

1.  After you populate the transaction with instructions and run a simulation to verify that everything is correct, launch a transaction inside your Squad by clicking on "Initiate Transaction". The custom transaction with arbitrary instructions will be launched upon transaction execution.
    

#### 

[](https://docs.squads.so/main/navigating-your-squad/developers-assets/transaction-builder#to-populate-a-custom-transaction-draft-for-programs-written-in-rust)

**To populate a custom transaction draft for programs written in Rust**

1.  To add a custom instruction, click on the draft and then click "Add instruction". Select the "Custom instruction" option.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FqKIlqcpIR9WXae8B5q1l%252FTransaction%2520builder-5.png%3Falt%3Dmedia%26token%3D54932ef2-a5da-4880-b01e-7b64f907a421&width=768&dpr=4&quality=100&sign=fe9971c2&sv=2)

Rust transaction

1.  Insert the program address, and then click "Add instruction".
    
2.  Enter the account information and select the desired data options (Buffer or Raw). Finally, click "Save draft". You can add another instruction inside the draft to run two custom instructions in one transaction.
    

After populating the draft with arbitrary instructions, you can run a simulation to check if your transaction is assembled correctly.

1.  Once you have populated the transaction with instructions and run a simulation to verify that everything is correct, launch the transaction inside your Squad by clicking on "Initiate Transaction". The custom transaction with arbitrary instructions will be launched upon transaction execution.
    

#### 

[](https://docs.squads.so/main/navigating-your-squad/developers-assets/transaction-builder#to-populate-the-draft-with-instructions-from-base58-encoded-transactions)

**To populate the draft with instructions from base58 encoded transactions**

1.  To add an instruction, click on the draft and select "Add instruction". Then, choose the "Import base58 encoded tx" option.
    
2.  Insert the base58 encoded transaction and click "Next". Review the data and click "Add instruction".
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252F04cTkb1FwO3NI4htJyhY%252FTransaction%2520builder-4.png%3Falt%3Dmedia%26token%3D5fc27d84-698e-44dc-b766-e5af1266b437&width=768&dpr=4&quality=100&sign=bca77784&sv=2)

Base 58 transaction

1.  Once you have verified the data and run a simulation to ensure its correctness, initiate a transaction within your Squad by clicking on "Initiate Transaction". This will launch a custom transaction with arbitrary instructions upon execution.
    

#### 

[](https://docs.squads.so/main/navigating-your-squad/developers-assets/transaction-builder#to-interact-with-the-validators-and-stake-pools-using-predefined-templates)

**To interact with the validators and stake pools using predefined templates**

1.  Click on "Add instruction".
    
2.  Select the template you want to use from the list: Stake program, Vote program, Stake Pool program, or Switchboard program.
    

**The Stake Program template** allows you to interact with validators to deactivate and withdraw staked SOL.

**The Vote Program template** enables you to change the withdraw authority, withdraw stake rewards, and change the commission of the validator.

**The Stake Pool Program template** lets you set the manager, fees, and funding authority of the stake pool.

**Switchboard Program template** allows you to interact with, create, and manage feeds from a multisig in Switchboard.

1.  Populate any of the templates with the required data and launch a transaction. Once the transaction meets confirmation threshold and is executed, the interaction with the program will be made.
    

[PreviousToken Manager](https://docs.squads.so/main/navigating-your-squad/developers-assets/token-manager)
[NextSettings](https://docs.squads.so/main/navigating-your-squad/settings)

Last updated 1 year ago

---

# Coinflow Off-ramp | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252F6uoUVNoPPD504YTfCYbe%252Fcoinflow.png%3Falt%3Dmedia%26token%3D44bdda35-a03a-472e-bb81-ccccec38ed3f&width=1248&dpr=4&quality=100&sign=c526f807&sv=2)

Coinflow off-ramping is currently only available for individuals and businesses with bank accounts in the US.

[](https://docs.squads.so/main/getting-started/on-and-off-ramp/coinflow-off-ramp#what-is-coinflow)

What is Coinflow?


-------------------------------------------------------------------------------------------------------------------------

Coinflow develops software bridging conventional finance and blockchain tech, enabling users to purchase digital assets and services using standard payment methods. With top-tier US bank collaborations, Coinflow provides instant 24/7 crypto off-ramping to user bank accounts.

[](https://docs.squads.so/main/getting-started/on-and-off-ramp/coinflow-off-ramp#how-to-off-ramp-assets-to-a-bank-account)

How to off-ramp assets to a bank account


------------------------------------------------------------------------------------------------------------------------------------------------------------------------

1.  Navigate to the "Dashboard" of your Squad and click the "Send" button.
    
2.  Choose the "Off-ramp" option in the pop-up.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252F95rOCsURNzmtQ2dnTfnt%252Fimage.png%3Falt%3Dmedia%26token%3D33cf470c-962e-4245-aece-b8d326b8cc13&width=768&dpr=4&quality=100&sign=5d311cdf&sv=2)

Send popup

1.  Select "Coinflow" as the off-ramp option.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FXes5cV1NTZ31W43S2mmL%252Fimage.png%3Falt%3Dmedia%26token%3D47fe8cc0-9c4c-471f-8195-d9a4e8ff65ee&width=768&dpr=4&quality=100&sign=46c4e85c&sv=2)

Coinflow off-ramp popup

1.  Enter your email and country of residence. Click "Next" to continue to the KYC/KYB process.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FEEdfghdjbdpkf2tKXXAh%252FScreenshot%25202024-12-05%2520at%25203.53.50%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D2c2d5b1d-d76d-446e-9874-19ecc5fdd697&width=768&dpr=4&quality=100&sign=6434b432&sv=2)

Withdrawal Verification

1.  To continue, select your account type as "Individual" or "Business". Click the "Next" button to complete the KYC (for individuals) or KYB (for businesses) verification.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FtymDE9kYTRRwarctQNNl%252FScreenshot%25202024-12-05%2520at%25203.54.17%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3Dd490bbfd-1cc9-482d-88d2-e2c31e61b93c&width=768&dpr=4&quality=100&sign=444c67d7&sv=2)

1.  Complete the verification process to continue with the off-ramp process.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FGBBVfUYedxFQPkg6wtVh%252FScreenshot%25202024-12-05%2520at%25203.54.44%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D5445f2b9-441e-47ed-aee0-a9b958627653&width=768&dpr=4&quality=100&sign=10534b2c&sv=2)

1.  Once your KYC/KYB process is complete and verified, you will be able to continue. Choose the account you want to send funds from and the account that will receive USD.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FwqACeCsLAdTS7jFG2XdD%252Fimage.png%3Falt%3Dmedia%26token%3D86649421-544b-4045-b366-3f1fcf84a33a&width=768&dpr=4&quality=100&sign=d80a035f&sv=2)

Off-ramping

1.  Add a new bank account by filling in the following details:
    

*   Account owner
    
*   Account type
    
*   Bank name and type
    
*   Beneficiary address
    
*   Routing number
    
*   Account number
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FPasX15xcgfsuolhCWzLX%252Fimage.png%3Falt%3Dmedia%26token%3D64fcc779-fe39-43e8-9d71-b872683b5fdc&width=768&dpr=4&quality=100&sign=45ecaf18&sv=2)

Bank account details

1.  Enter the amount you want to send and the type of transaction. Click the "Next" button to review your transaction.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FRpOLw2soaN6hDwpG03xS%252Fimage.png%3Falt%3Dmedia%26token%3D5f06fc70-499a-4f24-b01c-8ee83b7c99d4&width=768&dpr=4&quality=100&sign=f6ece024&sv=2)

Amount and Transaction speed

1.  Once reviewed, initiate the transaction. You will receive USD in your bank account once your transaction is complete according to the chosen transaction type.
    

[PreviousSphere](https://docs.squads.so/main/getting-started/on-and-off-ramp/sphere)
[NextBridge Off-Ramp](https://docs.squads.so/main/getting-started/on-and-off-ramp/bridge-off-ramp)

Last updated 11 months ago

---

# TipLink | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FVZxVYJmu1krrhVgxDIbp%252Ftiplink.png%3Falt%3Dmedia%26token%3D4601c975-7fb0-433b-9f5d-64c9b03cef36&width=1248&dpr=4&quality=100&sign=d9deb89d&sv=2)

[](https://docs.squads.so/main/navigating-your-squad/integrated-apps/tiplink#what-is-tiplink)

What is TipLink?


-------------------------------------------------------------------------------------------------------------------

TipLink enables users to send digital assets to anyone via a link or QR code. To receive these digital assets, recipients simply have to click on the link or scan the QR code — regardless of whether they have a crypto wallet or not. By abstracting the complexity of blockchains, TipLink aims to drive broader adoption of crypto, bridging the gap between tech-savvy users and the general public.

[](https://docs.squads.so/main/navigating-your-squad/integrated-apps/tiplink#how-do-squads-users-benefit-from-this-integration)

How do Squads users benefit from this integration?


---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

By integrating TipLink, you can now create and use a Squads account with your email. Also, TipLink enables you to send tokens — such as SOL, USDC, and more — simply by entering the email address of the recipient. This feature is particularly useful to enterprises using Squads for paying contractors and service providers who do not have a crypto wallet.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FPeyLTsVTpqURe6wOvSje%252FkIu84b5Sojf6faOJX1UmNmWBs.avif%3Falt%3Dmedia%26token%3Dbbe741b7-a249-4214-b463-5d266afb4418&width=768&dpr=4&quality=100&sign=12c8a295&sv=2)

By avoiding wallet addresses — which come as long, complex strings of alphanumeric characters, and are prone to errors when copied or typed manually — the overall transaction experience can also be made more intuitive and user-friendly.

Apart from that, wallet addresses can also expose users to phishing attacks, where malicious actors trick them into sending funds to fraudulent addresses that look similar to legitimate ones. With our TipLink integration, however, we're able to prevent this right from the outset.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FXdP4mF5EuwIafcuUpTKo%252FzxlNkEHOuIMfTRMnDXn6MqXrxcM.avif%3Falt%3Dmedia%26token%3De9af8289-0690-4e36-9559-d061af6d6e1a&width=768&dpr=4&quality=100&sign=838d9521&sv=2)

TipLinks that are sent through Squads can only be accessed through the email account of the intended recipient. And if a TipLink has been sent to the wrong email address or the TipLink funds are not being claimed, Squads users can recover the associated tokens back to their vault.

[](https://docs.squads.so/main/navigating-your-squad/integrated-apps/tiplink#how-to-send-cryptos-to-an-email-address)

How to send cryptos to an email address?


-------------------------------------------------------------------------------------------------------------------------------------------------------------------

Sending crypto to an email address via TipLink is simple. Simply enter the email address of the recipient instead of the wallet address.

NFTs and Token Extensions (Token-2022) are not supported yet.

[PreviousIntegrated apps](https://docs.squads.so/main/navigating-your-squad/integrated-apps)
[NextRange](https://docs.squads.so/main/navigating-your-squad/integrated-apps/range)

Last updated 1 year ago

---

# Third-Party Payouts | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FlE6ClCpbIUVlikgJuv0g%252Fbridge%2520xyz.png%3Falt%3Dmedia%26token%3D8c6f75b3-0911-44f6-8c66-68e0f7a740b3&width=1248&dpr=4&quality=100&sign=a3f683a1&sv=2)

Third-party payouts enables [Squads](https://squads.so/)
 users to make USDC payouts to bank accounts of both businesses and individuals, with funds arriving in either USD or EUR.

1.  [How It Works](https://docs.squads.so/main/getting-started/on-and-off-ramp/third-party-payouts#how-to-create-a-third-party-payment)
    
2.  [Options And Fees](https://docs.squads.so/main/getting-started/on-and-off-ramp/third-party-payouts#options-and-fees)
    
3.  [User Eligibility](https://docs.squads.so/main/getting-started/on-and-off-ramp/third-party-payouts#user-eligibility)
    

[](https://docs.squads.so/main/getting-started/on-and-off-ramp/third-party-payouts#how-it-works)

How It Works


------------------------------------------------------------------------------------------------------------------

**KYB Verification and Contact bank details**

*   Log in to your Squad and navigate to the “Contacts” section in the left-hand menu.
    
*   Choose an existing contact or create a new one
    
*   The "Bank Account Details" section of the "Contacts" page will prompt you to verify with Bridge if needed.
    
*   Once verified (takes up to 24 hours), add the contact's bank details
    

**Making a payout**

*   Go to your Squad dashboard and click “Send”. In the “External” section, choose “To bank account”. Select your payment account and the payout recipient from your contacts— then click “Next”. Alternatively, you can click the “Send” button directly from the contact overview to initiate a faster third-party payout workflow.
    
*   Next, enter the USDC amount you'd like to pay out and choose a transaction method—click “Next” to proceed.
    
*   Review the payout details and initiate the transaction. The USDC payout will be converted to USD or EUR based on the recipient’s bank details.
    

[](https://docs.squads.so/main/getting-started/on-and-off-ramp/third-party-payouts#options-and-fees)

Options And Fees


--------------------------------------------------------------------------------------------------------------------------

Multiple transaction methods are available for third-party payouts.

**Wire Transfer**

*   Fee: $20 + 0.5%
    
*   Settlement: Within 1 business day (fastest option)
    

**ACH Same Day**

*   Fee: $1 + 0.5%
    
*   Settlement: Within 1 business day
    

**Standard ACH**

*   Fee: $0.50 + 0.5%
    
*   Settlement: 2-3 business days
    

**SEPA Transfer**

*   Fee: $1.00 + 0.5%
    
*   Settlement: 1-5 business days
    

[](https://docs.squads.so/main/getting-started/on-and-off-ramp/third-party-payouts#user-eligibility)

User Eligibility


--------------------------------------------------------------------------------------------------------------------------

**Availability** Third-party payouts are available to businesses in Canada, Europe, Asia, and other regions outside OFAC sanctions. While U.S. businesses are not yet eligible, non-U.S. businesses can use the feature to pay their U.S. counterparts.

**Restrictions** Third party payouts are not available for US based customers or the 39 countries in the list below.

*   Afghanistan
    
*   Albania
    
*   Algeria
    
*   Bangladesh
    
*   Belarus
    
*   Central African Republic
    
*   China
    
*   Cuba
    
*   Democratic Republic of the Congo
    
*   Eritrea
    
*   Ethiopia
    
*   Gaza Strip
    
*   Iran
    
*   Iraq
    
*   Kenya
    
*   Kosovo
    
*   Lebanon
    
*   Libya
    
*   Mali
    
*   Morocco
    
*   Myanmar
    
*   Nepal
    
*   Nicaragua
    
*   Niger
    
*   North Korea
    
*   North Macedonia
    
*   Pakistan
    
*   Qatar
    
*   Russian Federation
    
*   Slovenia
    
*   Somalia
    
*   South Sudan
    
*   Sudan
    
*   Syria
    
*   Ukraine
    
*   Venezuela
    
*   West Bank
    
*   Yemen
    
*   Zimbabwe
    

[PreviousBridge Off-Ramp](https://docs.squads.so/main/getting-started/on-and-off-ramp/bridge-off-ramp)
[NextTreasury Management Overview](https://docs.squads.so/main/getting-started/treasury-management-overview)

Last updated 9 months ago

---

# FAQs | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FxP5nnFvlz8LHXryeTO2P%252Ffaq.png%3Falt%3Dmedia%26token%3D377a6372-64d2-4637-b5ed-02d4b19a6c60&width=1248&dpr=4&quality=100&sign=69c25d35&sv=2)

**What is a Squad?**[](https://docs.squads.so/main/additional-resources/faqs#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.**[](https://docs.squads.so/main/additional-resources/faqs#im-getting-an-error-and-cant-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?**[](https://docs.squads.so/main/additional-resources/faqs#ive-created-a-squad-but-cant-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?**[](https://docs.squads.so/main/additional-resources/faqs#which-blockchain-is-squads-protocol-built-on)

Squads Protocol is built on the Solana blockchain.

**Is Squads Protocol permissionless?**[](https://docs.squads.so/main/additional-resources/faqs#is-squads-protocol-permissionless)

Yes, Squads Protocol is permissionless to interact with.

**How can I contribute to the protocol?**[](https://docs.squads.so/main/additional-resources/faqs#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?**[](https://docs.squads.so/main/additional-resources/faqs#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](https://docs.squads.so/main/navigating-your-squad/squadsx)
.

**Can I create a Squad and gate access to it with NFTs?**[](https://docs.squads.so/main/additional-resources/faqs#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?**[](https://docs.squads.so/main/additional-resources/faqs#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](https://docs.squads.so/main/additional-resources/what-if-the-squads-app-goes-down)
.

**Can I add a custom RPC to use the Squads app?**[](https://docs.squads.so/main/additional-resources/faqs#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.

[PreviousIntegral](https://docs.squads.so/main/navigating-your-squad/reporting-and-accounting/integral)
[NextAdvanced Security Best Practices](https://docs.squads.so/main/additional-resources/advanced-security-best-practices)

Last updated 12 months ago

---

# Manage assets | Squads Docs

### 

[](https://docs.squads.so/main/navigating-your-squad/treasury/manage-assets#how-to-deposit-assets-into-your-squads-account)

How to deposit assets into your Squads account

*   Navigate to the "Treasury" tab and click "Deposit"
    
*   Select the target account and asset type (SPL token or NFT)
    
*   Click "Deposit" to complete the process
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FBVxN1irRgsPYH7NEnRjW%252FDeposit%2520update.png%3Falt%3Dmedia%26token%3D8b7b5ede-279a-487f-bdcb-1fa61ac1bea1&width=768&dpr=4&quality=100&sign=dac46b77&sv=2)

Deposit pop-up

### 

[](https://docs.squads.so/main/navigating-your-squad/treasury/manage-assets#how-to-withdraw-assets-from-your-squads-account)

How to withdraw assets from your Squads account

Users can withdraw their assets from their Squads multisig to:

*   Another wallet or a centralized exchange (CEX)
    
*   Multiple wallets/Squads using Batch send
    
*   An email, via [TipLink](https://docs.squads.so/main/navigating-your-squad/integrated-apps/tiplink)
    
*   Their US bank account, via Sphere or Coinflow
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252F4uOAjZb1KN55EDWIGWUJ%252FScreenshot%25202024-10-01%2520at%252012.07.20%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D3f1a4a95-cfbb-49b9-a39a-7f02219aaaa2&width=768&dpr=4&quality=100&sign=66e241ac&sv=2)

Send pop-up

#### 

[](https://docs.squads.so/main/navigating-your-squad/treasury/manage-assets#sending-assets-to-another-wallet)

Sending assets to another wallet

Here are the steps to sending funds from your Squads multisig to another wallet:

*   Navigate to the "Treasury" tab, and click the "Send" button.
    
*   Select the option to send to another wallet in the popup window.
    
*   Enter the recipient address, token, and amount you want to send.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FgumnLtWSC5ZrLo0JTG5D%252Fsend%2520tx%25201.png%3Falt%3Dmedia%26token%3D235725a3-14d1-4b0d-83e9-d19765c81e62&width=768&dpr=4&quality=100&sign=94f329be&sv=2)

Sending assets to another wallet

*   Once added, you can review and initiate your transaction. This additional safeguard enables users to double-check and verify recipient addresses and token amounts before finalizing the transaction, reducing the risk of errors.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252F9JwpkgWtan7oILimdAzl%252FScreenshot%25202024-10-01%2520at%252012.09.01%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D5e25248a-c173-4f0c-b670-725bc5f90a2e&width=768&dpr=4&quality=100&sign=946e2863&sv=2)

Review page

*   Funds will be transferred upon the execution of the transaction.
    

Always send a first small test amount when sending assets to centralized exchanges (CEXs). Some CEXs do not recognize transfers from Squads multisigs/PDAs. Learn more [here](https://docs.squads.so/main/frequently-asked-questions/sending-assets-to-from-centralized-exchange-cexs)
.

Sending a specific token to a wallet for the first time requires 0.003 SOL in your Squads account. This fee creates the token account (ATA) in the recipient's wallet. For instance, if you’re sending USDC to a wallet that has never received USDC before, you will have to incur this amount.

#### 

[](https://docs.squads.so/main/navigating-your-squad/treasury/manage-assets#batch-send)

Batch Send

Batch Send allows users to send tokens to multiple recipients. Here are the steps to execute a batch send transaction:

*   In the popup window, select the “Batch send” option.
    
*   Enter the token you want to send. Users can only select one token per batch transaction to simplify the workflow.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FkgcpyG6PxtRRfe7Yz1dd%252FScreenshot%25202024-10-01%2520at%252012.09.52%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D40631321-2b39-4457-919e-61d8120878e9&width=768&dpr=4&quality=100&sign=fdd90a7c&sv=2)

Batch send

Batch Send transactions can be executed in two ways:

*   **Batch:** Users can manually enter recipient wallet addresses and the amount they want to send to each recipient.
    
*   **Split:** This allows for the distribution of the selected amount in equal portions to multiple specified addresses through a single transaction.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FeJvUdW3SDiWKZVzuTauQ%252Fsend%2520tx%25202.png%3Falt%3Dmedia%26token%3D7d82d44d-aaa8-4934-87c7-320066924b65&width=768&dpr=4&quality=100&sign=1ea22b3b&sv=2)

Two options for Batch Send

*   Once the details have been entered, you can review the recipients and the amount each one is receiving. Initiate your transaction upon confirmation and assets will be transferred.
    

#### 

[](https://docs.squads.so/main/navigating-your-squad/treasury/manage-assets#email-send)

Email Send

You can also send assets by entering the recipient’s email address. This is powered by [TipLink](https://tiplink.io/)
. Learn more about our integration and how you can use email to send your assets [here](https://docs.squads.so/main/navigating-your-squad/in-app-integrations/tiplink)
.

If you send assets to the wrong email address or the TipLink funds are not claimed, you can recover the associated tokens back to your vault.

#### 

[](https://docs.squads.so/main/navigating-your-squad/treasury/manage-assets#off-ramp)

Off-ramp

Users can off-ramp their onchain assets from their Squad directly to their bank accounts. This can be done using Sphere and Coinflow. Learn more about off-ramping assets [here](https://docs.squads.so/main/getting-started/on-and-off-ramp)
.

### 

[](https://docs.squads.so/main/navigating-your-squad/treasury/manage-assets#how-to-receive-assets-into-your-squads-account)

How to receive assets into your Squads account

To receive funds from external parties like contractors, investors, and other Solana wallets :

*   Click the copy-paste or QR code icon under the Squads profile section
    
*   Share the Squads account address or QR code with the sender
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FL7M85cd3s2GdajhRgL6e%252FRecieve.png%3Falt%3Dmedia%26token%3D47891ea1-352a-4d83-9af9-efc84068d5e9&width=768&dpr=4&quality=100&sign=a5336e74&sv=2)

Receive screen

### 

[](https://docs.squads.so/main/navigating-your-squad/treasury/manage-assets#how-to-burn-assets-in-your-squads)

How to burn assets in your Squads

Squad members can burn tokens present in their treasury.

1.  In the Account page in the Treasury section of your Squad, head over to the token you want to burn under the "Coins" tab.
    
2.  Click the three dots to the right of the token and click the "Burn" button.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FDndFAkthTeZbdpOxDWjx%252Fimage.png%3Falt%3Dmedia%26token%3D75b2c757-8895-4c93-8538-ef19ee303e04&width=768&dpr=4&quality=100&sign=d68b449e&sv=2)

Tokens in the Coins tab

1.  Select the amount of tokens you want to burn, add a note (optionally), and initiate a transaction.
    
2.  The tokens will be burned once the transaction is executed.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252F19sl2AKAgijJMxcAx9DW%252FScreenshot%25202024-11-19%2520at%25201.57.09%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3Da88d0346-dd36-4bf5-9dab-e1e05f314066&width=768&dpr=4&quality=100&sign=e0f6b348&sv=2)

Burn Tokens

### 

[](https://docs.squads.so/main/navigating-your-squad/treasury/manage-assets#nfts)

**NFTs**

Members can deposit up to 20 NFTs and batch-send hundreds of NFTs in a single transaction.

Users can also toggle between list and icon view for NFT gallery display.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252Fx1a11RF6S2eS1XB75Cm8%252Fimage.png%3Falt%3Dmedia%26token%3D27d8c392-8643-4922-adb3-b33e71cb2534&width=768&dpr=4&quality=100&sign=486b2e20&sv=2)

[PreviousSub-accounts](https://docs.squads.so/main/navigating-your-squad/treasury/sub-accounts)
[NextContacts](https://docs.squads.so/main/navigating-your-squad/treasury/contacts)

Last updated 12 months ago

---

# Safe | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FLzLxT4okyeqxNulAQZz9%252Fsafe.png%3Falt%3Dmedia%26token%3Dd98dc017-f041-49d5-bdbb-0040a4eaf112&width=1248&dpr=4&quality=100&sign=7a1ed907&sv=2)

[](https://docs.squads.so/main/navigating-your-squad/integrated-apps/safe#what-is-safe)

What is Safe?


----------------------------------------------------------------------------------------------------------

[Safe](https://safe.global/)
 is an EVM-based onchain asset custody protocol. Launched in 2018, Safe has established itself as the EVM smart account standard today - securing over $100 billion in value across 8+ million smart accounts. Aligned with the vision of Squads, they are also pursuing a future where everyone has complete control and flexibility over their digital assets.

[](https://docs.squads.so/main/navigating-your-squad/integrated-apps/safe#how-do-squads-users-benefit-from-this-integration)

How do Squads users benefit from this integration?


------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Thanks to our partnership with Safe, you can now add any Safe wallet as a view-only account in Squads. Teams with assets on the EVM can now view their entire treasury across multiple chains in a single interface.

[](https://docs.squads.so/main/navigating-your-squad/integrated-apps/safe#how-to-add-your-safe-wallet-to-your-squad)

How to add your Safe wallet to your Squad?


--------------------------------------------------------------------------------------------------------------------------------------------------------------------

1.  Navigate to the "Treasury" tab, and click the "Add Safe Account" button below your Account in the Navigation bar.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FypP34L7Zx4c70KgyqBUi%252Fimage.png%3Falt%3Dmedia%26token%3Df9d90ace-9937-462f-b385-2e7ecde6de81&width=768&dpr=4&quality=100&sign=49aa301d&sv=2)

Treasury tab

1.  Fill in the required data within the pop-up window. The data includes:
    
    1.  Name of the Safe wallet (optional)
        
    2.  Safe's address
        
    
2.  Click the "Add" button.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252F9CJ64JJXrcCKmouAfGTe%252FScreenshot%25202024-07-04%2520at%25206.44.47%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3Dcc11c919-62a7-4c91-8a61-1a85ff0af86f&width=768&dpr=4&quality=100&sign=1de32c09&sv=2)

Add Safe Multisig pop-up

1.  Your Safe wallet will be added to the Treasury tab as a view-only account.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252F8zgLnAzIxKshu4PqT1hU%252Fimage.png%3Falt%3Dmedia%26token%3D4d45b8b4-7506-473c-80fd-5d2b4ed8532e&width=768&dpr=4&quality=100&sign=1554a01a&sv=2)

Safe wallet as a view-only account

[PreviousSNS](https://docs.squads.so/main/navigating-your-squad/integrated-apps/sns)
[NextSquadsX](https://docs.squads.so/main/navigating-your-squad/squadsx)

Last updated 1 year ago

---

# Settings | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FCuCP68SDA6vxL7WAtbpX%252Fsettings.png%3Falt%3Dmedia%26token%3Dab24557c-0c96-470b-894f-6944b56112f5&width=1248&dpr=4&quality=100&sign=3a2d1f68&sv=2)

Squad Settings

The "Settings" tab displays information about the Squad and allows you to:

*   View the Squad's vault address and multisig address
    
*   Edit the photo, name, and description of the Squad
    
*   Check the confirmation threshold and initiate a transaction to change it
    
*   Select the default explorer for the Squad's transactions
    
*   Add [Spending Limits](https://docs.squads.so/main/navigating-your-squad/settings/spending-limits)
    
*   Set a [Time Lock](https://docs.squads.so/main/navigating-your-squad/settings/time-locks)
    
*   Enable/Disable [Squad UI Privacy](https://docs.squads.so/main/navigating-your-squad/settings/privacy)
    
*   Export CSV of your transactions
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252Ff0S68nI9VWWWiMATpX3d%252FScreenshot%25202024-06-25%2520at%252010.45.06%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3Ded4c3638-0891-4e96-acde-9020cca1e505&width=768&dpr=4&quality=100&sign=2b0a271b&sv=2)

Settings page

### 

[](https://docs.squads.so/main/navigating-your-squad/settings#vault-and-multisig-address)

Vault and Multisig Address

When creating a Squad, a Program Derived Address (PDA) is created with specific details such as members, threshold, and more. This PDA's address is the **multisig account address**, owned by the Squad program and used exclusively for Squad detection.

**The Squad Vault** and Sub-accounts are PDAs derived from the multisig account address. Unlike the Squad's PDA, they aren't owned by the program, allowing them to function as classic wallets for sending and receiving funds.

**DO NOT** set the Multisig Account address as an authority of your programs nor send any kind of assets to it.

**ONLY** the Squad Vault address should be set as the owner of your assets/authorities. The Multisig Account address is used solely for CLI settings commands.

Sending assets or setting authority to the Multisig Account address will cause irreversible loss of funds/assets.

### 

[](https://docs.squads.so/main/navigating-your-squad/settings#threshold-parameter)

**Threshold Parameter**

The confirmation threshold is crucial for securing assets within a Squad. It represents the number of Squad members required to confirm before executing a transaction.

When configuring the confirmation threshold for a Squad:

*   Avoid setting it at 1/n signatures, as this creates a single point of failure.
    
*   Avoid setting it at maximum capacity (e.g., 2/2, 3/3) to prevent potential loss of access.
    

To adjust the confirmation threshold:

1.  Navigate to the "Settings" tab.
    
2.  Click on the threshold icon, set the new threshold, and launch a transaction.
    
3.  The threshold will change upon transaction execution.
    

Only members with "Voter" permission count towards the threshold parameter.

Changing the confirmation threshold will cancel all "Active" and "Ready" transactions in a Squad for security reasons. Complete these transactions before changing the threshold to avoid issues.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FDeoSHMckjnaE95mxEeVW%252F3%2520threshold%29.png%3Falt%3Dmedia%26token%3De5fedf16-39ab-42dc-8d53-dc74043c9346&width=768&dpr=4&quality=100&sign=9292710d&sv=2)

Change threshold pop-up

[PreviousTransaction Builder](https://docs.squads.so/main/navigating-your-squad/developers-assets/transaction-builder)
[NextSpending Limits](https://docs.squads.so/main/navigating-your-squad/settings/spending-limits)

Last updated 11 months ago

---

# Validators | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FCQW00YINkiIFgPRizVG0%252Fvalidators.png%3Falt%3Dmedia%26token%3D47035e87-07bc-4504-b381-e1c1280e0bde&width=1248&dpr=4&quality=100&sign=5e38f7ab&sv=2)

Users can manage validators directly from their Squad. The management of validators includes changing commissions, withdrawing rewards, and changing authorities.

### 

[](https://docs.squads.so/main/navigating-your-squad/developers-assets/validators#adding-validators)

**Adding validators**

Users can transfer their validator withdraw authority to a Squad.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252Fn1fENmMZ6YyEa1ecUr2O%252FValidator-9.png%3Falt%3Dmedia%26token%3D95b2d36b-7f6f-41fa-8929-3530b124f919&width=768&dpr=4&quality=100&sign=5fd96877&sv=2)

Validators tab

**To transfer validator withdraw authority to a Squad:**

1.  Go to the "Validators" tab and click the "+ Add Validator" button.
    
2.  Enter the name and validator ID, then click "Next".
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252F6YY3QxMpg1F5okq3OdnH%252FValidator%2520add%2520a%2520val%2520NEW.png%3Falt%3Dmedia%26token%3D368d3423-c94c-4821-a2a1-d51b948b9d7f&width=768&dpr=4&quality=100&sign=6cad67aa&sv=2)

Add validator pop-up

1.  Set the validator withdraw authority and click "Verify Authority". There are three ways to transfer validator authority to a Squad:
    

*   Copy the address of your Squad and transfer the authority to it
    
*   Insert the path of the actual authority keypair (Absolute path), copy the code, and run it in the CLI tool
    
*   Use SAT (Safe Authority Transfer)
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FeE05w1f2O5Pf86DfVEoP%252FValidator-3.png%3Falt%3Dmedia%26token%3D43cd8c0e-c284-4e70-aa2e-45204a0af887&width=768&dpr=4&quality=100&sign=14c707bc&sv=2)

Set withdraw authority pop-up

For users who would want to perform the authority transfer more safely, there is an option to make a Safe Authority Transfer (SAT). SAT creates a transaction in the Squad, which needs to be signed by both Squad's Vault PDA and the current authority holder.

**To perform a Safe Authority Transfer (SAT):**

1.  Add your CLI wallet to the Squad. Check the [**Settings and Members**](https://docs.squads.so/main/navigating-your-squad/settings#manage-members)
     page for more info on how to add members.
    
2.  Click on the "Create SAT" button.
    
3.  Launch a transaction inside your Squad.
    
4.  Once the transaction meets the confirmation threshold, execute it with your CLI wallet, which you added to your Squad. More on transactions [**here.**](https://docs.squads.so/main/navigating-your-squad/transactions#how-transactions-work-inside-squads)
    
5.  After the transaction is executed, the withdraw authority will be transferred to your Squad.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FeC68P5NU4jYziSmfT7Ly%252FValidator-4.png%3Falt%3Dmedia%26token%3D9f829ca1-2fff-4ed8-b7b8-d4cf50f72a2d&width=768&dpr=4&quality=100&sign=f7b8687b&sv=2)

Safe Authority Transfer (SAT) pop-up

### 

[](https://docs.squads.so/main/navigating-your-squad/developers-assets/validators#managing-validators)

**Managing validators**

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252Fj407m5eQq0qvdzQB4Zcb%252FValidator%2520pop-up%2520NEW.png%3Falt%3Dmedia%26token%3D1472c81a-4d11-45e4-be3e-cb53f75773b1&width=768&dpr=4&quality=100&sign=8aaa64d0&sv=2)

Validator pop-up

**Changing Commission:**

1.  Go to the "Validators" tab and select the validator that you want to manage.
    
2.  Click on the "Change commission" button.
    
3.  Enter the new commission percentage and launch the transaction.
    
4.  The validator's commission will be updated upon execution of the transaction.
    

**Withdrawing Rewards:**

1.  Go to the "Validators" tab and select the validator from which you want to withdraw rewards.
    
2.  Click on the "Withdraw Rewards" button.
    
3.  Click on the "Withdraw" button to launch the transaction.
    
4.  Upon execution, your rewards will appear in your Squad vault.
    

**Changing Authority:**

1.  Go to the "Validators" tab and select the validator whose authority you want to change.
    
2.  Click on the "Change Authority" button.
    
3.  Enter the new address to which you want to pass the authority.
    
4.  Click on the "Initiate a transaction" button and launch the transaction. The authority will be transferred to the newly assigned address upon execution of the transaction.
    

Users can also use the Squads CLI tool to withdraw the validator withdraw authority from their Squad.

[PreviousPrograms](https://docs.squads.so/main/navigating-your-squad/developers-assets/programs)
[NextToken Manager](https://docs.squads.so/main/navigating-your-squad/developers-assets/token-manager)

Last updated 1 year ago

---

# Advanced Security Best Practices | Squads Docs

This guide provides comprehensive security recommendations for organizations using Squads to manage digital assets. Following these best practices will help protect your treasury and program upgrades from both external and internal threats.

### 

[](https://docs.squads.so/main/additional-resources/advanced-security-best-practices#table-of-contents)

Table of Contents

*   [General Overview](https://docs.squads.so/main/additional-resources/advanced-security-best-practices#general-overview)
    
*   [Core Security Practices](https://docs.squads.so/main/additional-resources/advanced-security-best-practices#core-security-practices)
    
*   [Treasury Segmentation](https://docs.squads.so/main/additional-resources/advanced-security-best-practices#treasury-segmentation)
    
*   [Program Upgrades](https://docs.squads.so/main/additional-resources/advanced-security-best-practices#program-upgrades-double-verification-and-verifiable-builds)
    
*   [Squads Frontend Verification](https://docs.squads.so/main/additional-resources/advanced-security-best-practices#squads-frontend-verification)
    
*   [Mitigating Signer Attacks](https://docs.squads.so/main/additional-resources/advanced-security-best-practices#mitigating-signer-attacks)
    

### 

[](https://docs.squads.so/main/additional-resources/advanced-security-best-practices#general-overview)

General Overview

An important element of Squads' security is its transparent, sequential transaction process. This sequential structure comes from Squads Protocol's architecture, where each transaction follows a verifiable, onchain lifecycle:

1.  Initiate: A transaction is proposed and recorded onchain. This creates both a transaction account (containing the actual transaction data to be executed) and a proposal account (for tracking approvals). Transaction details include a unique transaction ID that all members can cross-reference to ensure they're approving the same transaction.
    
2.  Approve: Signers review and provide onchain signatures to approve the transaction. Each signature modifies the proposal account's state rather than changing the transaction account. This approach preserves the original transaction while tracking approval progress.
    
3.  Execute: Once the multisig threshold is met (minimum required approvals), the transaction is executed onchain. The system verifies the proposal account's status before processing the unchanged transaction account.
    

This sequential, fully onchain approach creates an immutable audit trail that enables users to self-verify transactions and eliminates opportunities for manipulation between approval and execution stages. Squads never sends the same transaction to multiple signers - it only updates the proposal state with each approval.

### 

[](https://docs.squads.so/main/additional-resources/advanced-security-best-practices#core-security-practices)

Core Security Practices

#### 

[](https://docs.squads.so/main/additional-resources/advanced-security-best-practices#squads-multisig-configuration)

Squads Multisig Configuration

*   Higher approval threshold: Implement a threshold of 4/6 or higher to ensure multiple signers are required for transaction approval, adding layers of security against individual compromises.
    
*   Time Locks: Enable time locks to defer execution of approved transactions for a set period. This creates a safety window to respond to potentially unauthorized transactions even after approval. Choose appropriate durations—shorter intervals (e.g. 10-15 minutes) for program upgrades that may require quick responses, longer intervals for treasury transfers where additional review time enhances security.
    
*   Key Rotation: Rotate keys that have been potentially exposed to unauthorized parties or not properly isolated from external systems.
    
*   Separate Approval and Execution: Always approve and execute transactions in separate steps. Avoid using the "Approve + Execute" feature for maximum security.
    
*   Diversify signing interfaces and devices: Employ signers using both mobile and desktop with hardware wallets to enhance security through diversity.
    

#### 

[](https://docs.squads.so/main/additional-resources/advanced-security-best-practices#transaction-verification)

Transaction Verification

*   Live communication: Maintain live communication with other signers during transaction approval, ensuring each signer's approval has been properly registered before proceeding.
    
*   Transaction simulation and inspection: Simulate transactions and check the results using Solana Explorer Inspector to ensure expected behavior before execution.
    

**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.

### 

[](https://docs.squads.so/main/additional-resources/advanced-security-best-practices#treasury-segmentation)

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.

### 

[](https://docs.squads.so/main/additional-resources/advanced-security-best-practices#program-upgrades-double-verification-and-verifiable-builds)

Program Upgrades: Double Verification and Verifiable Builds

#### 

[](https://docs.squads.so/main/additional-resources/advanced-security-best-practices#understanding-buffer-accounts)

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
    

#### 

[](https://docs.squads.so/main/additional-resources/advanced-security-best-practices#verifiable-builds)

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.

### 

[](https://docs.squads.so/main/additional-resources/advanced-security-best-practices#squads-frontend-verification)

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: [https://github.com/Squads-Protocol/public-v4-client](https://github.com/Squads-Protocol/public-v4-client)
        
    *   v3: [https://github.com/Squads-Protocol/public-v3-client](https://github.com/Squads-Protocol/public-v3-client)
        
    

**Range Integration (coming soon)**

Range will provide enhanced verification through automated notifications, human-readable transaction parsing, risk assessment, and detailed verification interfaces.

**Cold IPFS Frontend & Onchain Verification (coming soon)** Squads will deploy a minimalist “cold” frontend on IPFS that operates completely independent of Squads’ infrastructure, reducing dependency on Squads’ servers and web interface. This approach enhances security by removing exposure to potential Squads infrastructure compromises and dependencies on local environment security. This “cold” frontend is ideal for large-value accounts (e.g., Reserve Treasury and Program Upgrades). Additionally, builds will be hashed accordingly by release and have the hash published on Solana, IPFS, and other relevant channels. Users can then verify the authenticity of the client themselves, regardless of origin (IPFS, self-hosting, etc).

### 

[](https://docs.squads.so/main/additional-resources/advanced-security-best-practices#mitigating-signer-attacks)

Mitigating Signer Attacks

Protecting individual signers is fundamental to maintaining the integrity of your multisig operations. By implementing these security measures, your team can significantly strengthen your overall security:

#### 

[](https://docs.squads.so/main/additional-resources/advanced-security-best-practices#dedicated-hardware-security)

Dedicated Hardware Security

Dedicated Devices

*   Use dedicated hardware wallets exclusively for Squads transactions
    
*   Never use these devices for other applications, especially for keys with initiate permissions
    

Diversify Hardware Vendors

*   Use hardware wallets from different manufacturers (Ledger, Trezor, Keystone)
    
*   Hardware diversification prevents single-vendor vulnerabilities
    

#### 

[](https://docs.squads.so/main/additional-resources/advanced-security-best-practices#initiator-security)

Initiator Security

Transaction initiators pose the highest security risk since they define what gets recorded onchain:

*   Transaction content becomes immutable once initiated
    
*   Apply strictest security measures to devices used for initiation
    
*   Restrict initiation rights using Squads Permissions
    

Role-Based Permissions Squads Permissions offers three distinct roles:

*   Proposer - Can only create transactions
    
*   Voter - Can only vote on proposed transactions
    
*   Executor - Can only execute approved transactions
    

Limiting who can initiate transactions creates a critical security barrier at the most vulnerable point in the workflow.

#### 

[](https://docs.squads.so/main/additional-resources/advanced-security-best-practices#the-two-minute-rule)

The Two-Minute Rule

The sequential nature of Squads transactions, combined with Solana's blockhash expiration, creates a powerful security mechanism:

When multiple signers need to approve a transaction:

1.  After initiation, each signer should wait 2 minutes before the next person proceeds
    
2.  This waiting period allows the blockhash to expire
    
3.  If no suspicious transactions appears during this 2-minute window, the next signer can safely proceed
    

**Why This Works:**

*   Solana signatures are linked to specific blockhashes
    
*   These blockhashes automatically expire after 2 minutes
    
*   If your device is compromised and someone captures your signature, they only have a 2-minute window to misuse it
    
*   After 2 minutes, the captured signature becomes useless for malicious transactions
    
*   Because the transaction content is fixed onchain at initiation, signers can verify they're approving the intended transaction through multiple independent sources
    

**Durable Nonce Exception**

The two-minute rule depends on blockhash expiration, but durable nonces bypass this protection:

*   Durable nonces allow transactions to remain valid indefinitely
    
*   If the initiator has a durable nonce account, the two-minute rule is ineffective
    

To ensure a durable nonce transaction is not involved:

*   Verify the initiator has no durable nonce accounts using getProgramAccounts calls
    
*   Ensure the displayed fee-payer for transactions matches the initiators public key (if your Squads Fee Relayer is turned on, then the fee-payer should be the Fee Relayer key address of which you can find in Settings)
    

[PreviousFAQs](https://docs.squads.so/main/additional-resources/faqs)
[NextCosts of using Squads](https://docs.squads.so/main/additional-resources/costs-of-using-squads)

Last updated 8 months ago

---

# Start using SquadsX | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FjwlGfFjVpmR7JhG5ptdM%252Fsmart-contract-wallet-solana-squadsx-multisig-wallet-solana-account-abstraction-aa.png%3Falt%3Dmedia%26token%3D16ef7928-4c5d-4b83-a368-3396e31fcc13&width=1248&dpr=4&quality=100&sign=ea47530a&sv=2)

### 

[](https://docs.squads.so/main/navigating-your-squad/squadsx/start-using-squadsx#what-is-squadsx)

What is SquadsX

SquadsX is a companion tool that enables users to interact with the Solana ecosystem from the security of their multisig. By using this web extension wallet, users can connect to apps and protocols on Solana that are not directly integrated into the Squads platform.

For app developers oriented information (such as integration) on the SquadsX extension, check out the technical docs [here](https://docs.squads.so/main/squadsx-beta-development/)
.

### 

[](https://docs.squads.so/main/navigating-your-squad/squadsx/start-using-squadsx#how-to-start-using-the-extension)

How to start using the extension

1.  Subscribe to the [Squads Business Plan](https://docs.squads.so/main/getting-started/pricing)
    .
    
2.  Head to the Members page from the navigation tab on the left.
    
3.  Click the "Add SquadsX" button.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FjZPnvSE1QGPmFNKM7QpX%252FScreenshot%25202024-11-11%2520at%25207.31.32%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D2174d9b7-809c-4f34-be7c-762d5614e391&width=768&dpr=4&quality=100&sign=dd42bd48&sv=2)

Add SquadsX

1.  Click the "Generate new key" button.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FogjkSPc0JleBMWcStWIB%252FScreenshot%25202024-11-11%2520at%25207.34.54%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3Df7bbc176-c2ad-442e-b953-389bc03d6f86&width=768&dpr=4&quality=100&sign=73c20702&sv=2)

1.  Click the "Download SquadsX" button to download the SquadsX extension from the [Chrome web store](https://chromewebstore.google.com/detail/squadsx/jhmfofkpljgmilikdmkglcmekjnlekda)
    .
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FfcXQGsrD1yoRiyp2y5fB%252FScreenshot%25202024-11-11%2520at%25207.39.37%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3De19ec1b0-850c-43eb-a7da-31dc735b30f5&width=768&dpr=4&quality=100&sign=d08394e8&sv=2)

Download SquadsX

1.  Click the "Generate Code" button to generate your personal access code for the SquadsX extension. Copy this code and continue in the extension.
    
2.  Launch the extension and enter the access code you generated.
    
3.  Set a password that you will use to unlock the extension.
    
4.  Add the SquadsX public key freshly created to your Squad to initiate transactions.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FtDu5yKhxFkR0e80HB2Tv%252FScreenshot%25202024-11-11%2520at%25207.42.04%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D38d849e1-69b7-4308-9c85-0e3e97125369&width=768&dpr=4&quality=100&sign=d433e21f&sv=2)

Add your SquadsX key

Squads automatically create a key for you that will be used to create transactions inside your Squad. The SquadsX public key will by default only have the "Proposer" [permission](https://docs.squads.so/main/navigating-your-squad/members/permissions)
 — it will only be able to create transactions inside your Squad without the ability to approve nor execute them.

1.  Once added to your Squad, you will be able to see your Squad in SquadsX and connect it to apps in the Solana ecosystem. Check all the apps compatible with SquadsX [here](https://docs.squads.so/main/navigating-your-squad/squadsx/compatible-apps)
    .
    

If the [Fee Relayer](https://docs.squads.so/main/navigating-your-squad/members/fee-relayer)
 is enabled for your Squad, all the SquadsX transaction fees will be paid with the SOL in your vault, up to the spending limit set.

If the [Fee Relayer](https://docs.squads.so/main/navigating-your-squad/members/fee-relayer)
 is turned off, the SquadsX public key will have to be top up to initiate transactions.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252Fks4CTuNUSjDgkVvAKf0d%252Fimage.png%3Falt%3Dmedia%26token%3Db7afed16-1ae4-444a-aa68-0a15a59ce1af&width=768&dpr=4&quality=100&sign=f2634630&sv=2)

Squads in the SquadsX extension

### 

[](https://docs.squads.so/main/navigating-your-squad/squadsx/start-using-squadsx#how-to-use-squadsx-for-interacting-with-solana-dapps)

How to use SquadsX for interacting with Solana dApps

1.  Navigate to the dApp you wish to interact with. See the list of apps compatible with SquadsX [here](https://docs.squads.so/main/navigating-your-squad/squadsx/compatible-apps)
    .
    
2.  Click "Connect Wallet" and select SquadsX.
    
3.  After initiating an action in the app, sign the transaction in the SquadsX pop-up just as you normally would with any other wallet.
    
4.  The transaction will now be added to your Squad under the Transactions page for approval.
    
5.  Once approved and executed, the action will be reflected in the dApp.
    

[PreviousSquadsX](https://docs.squads.so/main/navigating-your-squad/squadsx)
[NextCompatible Apps](https://docs.squads.so/main/navigating-your-squad/squadsx/compatible-apps)

Last updated 1 year ago

---

# Compatible Apps | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FoU9evhsfkdYTr8QTOX2l%252Fsolana-multisig-wallet-squadsx-browser-extension-wallet-multisig-solana-best-connect-dapps.png%3Falt%3Dmedia%26token%3Dd1cb30f0-31da-4912-b93c-7603eea0fd25&width=1248&dpr=4&quality=100&sign=9a079fe&sv=2)

Here is the list of applications you can access via SquadsX to execute operations with your treasury assets:

This list indicates compatibility only and does not constitute an endorsement of any app's team, product, or security. Always perform your due diligence before engaging with third-party applications.

Asset Management

DEXs

Money Markets

NFTs

Others

Application

Use Cases

Limitations

**Magna**

Create Allocation

\-

Import Allocation

\-

Create Schedule

\-

Start & Fund Distribution

\-

**Streamflow**

Create Airdrops

\-

Create Vest

\-

Payments

\-

**Request Finance**

Create, track and reconcile invoices

**Squads**

Initiate Transactions

\-

Approve/Reject Transactions

\-

Application

Use Cases

Limitations

**Jupiter**

Swaps/Limit Orders

\-

DCA

\-

Value Average

\-

Perp Trading

\-

**Lulo**

Deposit/Withdraw

\-

**Meteora**

Deposit/Withdraw (Standard pool)

\-

**Orca**

Swap

\-

**Raydium**

Swap

\-

Liquidity Provisioning

The transaction might not go through successfully if your Fee Relayers is enabled. Please contact support if you face an error.

Liquidity Provisioning

\-

**Zeta**

Buy/Sell

\-

**Darklake**

Swap

Application

Use Cases

Limitations

**Drift**

Borrow/Lend

\-

**Exponent**

Deposit/Lend

Only available for fragSOL, kySOL, and USD.

**Kamino**

Borrow/Lend

\-

**Marginfi**

Lending

The transaction might not go through successfully if your Fee Relayers is disabled. Please contact support if you face an error.

**Save (formerly Solend)**

Deposit/Withdraw

\-

Application

Use Cases

Limitations

**Tensor**

Buy/Sell NFTs

\-

Application

Use Cases

Limitations

**Marinade**

Native Stake/Unstake

\-

Liquid Stake/Unstake

\-

**Sanctum**

Deposit Into The Infinity Pool

\-

Withdraw INF

\-

Trade LSTs

\-

**Solayer**

Deposit/Withdraw

\-

**TipLink**

Create A TipLink

\-

SquadsX is still in beta, bugs or compatibility issues may occur. If you face any issues, please reach out to us on [Discord](https://discord.com/invite/squadsprotocol)
.

[PreviousStart using SquadsX](https://docs.squads.so/main/navigating-your-squad/squadsx/start-using-squadsx)
[NextReporting and Accounting](https://docs.squads.so/main/navigating-your-squad/reporting-and-accounting)

Last updated 2 months ago

---

# Quickstart Guide | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FJCktthaTbVceMhZFGe34%252Fquickstart.png%3Falt%3Dmedia%26token%3Dbe01a78c-4923-4698-ac0f-48241f40bb0a&width=1248&dpr=4&quality=100&sign=6741752b&sv=2)

### 

[](https://docs.squads.so/main/getting-started/quickstart-guide#creating-a-squad)

Creating A Squad

Creating a Squads multisig is a straightforward process that begins with connecting your Solana wallet (such as Phantom or Backpack) to Squads.

*   Upon connecting, choose a name for your squad, select the number of approvals required for transactions, and add squad members by adding their wallet addresses.
    
*   It is recommended to avoid minimum confirmation thresholds (1/x) and maximum thresholds (e.g. 5/5). Instead, opt for an optimal approach like 2/3 or 3/5 depending on the size of your team.
    
*   Always ensure each member keeps a backup of their private keys used for the multisig and that the threshold allows for easy replacement of a lost/compromised key. Recommend members to use cold wallets to protect their private keys.
    

You can modify your Squad settings after creation, including adjusting the confirmation threshold and managing members (add/remove). Any changes you make will require approval based on the existing confirmation threshold in place.

Follow our step-by-step guide to creating your Squad [here](https://docs.squads.so/main/getting-started/create-a-squad)
.

### 

[](https://docs.squads.so/main/getting-started/quickstart-guide#setting-up-your-squad)

Setting Up Your Squad

Once you have created your multisig with a robust and secure setup, you can deposit your onchain assets to your Squad. You can carry out transfers to your Squad multisig address from these sources:

*   A Solana wallet (Phantom, Backpack, etc.);
    
*   centralized exchange ([refer to our list of supported CEXs](https://docs.squads.so/main/additional-resources/sending-assets-to-from-centralized-exchange-cexs)
    );
    
*   or on-ramp from a bank account using [Sphere](https://docs.squads.so/main/getting-started/on-and-off-ramp/sphere)
    .
    

Note: Before adding a large amount, it is recommended to first test with a small sum to ensure:

*   all members understand the process,
    
*   your multisig setup works as expected.
    

You can manage the settings of your Squad and its members using features like [Permissions](https://docs.squads.so/main/navigating-your-squad/settings#permissions)
, [Time Locks](https://docs.squads.so/main/navigating-your-squad/settings#time-locks)
, [Spending Limits](https://docs.squads.so/main/navigating-your-squad/settings#spending-limits)
, and more. Learn more about managing your Squad settings [here](https://docs.squads.so/main/navigating-your-squad/settings)
.

Learn more advanced security measures you can take that can significantly enhance your defense against potential attacks while using Squads [here](https://docs.squads.so/main/additional-resources/advanced-security-best-practices)
.

### 

[](https://docs.squads.so/main/getting-started/quickstart-guide#treasury-operations)

Treasury Operations

The Squads dashboard provides an intuitive interface to not just store but manage your assets and perform treasury operations.

#### 

[](https://docs.squads.so/main/getting-started/quickstart-guide#on-and-off-ramping-assets)

On And Off-Ramping Assets

Squads users can on-ramp assets to their multisig and off-ramp assets to their bank accounts seamlessly using:

*   [Squads Virtual US Bank Account](https://docs.squads.so/main/getting-started/on-and-off-ramp/virtual-us-bank-account)
    : Receive payments in USD, which are seamlessly converted to USDC in your Squad account.
    
*   [Sphere](https://docs.squads.so/main/getting-started/on-and-off-ramp/sphere)
    : Seamless on-ramping and off-ramping of assets cost-effectively via Wire, ACH, and SEPA transfers for USD and EUR bank accounts.
    
*   [Coinflow Off-ramp](https://docs.squads.so/main/getting-started/on-and-off-ramp/coinflow-off-ramp)
    : Top-tier US bank collaborations and instant 24/7 crypto off-ramping to individuals and businesses with bank accounts in the US.
    
*   [Bridge Off-ramp](https://docs.squads.so/main/getting-started/on-and-off-ramp/bridge-off-ramp)
    : Available to businesses with US or European bank accounts in most regions outside the OFAC sanctions list.
    

Learn more about on and off-ramping assets [here](https://docs.squads.so/main/getting-started/on-and-off-ramp)
.

#### 

[](https://docs.squads.so/main/getting-started/quickstart-guide#accessing-the-ecosystem)

Accessing The Ecosystem

There are a ton of operations teams can undertake by accessing the vast Solana ecosystem:

*   [In-app trading](https://docs.squads.so/main/navigating-your-squad/trade)
     powered by Jupiter
    
*   [Staking](https://docs.squads.so/main/navigating-your-squad/stake)
     with any Solana validator (powered by Stakewiz), various liquid staking providers (fuseSOL, Jito, Marinade, SolBlaze, marginfi), Marinade Native, and the [Squads Validator](https://docs.squads.so/main/navigating-your-squad/in-app-integrations/staking/staking-with-squads)
    

[SquadsX](https://docs.squads.so/main/navigating-your-squad/squadsx)
 is a companion tool that enables teams to connect their Squads treasury to applications within the Solana ecosystem not directly integrated into Squads while maintaining smart account security.

And if you are a team looking for advanced features and granular controls over your assets, you can purchase the [Squads Business or Enterprise](https://docs.squads.so/main/getting-started/pricing)
 plan. It equips you with additional powerful features such as permissions, payments, sub-accounts, fee relayer, and more.

### 

[](https://docs.squads.so/main/getting-started/quickstart-guide#administration)

Administration

#### 

[](https://docs.squads.so/main/getting-started/quickstart-guide#invoice-management-and-accounting)

Invoice Management And Accounting

Request Finance makes it easy for teams to manage and automate accounting workflows for their business. Using [SquadsX](https://docs.squads.so/main/navigating-your-squad/squadsx)
, teams can connect their Squads account to Request Finance to:

*   Create and manage invoices that automatically link with Squads transactions for streamlined payment approval and execution.
    
*   Monitor approval and payment status for seamless invoice management.
    

Explore additional accounting features of Request Finance [here](https://www.request.finance/)
.

Squads users can get started with a [2-month free trial](https://www.request.finance/partners/squads)
.

#### 

[](https://docs.squads.so/main/getting-started/quickstart-guide#reporting-with-squads)

Reporting With Squads

Users can use [Integral](https://integral.xyz/)
 to streamline bookkeeping, treasury management, tax compliance, and auditing processes. Once you've set up an account on Integral, you can seamlessly integrate your Squads App address by simply copying and pasting it into the platform.

This integration provides you with a comprehensive overview of all your onchain activities — giving you access to detailed insights that enable you to effortlessly meet your compliance requirements and maintain accurate records of your onchain transactions.

### 

[](https://docs.squads.so/main/getting-started/quickstart-guide#squads-on-mobile)

Squads On Mobile

The Squads app can also be used on mobile devices via in-app browsers of mobile wallets like:

*   Phantom;
    
*   Backpack;
    
*   Solfare, and more.
    

More on how to access your Squad on mobile [here](https://docs.squads.so/main/additional-resources/squads-on-mobile)
.

In the unlikely event that the Squads app would be unavailable for a long period, we have put in place multiple options to allow users to access their assets. Learn more about accessing your Squad in such a case [here](https://docs.squads.so/main/getting-started/what-if-the-squads-app-goes-down)
.

### 

[](https://docs.squads.so/main/getting-started/quickstart-guide#contact-us)

Contact Us

If you are facing any issues or have questions, join our [Discord](https://discord.com/invite/squadsprotocol)
 or reach out to [\[email protected\]](https://docs.squads.so/cdn-cgi/l/email-protection)
.

[PreviousSecurity](https://docs.squads.so/main/basics/security)
[NextCreate a Squad](https://docs.squads.so/main/getting-started/create-a-squad)

Last updated 5 months ago

---

# Liquid Staking | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FH2pECOzMbxmKsYwQPtRm%252Fliquid.png%3Falt%3Dmedia%26token%3Dd6a2edc3-17f4-48e3-bfd1-93c98a6812fa&width=1248&dpr=4&quality=100&sign=cc957a30&sv=2)

fuseSOL[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#fusesol)

[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#overview)

Overview


-------------------------------------------------------------------------------------------------

Users can [swap](https://docs.squads.so/main/navigating-your-squad/trade)
 their SOL from within the Squads app for fuseSOL, the industry's first smart wallet liquid staking token.

[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#what-is-fusesol)

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.

[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#how-to-stake-with-fusesol)

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](https://docs.squads.so/main/navigating-your-squad/trade/swaps)
    " or "[Limit Order](https://docs.squads.so/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.
    

[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#how-to-unstake-and-withdraw-sol)

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[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#jitosol)

[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#overview-1)

Overview


---------------------------------------------------------------------------------------------------

Users can deposit their SOL holdings into Jito stake pool, which lets them earn staking rewards with additional returns for MEV redistribution.

[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#what-is-jitosol)

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.

[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#what-is-mev)

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.

[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#how-to-stake-with-jito-stake-pool)

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._

1.  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.
    

[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#how-to-unstake-and-withdraw-sol-1)

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[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#marinade)

[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#overview-2)

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.

[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#what-is-msol)

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.

[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#how-to-stake-with-marinade-stake-pool)

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._

1.  Your SOL will start the activating period upon the transaction execution (more on the transactions [here](https://docs.squads.so/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.
    

[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#how-to-unstake-from-marinade-stake-pool)

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[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#solblaze)

[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#overview-3)

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.

[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#what-is-bsol)

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.

[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#how-to-stake-with-solblaze-stake-pool)

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._

1.  Your SOL will start the activating period upon the transaction execution (more on the transactions [here](https://docs.squads.so/main/navigating-your-squad/transactions)
    ) and will appear in the vault as the bSOL. Once the new epoch starts, you will start earning rewards.
    

[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#how-to-unstake-from-solblaze-stake-pool)

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[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#marginfi)

[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#overview-4)

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.

[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#what-is-lst)

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.

[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#how-to-stake-with-marginfi-stake-pool)

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._

1.  Your SOL will start the activating period upon the transaction execution (more on the transactions [here](https://docs.squads.so/main/navigating-your-squad/transactions)
    ) and will appear in the vault as the LST. Once the new epoch starts, you will start earning rewards.
    

[](https://docs.squads.so/main/navigating-your-squad/stake/liquid-staking#how-to-unstake-from-marginfi-stake-pool)

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.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FSv7k8SOGRI9Ybd7lHUnz%252FScreenshot%25202024-05-14%2520at%25205.14.48%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D1d5e024c-52e0-4a46-bcf4-d7b3f8d72271&width=768&dpr=4&quality=100&sign=14c9795f&sv=2)

Liquid Staking Tab

[PreviousDirect Staking](https://docs.squads.so/main/navigating-your-squad/stake/direct-staking)
[NextMarinade Native](https://docs.squads.so/main/navigating-your-squad/stake/marinade-native)

Last updated 1 year ago

---

# Token Manager | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FwocsXCrMRsLfJGvVLC8q%252Ftoken.png%3Falt%3Dmedia%26token%3Da9fa89ec-1ecb-463c-a3f1-1c9afe66278a&width=1248&dpr=4&quality=100&sign=36b9ce8f&sv=2)

Users can mint, burn and manage authorities of their tokens inside their Squad using the “Token manager”.

The Token Manager is only accessible to users with a Squads Business or Enterprise plan. Learn more about our pricing and plans [here](https://docs.squads.so/main/getting-started/pricing)
.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FO8uQxT1H1XGEKcZZ3leV%252FScreenshot%25202024-11-11%2520at%252011.49.49%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3Db9a3638b-eb5f-4756-8f6c-1d303cfd4f8d&width=768&dpr=4&quality=100&sign=6d8c3a49&sv=2)

Token Manager

[](https://docs.squads.so/main/navigating-your-squad/developers-assets/token-manager#creating-a-token-from-squads)

Creating a token from Squads


----------------------------------------------------------------------------------------------------------------------------------------------------

1.  Navigate to the "Token Manager" page under the "Developers" section in the navigation tab. Click the "+ Add Token" button. Select the "Create Token" option inside the pop-up.
    
2.  Select the SPL Token Standard or the New Token Extensions Program option.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FZgSzsVidBoStlNZf2gkY%252FScreenshot%25202024-11-11%2520at%252011.51.25%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3D73c96bf3-1b69-47bd-8a9d-9ce1a879359e&width=768&dpr=4&quality=100&sign=7f75f776&sv=2)

Token creation popup

1.  Fill in the required data within the pop-up window. The data includes:
    

*   Token name and picture
    
*   Token symbol
    
*   Token description (optional)
    
*   Token decimals
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FNckYuOytYqMD8ce9A4Jh%252FScreenshot%25202024-11-11%2520at%252011.52.24%25E2%2580%25AFPM.png%3Falt%3Dmedia%26token%3Dca544b27-78ef-4f06-aa07-4c80f41d9ac8&width=768&dpr=4&quality=100&sign=6f23788d&sv=2)

Create Token popup

1.  Click "Create" to generate a transaction on the Transactions page to be approved by the multisig threshold.
    

To create a new token, you will need a minimum of 0.003 SOL in your Squad vault to cover the cost of creating [ATA](https://spl.solana.com/associated-token-account)
 for this token.

1.  Your token will be created and appear inside the "Token Manager" tab upon transaction execution (more on transactions [here](https://docs.squads.so/main/navigating-your-squad/transactions)
    ).
    

[](https://docs.squads.so/main/navigating-your-squad/developers-assets/token-manager#minting-tokens-from-squads)

Minting tokens from Squads


------------------------------------------------------------------------------------------------------------------------------------------------

1.  In the Token Manager, click the "Actions" dropdown and click the "Mint" button under it.
    
2.  Specify the amount of tokens you want to mint and launch the transaction.
    
3.  After the transaction has been executed, your token will appear in your Squad vault.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FrIllUf10j9y3YvyZVg39%252FScreenshot%25202024-11-12%2520at%252012.00.00%25E2%2580%25AFAM.png%3Falt%3Dmedia%26token%3Defce08ee-2197-44e7-938b-d0aefdd1694d&width=768&dpr=4&quality=100&sign=22ed5391&sv=2)

Mint Token popup

[](https://docs.squads.so/main/navigating-your-squad/developers-assets/token-manager#updating-your-tokens-metadata)

Updating your token's metadata


-------------------------------------------------------------------------------------------------------------------------------------------------------

1.  In the Token Manager, click the "Actions" dropdown and click the "Update Metadata" button under it.
    
2.  Update the specific fields within the pop-up window. All fields that are not updated will remain unchanged. The updatable data fields include:
    
    1.  Token name and picture
        
    2.  Token symbol
        
    3.  Token description (optional)
        
    4.  Update authority (optional)
        
    
3.  Click "Update" to generate a transaction in the Transactions page to be approved by the multisig threshold.
    

Creating and editing tokens with a Ledger is not possible because Solana message signing is not yet supported by Ledger

[](https://docs.squads.so/main/navigating-your-squad/developers-assets/token-manager#transferring-the-token-authority-to-squads)

Transferring the token authority to Squads


--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Users can transfer the token authority to the Squad if they already have the existing token. They can also transfer the token authority which belongs to the Squad to the external wallet at any time.

**To transfer the authority of an existing token to your Squad:**

1.  Navigate to the "Token Manager" page under the "Developers" section in the navigation tab. Click the "+ Add Token" button. Select the "Transfer token authority to your Squad" option.
    
2.  Insert the current token authority address, copy and paste the code into your CLI tool. The CLI code should be run by the current authority. Then click “Change authority”.
    

**To transfer the mint authority from your Squad:**

1.  In the Token Manager, click the "Transfer" dropdown and click the "Mint Authority" button under it.
    
2.  Insert the new authority address and click "Initiate" to launch a transaction. The mint authority will be transferred upon transaction execution.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FrjU8jll3ORLtG9D5Bf1Y%252FScreenshot%25202024-11-12%2520at%252012.15.14%25E2%2580%25AFAM.png%3Falt%3Dmedia%26token%3D78a5f8fb-bec1-4ea1-a089-26c0f4409b1a&width=768&dpr=4&quality=100&sign=9b88dd0c&sv=2)

Change Mint Authority

[](https://docs.squads.so/main/navigating-your-squad/developers-assets/token-manager#freezing-account-from-your-squad)

Freezing account from your Squad


------------------------------------------------------------------------------------------------------------------------------------------------------------

Users can freeze accounts using Squads Token Manager. Freezing an account allows you to halt all transfers of a token on a specific address.

**Please note** that to do this the "Freeze authority" of your token needs to be set to your Squad.

**How to freeze account:**

1.  Create or delegate a token and set its freeze authority to your Squad.
    
2.  In the Token Manager, click the "Actions" dropdown and click the "Freeze Account" button under it.
    
3.  Enter the account address and initiate a transaction within your Squad.
    
4.  The token account will remain frozen until you unfreeze it. To unfreeze the account, select "Unfreeze account" from the "Actions" button.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FtOaSCbBgoS9odXOgHleB%252FScreenshot%25202024-11-12%2520at%252012.21.29%25E2%2580%25AFAM.png%3Falt%3Dmedia%26token%3Dc1fb1116-e23c-4d49-8d2a-0757232d3a4d&width=768&dpr=4&quality=100&sign=22548ac2&sv=2)

Freeze Account

[](https://docs.squads.so/main/navigating-your-squad/developers-assets/token-manager#transferring-the-freeze-authority-of-a-token)

Transferring the freeze authority of a token


------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

User can transfer freeze authority of a token to a different address using Squads Token Manager.

**How to transfer freeze authority of a token:**

1.  In the Token Manager, click the "Transfer" dropdown and click the "Freeze Authority" button under it.
    
2.  Insert the address to which the freeze authority will be transferred and initiate the transaction.
    
3.  The freeze authority will be transferred to the new address once the transaction is executed.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252F3ExriIXwZ7NCRnCz0BWV%252FScreenshot%25202024-11-12%2520at%252012.22.22%25E2%2580%25AFAM.png%3Falt%3Dmedia%26token%3Db257fd1b-cab7-4653-913d-070b8cf8e582&width=768&dpr=4&quality=100&sign=5203d44&sv=2)

Transfer Freeze Authority

[](https://docs.squads.so/main/navigating-your-squad/developers-assets/token-manager#burning-the-freeze-authority-of-a-token)

Burning the freeze authority of a token


--------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Users can use the Squads Token Manager to burn the freeze authority of a token.

Please note that to do this the "Freeze authority" of your token needs to be set to your Squad.

1.  In the Token Manager, click the "Burn" dropdown and click the "Freeze Authority" button under it.
    
2.  Add a note (optionally) and initiate a transaction.
    
3.  The freeze authority will be burned once the transaction is executed, making your token immutable.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FcqEotdiu4eBTqpY1Dmjz%252FScreenshot%25202024-11-12%2520at%252012.23.03%25E2%2580%25AFAM.png%3Falt%3Dmedia%26token%3D59afeee6-f73c-4e01-b0ba-9f3a02fc4e67&width=768&dpr=4&quality=100&sign=42be2739&sv=2)

Burn Freeze Authority

[](https://docs.squads.so/main/navigating-your-squad/developers-assets/token-manager#burning-tokens-from-squads)

Burning Tokens from Squads


------------------------------------------------------------------------------------------------------------------------------------------------

Members can burn tokens in the Squad in the Treasury section.

Learn how to burn tokens in your treasury in our guide [here](https://docs.squads.so/main/navigating-your-squad/treasury/manage-assets#burning-tokens)
.

[PreviousValidators](https://docs.squads.so/main/navigating-your-squad/developers-assets/validators)
[NextTransaction Builder](https://docs.squads.so/main/navigating-your-squad/developers-assets/transaction-builder)

Last updated 12 months ago

---

# Programs | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FRMjgpc4xRRe7G3Kq4LR7%252Fprograms.png%3Falt%3Dmedia%26token%3Dac741cde-69fd-4c45-94bc-fca46e6d8a18&width=1248&dpr=4&quality=100&sign=835ff890&sv=2)

Squads offers a seamless experience for managing programs. Users can collectively manage program upgrades with their team via multisig. This eliminates single points of failure and reduces the risk of unauthorized changes to the program(s).

**With Squads, users can:**

*   Add programs to their Squad
    
*   Upgrade programs
    
*   Change the authority of programs
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FZajoY1WRVaygFX6yZ2iQ%252FEmpty%2520prog.png%3Falt%3Dmedia%26token%3D9901b37f-79ea-4233-9548-5b077ce483a6&width=768&dpr=4&quality=100&sign=9cf1a698&sv=2)

Programs tab

### 

[](https://docs.squads.so/main/navigating-your-squad/developers-assets/programs#create-and-add-programs)

Create and add programs

Users can delegate programs to manage and upgrade them directly from their Squad.

#### 

[](https://docs.squads.so/main/navigating-your-squad/developers-assets/programs#create-programs)

Create programs

1.  Create and deploy a program using your CLI.
    

#### 

[](https://docs.squads.so/main/navigating-your-squad/developers-assets/programs#add-programs)

Add programs

1.  Navigate to the "Programs" tab within your Squad's vault. Then click on "Add Program".
    
2.  Enter the name and address of the program. Click "Next" and verify the transaction in the wallet pop-up.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FiUH5x14Uzfp1zrw53Jj5%252FAdd%2520prog%2520step%25201.png%3Falt%3Dmedia%26token%3Ddadd2121-1e8d-433a-8656-374367fc0d65&width=768&dpr=4&quality=100&sign=2dedefff&sv=2)

Add program pop-up

1.  Set the program’s upgrade authority to the address provided using one of the following options:
    

*   Copy the Squad address and transfer the authority from the current authority holder
    
*   Copy the code and run in your CLI tool that is an authority holder
    
*   Use SAT (Safe Authority Transfer) to transfer the upgrade authority
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252F6bq6jfA9mKNCbvsZiPKN%252FStep%25202%2520add%2520prog.png%3Falt%3Dmedia%26token%3Dc9306d0a-fb0a-402b-9c91-6fdcd120c28d&width=768&dpr=4&quality=100&sign=20ea5f0&sv=2)

Transfer program upgrade authority

For users who would want to perform the authority transfer in a safer way there is an option to make a Safe Authority Transfer (SAT). SAT creates a transaction in the Squad, which needs to be signed by both Squad's Vault PDA and the current authority holder.

**To perform a Safe Authority Transfer (SAT):**

1.  Add your CLI tool to the Squad. Check the [**Settings and Members page**](https://docs.squads.so/main/navigating-your-squad/settings#manage-members)
     for more information on adding members.
    
2.  Click on the "Create SAT" button.
    
3.  Run a transaction inside your Squad.
    
4.  Once the transaction meets the confirmation threshold, execute it with your CLI tool that you added to your Squad.
    
5.  Once the transaction is executed, your program authority will be transferred.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FIeMO1k5JvIrbIyUGpXp1%252FSAT.png%3Falt%3Dmedia%26token%3Ddb5a9a31-962f-45b2-93b0-583766112982&width=768&dpr=4&quality=100&sign=1b51e1d2&sv=2)

Safe Authority Transfer

**NOTE:** If the current authority is managed by a DAO or wallet you may need to set the authority by other means using the provided upgrade authority.

### 

[](https://docs.squads.so/main/navigating-your-squad/developers-assets/programs#upgrade-a-program)

Upgrade a program

Once a program has been added to a Squad it can be upgraded straight from it with an easy-to-use interface.

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FjaGnhvfvTCSyvOwhUgym%252FUppgd.png%3Falt%3Dmedia%26token%3Dc0337d1b-a126-4580-99f0-7bf919f0bc7b&width=768&dpr=4&quality=100&sign=99cda06c&sv=2)

Program upgrades

**To upgrade a program:**

1.  Deploy your upgrade to the buffer using the command below. (For Rust)
    

Copy

    solana program write-buffer <PROGRAM_FILEPATH>

For more information about writing intermediary buffer accounts refer to the link: [https://docs.solana.com/cli/deploy-a-program#using-an-intermediary-buffer-account](https://docs.solana.com/cli/deploy-a-program#using-an-intermediary-buffer-account)

1.  Click on the program from the list and then click on the "Add upgrade" button.
    
2.  Insert the details of the upgrade: name, buffer, spill address, commit link and address for buffer refund, then click "Next" and approve the transaction in the wallet pop-up.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FGVHYr9jJLVPoE33I9wjp%252FAdd%2520upgrade%2520pop%2520up.png%3Falt%3Dmedia%26token%3Dc12409d0-2788-424a-8ba3-9240586cdfea&width=768&dpr=4&quality=100&sign=41e77863&sv=2)

Add upgrade pop-up

1.  Set the authority of the buffer to the provided address by copying a code in your CLI. Then click “Verify authority”.
    

![](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252F70ASlQvC63FhLeQeX42u%252Fadd%2520upgrade%2520pop%25202.png%3Falt%3Dmedia%26token%3D08a5f06f-112e-4c4f-81f7-42daafef6250&width=768&dpr=4&quality=100&sign=22f072ca&sv=2)

Set upgrade buffer authority pop-up

1.  Click the "Upgrade" button. A transaction will be created, after it meets the confirmation threshold and gets executed, a program upgrade will be deployed.
    

### 

[](https://docs.squads.so/main/navigating-your-squad/developers-assets/programs#withdraw-program-upgrade-authority)

Withdraw program upgrade authority

A program authority delegated to a Squad can be changed to any other address if needed at any point.

**To do this:**

1.  Click on the program from the programs list.
    
2.  Click on the "Change authority" button.
    
3.  Insert a new program authority address and initiate a transaction.
    
4.  Program authority will be changed upon transaction execution.
    

### 

[](https://docs.squads.so/main/navigating-your-squad/developers-assets/programs#squads-github-action-for-program-upgrades)

Squads GitHub Action for Program Upgrades

With the Squads GitHub action, teams can automate program deployments directly from their Github CI/CD pipeline to a program upgrade proposal in their Squads multisig. It simplifies the process of building and deploying a program buffer account, as well as initializing an upgrade proposal.

After a program upgrade has been initialized, the members of the multisig can view the details about the upgrade in the Squads app. They can then verify that the on-chain buffer matches the program source code using [Ellipsis Labs's verifiable build](https://github.com/Ellipsis-Labs/solana-verifiable-build)
.

To set up the Squads GitHub action for your program upgrades, please refer to this guide: [github.com/Squads-Protocol/squads-v4-program-upgrade](https://github.com/Squads-Protocol/squads-v4-program-upgrade)
.

[PreviousDevelopers assets](https://docs.squads.so/main/navigating-your-squad/developers-assets)
[NextValidators](https://docs.squads.so/main/navigating-your-squad/developers-assets/validators)

Last updated 1 year ago

---

# Treasury Management Overview | Squads Docs

![Page cover](https://docs.squads.so/main/~gitbook/image?url=https%3A%2F%2F254049203-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FdUrslJzNhqr2JDZzXUUz%252Fuploads%252FiIPc9Ha9rPZWNowEVWqg%252Fmanaging%2520treasury.png%3Falt%3Dmedia%26token%3Dc48d7647-e185-408f-b5de-fa604b37703a&width=1248&dpr=4&quality=100&sign=7e89dfb2&sv=2)

Squads is an enterprise platform that provides a fully-integrated suite of tools to collectively manage digital assets, automate workflows and execute onchain transactions. With Squads, organizations streamline their onchain operations while maintaining institutional-grade security and self-custody.

Explore how Squads can help manage your assets and optimize your onchain treasury management.

#### 

[](https://docs.squads.so/main/getting-started/treasury-management-overview#table-of-contents)

**Table of Contents:**

*   [Understanding the Basics](https://docs.squads.so/main/getting-started/treasury-management-overview#understanding-the-basics)
    
*   [Using Squads for Your Treasury](https://docs.squads.so/main/getting-started/treasury-management-overview#using-squads-for-your-treasury)
    
*   [Treasury Operations using Squads](https://docs.squads.so/main/getting-started/treasury-management-overview#treasury-operations-using-squadsx)
    
*   [Security](https://docs.squads.so/main/getting-started/treasury-management-overview#security)
    
*   [Additional Resources](https://docs.squads.so/main/getting-started/treasury-management-overview#additional-resources)
    

[](https://docs.squads.so/main/getting-started/treasury-management-overview#understanding-the-basics)

Understanding the Basics


-----------------------------------------------------------------------------------------------------------------------------------

Squads offers a comprehensive solution for managing onchain treasuries powered by Solana’s performance, speed, and low transaction costs. Squads has many advantages over traditional offchain or centralized solutions:

*   **Seamless user experience:** Squads offers a platform tailored to enterprise needs, integrating a wide range of operations into a single, intuitive interface.
    
*   **Security:** Squads is built on top of [Squads Protocol](https://squads.so/protocol)
    , Solana's smart account standard securing $10+ billion in value and trusted by Solana’s leading teams, applications, and institutions. Squads Protocol provides the infrastructure for secure self-custody and programmatic onchain asset management.
    
*   **Transparency:** Onchain transactions provide key stakeholders with enhanced visibility and tracking of a business's treasury activity. This transparency is achieved through an immutable history of multi-signature approvals for asset management, ensuring relevant data is accessible and presented in a clear, human-readable format.
    

Squads powers onchain operations for over 250 teams in the ecosystem, including Jupiter, Jito, Pyth, Kamino, Backpack, Helius, Drift, and Tensor. Every Squad is a programmable multisig wallet built on Squads Protocol’s smart account technology, which enables collective management of onchain funds, streamlining asset management and eliminating single points of failure.

### 

[](https://docs.squads.so/main/getting-started/treasury-management-overview#using-squads-for-your-treasury)

Using Squads for Your Treasury

Squads provides an intuitive interface to easily manage your assets and perform treasury operations. These assets can be:

*   Funds raised from investors/the public;
    
*   Fees generated by the protocol/project;
    
*   Grants received;
    
*   Liquidity mining rewards as a marketing expense;
    
*   Investor funds and token vesting;
    
*   And any onchain liquid assets, such as NFTs, held by the company.
    

#### 

[](https://docs.squads.so/main/getting-started/treasury-management-overview#executing-transactions)

Executing transactions

Teams can seamlessly execute transactions like expenses, token swaps, liquidity provision, grants and more using the Squads dashboard. This includes on and off-ramping assets to fiat using [Sphere](https://docs.squads.so/main/navigating-your-squad/in-app-integrations/sphere)
 and [Coinflow](https://docs.squads.so/main/navigating-your-squad/in-app-integrations/coinflow-off-ramp)
.

These operations are streamlined with:

*   [Batch Transfers](https://docs.squads.so/main/navigating-your-squad/transactions#batch-actions)
    : Approve, reject, or cancel multiple transactions with a single click using Batch Actions.
    
*   [Spending limits](https://docs.squads.so/main/getting-started/settings-and-members#spending-limits)
    : Allow Squad members to move predetermined amounts from the treasury without requiring full Squad approval.
    
*   [Rent Reclaim](https://docs.squads.so/main/navigating-your-squad/transactions#rent-reclaim)
    : Recover rent associated with onchain accounts created during Squads transactions.
    
*   [Priority fees](https://docs.squads.so/main/navigating-your-squad/transactions#how-transactions-work-inside-squads)
    : Set custom priority fees to ensure smooth transaction execution during high network activity.
    
*   [Contacts](https://docs.squads.so/main/navigating-your-squad/treasury-assets#contacts)
    : Save addresses as contacts to streamline fund withdrawals.
    

For teams looking for advanced features and granular controls over their assets, the [Squads Business](https://docs.squads.so/main/getting-started/pricing)
 plan equips them with additional powerful features such as:

*   Permissions: Define custom roles and transaction approval criteria for each multisig member.
    
*   Payments: “Recipients” feature to create, track, and manage recurring payments—eliminating manual entry and saving teams valuable time.
    
*   Sub-accounts: Create separate vaults to efficiently manage various treasury assets, including payroll, marketing expenses, and NFT holdings.
    
*   Fee Relayer: Enable the multisig to cover network fees for members interacting with the Squad, providing a gasless experience from their perspective.
    

Learn more about our pricing plans [here](https://docs.squads.so/main/getting-started/pricing)
.

#### 

[](https://docs.squads.so/main/getting-started/treasury-management-overview#compliance)

Compliance

Squads users can use [Integral](https://integral.xyz/)
, a platform for real-time bookkeeping, accounting, tax compliance, and treasury management for businesses and individuals. To get started:

*   Set up an account on Integral
    
*   Copy and paste your Squad Vault address into the platform
    
*   Get access to automated bookkeeping, data, real-time treasury insights, and policies to meet your compliance and accounting requirements
    

#### 

[](https://docs.squads.so/main/getting-started/treasury-management-overview#staking)

Staking

Staking is the easiest way to earn a yield on your SOL. Enterprises can stake their SOL from the Squads app using:

*   [Squads Validator](https://squads.so/blog/update-introducing-squads-validator)
    ;
    
*   liquid staking providers (fuseSOL, Jito, Marinade, SolBlaze, marginfi);
    
*   specific Solana validator (powered by [Stakewiz](https://stakewiz.com/)
    ).
    

Learn more about staking [here](https://docs.squads.so/main/navigating-your-squad/in-app-integrations/staking)
.

#### 

[](https://docs.squads.so/main/getting-started/treasury-management-overview#in-app-trading)

In-app Trading

Enterprises can [trade their onchain assets](https://docs.squads.so/main/navigating-your-squad/trade)
 directly from within the Squads app using:

*   [Limit Orders](https://docs.squads.so/main/navigating-your-squad/trade/limit-orders)
    : Automate trades at predetermined price points, executing only when market conditions meet agreed-upon criteria. This feature is ideal for users who don't require immediate asset trades and prefer to wait for optimal market conditions.
    
*   [Spot Swaps](https://docs.squads.so/main/navigating-your-squad/trade/swaps)
    : Execute trades at current market prices. This option is ideal for teams requiring quick transactions. Note that these swaps are susceptible to failure due to price slippage and route expiration - issues amplified in multi-signature environments due to inherent delays between transaction initiation, approval, and execution.
    

Trades are powered by [Jupiter](https://jup.ag/)
 and seamlessly integrated into the Squads platform. This allows enterprises to trade directly from their Squads account without the need to withdraw company funds to individual wallets that could be exposed to different attack vectors and risks.

#### 

[](https://docs.squads.so/main/getting-started/treasury-management-overview#treasury-operations-using-squadsx)

Treasury Operations using SquadsX

[SquadsX](https://squads.so/blog/squadsx-multisig-extension-wallet-solana)
 is a companion tool for Squads that enables teams to connect their Squads treasury to applications within the Solana ecosystem while maintaining smart account security.

Below are a few ways teams use SquadsX to earn yield, vest tokens, and manage their onchain treasury:

**Earning yield on stablecoins**

Squads users can earn fees & rewards on stablecoins by deploying liquidity into stablecoin pools. These strategies enable passive yield on your stable assets:

Users can connect their SquadsX extension with DEXs like:

*   [Orca](https://www.orca.so/)
     - The most dominant DEX on Solana, it has a variety of stablecoin pools for users to provide liquidity and earn yield.
    
*   [Raydium](https://raydium.io/)
     - Another DEX with stablecoin liquidity pools where users can deploy their stables and earn yield.
    

Or, with lending/borrowing platforms like:

*   [Save](https://save.finance/)
     (previously Solend) - One of the lending and borrowing protocols on Solana – it enables users to deposit USDC into their pools and earn yield.
    

**Token Vesting**

A common operation for most onchain companies is the vesting, minting, distribution, and management of their native token. There are many operations associated with a project’s native token like vesting, airdrops, token locks, minting, and more.

Squads provides an [in-app token manager](https://docs.squads.so/main/navigating-your-squad/developers-assets/token-manager)
 and enables companies to access [Magna](https://www.magna.so/)
 and [Streamflow](https://streamflow.finance/)
 via SquadsX for all these token-related operations. This allows companies to plan and manage their token operations easily while maintaining the security of their Squads multisig.

**Yield Aggregators**

Yield aggregators are beneficial for users looking for platforms that automate yield optimization, saving time and potentially enhancing profits.

SquadsX enables users to connect their multsig with these yield aggregators like:

*   [Lulo](https://lulo.fi/)
     - Aggregates the best rates for assets like USDC across five lending/borrowing platforms and automatically rebalances deposits to the protocol offering the highest APYs at any given time.
    
*   [Meteora](https://app.meteora.ag/)
     - Features Dynamic Vaults that automatically rebalance between top lending protocols every minute.
    

Using SquadsX, users can also connect their multisig with [Sanctum](https://www.sanctum.so/)
 and deposit SOL liquidity into the Infinity pool. The INF token users get in exchange is a yield-bearing token whose yield is a combination of staking yields and trading fees earned from the Infinity Pool.

**Treasury Yields and Diversified Stables**

The current landscape of stablecoin offerings on Solana is evolving quickly, offering projects innovative use cases beyond simple "wrapped" USD. Projects looking to diversify their stables with more productive, non-volatile solutions can use SquadsX to access these innovative solutions.

*   Maple offers U.S. treasury yield to Solana-based teams through USDC lending. Squads users can access [Maple’s Cash Management product](https://solana.maple.finance/#/earn/pool/7Vqn5fdwckZadYVoH312aErP8PqNGNUx8WDrvKAHYfMd)
     via SquadsX and earn yield from U.S. T-Bills.
    
*   You can also have other alternate stables such as EUROe and USDY in your Squads multisig to diversify your stable assets while earning additional yield.
    

Note: While we have highlighted the most widely used tools in the Solana ecosystem today, please note that this does not imply an endorsement of their safety or quality.

### 

[](https://docs.squads.so/main/getting-started/treasury-management-overview#security)

Security

Squads is trusted by over 250 teams in the ecosystem and secures over $10 billion in value. Squads Protocol v3 was the first multisig program on Solana made [immutable](https://x.com/SquadsProtocol/status/1628776620243963904)
 while Squads Protocol v4 has been made [immutable](https://x.com/SquadsProtocol/status/1859947607671607443)
, and undergone [two formal verifications](https://docs.squads.so/main/v/security/formal-verifications/squads-protocol-v4)
 and multiple audits from the industry's leading firms.

To learn more about our security measures, read our documentation [here](https://docs.squads.so/main/v/security)
.

### 

[](https://docs.squads.so/main/getting-started/treasury-management-overview#additional-resources)

Additional Resources

*   [Squads Blog](https://squads.so/blog)
    
*   [Squads v4 Github](https://github.com/Squads-Protocol/v4)
    
*   [Squads Developer Docs](https://docs.squads.so/main/v/development)
    
*   [The Squads App](https://app.squads.so/)
    
*   [The Squads App (v3)](https://v3.squads.so/)
    

### 

[](https://docs.squads.so/main/getting-started/treasury-management-overview#secure-your-treasury-with-squads)

Secure your treasury with Squads

If you are an enterprise looking for an easy-to-use and secure platform for secure, transparent, and efficient treasury management, create a Squad on [app.squads.so](https://app.squads.so/)
 and reach out to [\[email protected\]](https://docs.squads.so/cdn-cgi/l/email-protection#83e4e2f1f1e6f7f7c3f0f2e7f0adeaec)
 to learn more.

[PreviousThird-Party Payouts](https://docs.squads.so/main/getting-started/on-and-off-ramp/third-party-payouts)
[NextPricing](https://docs.squads.so/main/getting-started/pricing)

Last updated 11 months ago

---

# Email Protection | Cloudflare

Please enable cookies.

Email Protection
================

You are unable to access this email address docs.squads.so
----------------------------------------------------------

The website from which you got to this page is protected by Cloudflare. Email addresses on that page have been hidden in order to keep them from being accessed by malicious bots. **You must enable Javascript in your browser in order to decode the e-mail address**.

If you have a website and are interested in protecting it in a similar way, you can [sign up for Cloudflare](https://www.cloudflare.com/sign-up?utm_source=email_protection)
.

*   [How does Cloudflare protect email addresses on website from spammers?](https://developers.cloudflare.com/waf/tools/scrape-shield/email-address-obfuscation/)
    
*   [Can I sign up for Cloudflare?](https://developers.cloudflare.com/fundamentals/setup/account/create-account/)
    

Cloudflare Ray ID: **99fd72199a7ea606** • Your IP: Click to reveal 54.237.218.47 • Performance & security by [Cloudflare](https://www.cloudflare.com/5xx-error-landing)

---