Actions: multisig

A multisig needs several signers to approve a transaction before it runs, so no single lost or stolen key can move funds. Teams, treasuries and subnet owners use multisigs to hold keys safely. Taostats Actions handles the whole flow in the browser. Open Multisig.

For how multisig works on Bittensor, see Multisig, explained and Extrinsics: multisig.

Actions

Import or Create New Multisig Wallet

Adds a multisig from its signatories and threshold. A multisig's address comes from those two things, so importing and creating are the same step. It is saved in this browser only; nothing goes on chain until the multisig has a transaction.

Create Your Multisig Transaction

Starts a transaction from call data, and your signature counts as the first approval. Choose Public (the full call goes on chain, so co-signers can read it) or Private (only the hash goes on chain until the final approval). Make unguessable adds a random remark so a predictable call cannot be guessed from its hash.

Approve Multisig

Approves a pending transaction. Paste the call data to check it against the pending hash before you sign. The approval that reaches the threshold must carry the full call data, because that approval executes the call.

View or Cancel Multisig Transactions

Lists pending transactions for your multisigs and cancels one before it executes.

Build any action as a multisig transaction

Every other action shows its Call data on the review screen, and you can copy it without signing. Paste it into Create Your Multisig Transaction to run that action from a multisig: a stake, a proxy change, a subnet hyperparameter, anything in the catalogue.