squads

Use multisig.rpc.multisigCreateV2 from the @sqds/multisig SDK with a one-time createKey, a threshold, and a members list with permissions. Derive the multisig PDA with getMultisigPda and send funds to the vault PDA derived via getVaultPda, not the multisig account itself.

Create a vault transaction with vaultTransactionCreate, then open a proposal with proposalCreate. Members vote using proposalApprove or proposalReject, and once the threshold is reached the transaction is executed with vaultTransactionExecute.

The Squads V4 Multisig program ID is SQDS4ep65T869zMMBKyuUq6aD6EgTu8psMjkvj52pCf on both mainnet and devnet. On Eclipse mainnet it is eSQDSMLf3qxwHVHeTr9amVAGmZbRLY2rFdSURandt6f.

Yes, create a spending limit through a config transaction with the AddSpendingLimit action, specifying mint, amount, period, members, and destinations. Authorized members then spend within the limit using spendingLimitUse without a full proposal.

Yes, Grid standing orders support daily, weekly, biweekly, monthly, quarterly, and yearly USDC payments via the /grid/standing-orders REST endpoint. Orders can be paused, resumed, updated, or cancelled, and webhook events report each execution.

NotAMember means the signing wallet is not in the multisig member list, and Unauthorized means the member lacks the required Initiate, Vote, or Execute permission. Verify membership and permission masks on the Multisig account before submitting.