Module state 

Structs

Batch

Stores data required for serial execution of a batch of multisig vault transactions. Vault transaction is a transaction that’s executed on behalf of the multisig vault PDA and wraps arbitrary Solana instructions, typically calling into other Solana programs. The transactions themselves are stored in separate PDAs associated with the this account.

ConfigTransaction

Stores data required for execution of a multisig configuration transaction. Config transaction can perform a predefined set of actions on the Multisig PDA, such as adding/removing members, changing the threshold, etc.

Member

Multisig

MultisigCompiledInstruction

Concise serialization schema for instructions that make up a transaction. Closely mimics the Solana transaction wire format.

MultisigMessageAddressTableLookup

Address table lookups describe an on-chain address lookup table to use for loading more readonly and writable accounts into a transaction.

Permissions

Bitmask for permissions.

Proposal

Stores the data required for tracking the status of a multisig proposal. Each Proposal has a 1:1 association with a transaction account, e.g. a VaultTransaction or a ConfigTransaction; the latter can be executed only after the Proposal has been approved and its time lock is released.

SmallVec

Concise serialization schema for vectors where the length can be represented by any type L (typically unsigned integer like u8 or u16) that implements AnchorDeserialize and can be converted to u32.

SpendingLimit

TransactionMessage

Unvalidated instruction data, must be treated as untrusted.

VaultTransactionMessage

Enums

ConfigAction

Period

The reset period of the spending limit.

Permission

ProposalStatus

The status of a proposal. Each variant wraps a timestamp of when the status was set.