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

Transaction

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:

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:

["squad", multisig, transactionIndex, "transaction"]
PreviousMultisigNextInstruction

Last updated 2 years ago