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. threhsold) of the owners have signed.

Note

• This code is unaudited. Use at your own risk.

Deployments

• Mainnet: A9HAbnCwoD6f2NkZobKFf6buJoN9gUVVvX5PoUnDHS6u
• Devnet: F3Uf5F61dmht1xuNNNkk3jnzj82TY56vVjVEhZALRkN

Upgrade Authorities

The program is upgradeable with self-referential multisigs as the authorities.

• Mainnet
  • Multisig: 3uztpEgUmvirDBYRXgDamUDZiU5EcgTwArQ2pULtHJPC
  • PDA: 2bXuJdSb4AeAZTBY8NDtYnSbxXGjgjkMHw9dPS9gjK9r
• Devnet
  • Multisig: FHY7K5SQvp7dUmGScjLih3hcwJe9GZ8cTShXkdeQJzRD
  • PDA: 5H4kCYbxpyKSb3BaL4qZNSJyqCLhs2aYCRTiUQTzQ7Rp

Note that the multisig is a program account and PDA is the program-derived-address, i.e., the signing address that can be used as the "authority" by other programs.

Developing

Anchor is used for developoment, and it's recommended workflow is used here. To get started, see the guide.

Build

anchor build --verifiable

The --verifiable flag should be used before deploying so that your build artifacts can be deterministically generated with docker.

Test

anchor test

Verify

To verify the program deployed on Solana matches your local source code, install docker, cd programs/multisig, and run

anchor verify <program-id | write-buffer>

A list of build artifacts can be found under releases.