435d6eb15f
|
||
|---|---|---|
| migrations | ||
| programs/multisig | ||
| tests | ||
| .gitignore | ||
| .travis.yml | ||
| Anchor.toml | ||
| Cargo.lock | ||
| Cargo.toml | ||
| LICENSE | ||
| README.md | ||
| SECURITY_AUDIT_REPORT.pdf | ||
| package-lock.json | ||
| package.json | ||
README.md
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:
- Owners - the set of addresses that sign transactions for the multisig.
- 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.
Note
- This code (0.9.0) is audited. Audit commissioned by Streamflow.
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.