Crate lmax_multisig

An example of a multisig to execute arbitrary Solana transactions.

This program can be used to allow a multisig to govern anything a regular Pubkey can govern. One can use the multisig as a BPF program upgrade authority, a mint authority, etc.

To use, one must first create a Multisig account, specifying two important parameters:

1. Owners - the set of addresses that sign transactions for the multisig.
2. Threshold - the number of signers required to execute a transaction.

Once the Multisig account is created, one can create a Transaction account, specifying the parameters for a normal solana transaction.

To sign, owners should invoke the approve instruction, and finally, the execute_transaction, once enough (i.e. threshold) of the owners have signed.

Modules

accounts

An Anchor generated module, providing a set of structs mirroring the structs deriving Accounts, where each field is a Pubkey. This is useful for specifying accounts for a client.

instruction

An Anchor generated module containing the program’s set of instructions, where each method handler in the #[program] mod is associated with a struct defining the input arguments to the method. These should be used directly, when one wants to serialize Anchor instruction data, for example, when speciying instructions on a client.

lmax_multisig

program

Module representing the program.

Macros

instructions_len

multisig_data_len

transaction_data_len

vec_len

Structs

Approve

ApproveBumps

Auth

AuthBumps

CancelTransaction

CancelTransactionBumps

CreateMultisig

CreateMultisigBumps

CreateTransaction

CreateTransactionBumps

ExecuteTransaction

ExecuteTransactionBumps

Multisig

Transaction

TransactionAccount

TransactionInstruction

Enums

ErrorCode

Constants

ID_CONST

Const version of ID

Statics

ID

The static program ID

security_txt

Static string containing the security.txt file.

Functions

check_id

Confirms that a given pubkey is equivalent to the program ID

entry

The Anchor codegen exposes a programming model where a user defines a set of methods inside of a #[program] module in a way similar to writing RPC request handlers. The macro then generates a bunch of code wrapping these user defined methods into something that can be executed on Solana.

entrypoint^⚠

Safety

id

Returns the program ID

id_const

Const version of ID