Squads v3 Docs
  • Welcome to Squads
  • Who we are?
  • Basics
    • What's a Multisig?
    • What's a Squad?
  • Getting Started
    • Create a Squad
  • Navigating Your Squad
    • Dashboard
    • Vault
    • Transactions
    • Developers
      • Programs
      • Token Manager
      • Validators
      • TX Builder
    • Creators
    • Apps
    • Owners and Settings
  • Integrations
    • Staking
      • Stakewiz
      • JitoSOL
      • Lido
      • Marinade
      • SolBlaze
    • Tensor
    • Cardinal
    • Dialect
    • Bonfida
    • Jupiter
    • Coinflow
  • Security and audits
    • Security
    • Security Policy & Bug Bounty
    • Audit reports
  • Frequently Asked Questions
    • General
    • Protocol
    • Costs of using Squads
  • Development
    • PDAs
      • Multisig
      • Transaction
      • Instruction
      • Derivation
    • Authorities
    • Anchor IDL
      • Loading the Program
      • Create a Multisig
      • Transactions
        • Create a Transaction
        • Adding Instructions
        • Activating a Transaction
        • Approve / Reject a Transaction
        • Executing
    • SDK
  • Squads Community
    • Self Custody Society (SCS)
    • Community
Powered by GitBook
On this page
  1. Development
  2. Anchor IDL

Transactions

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 MultisigNextCreate a Transaction

Last updated 2 years ago