Sign with a multisig account
A multisig account is a Terra account with a special key that can require more than one signature to sign transactions. This can be useful for increasing the security of the account or for requiring the consent of multiple parties to make transactions. Multisig accounts can be created by specifying:
- threshold number of signatures required
- the public keys involved in signing
To sign with a multisig account, the transaction must be signed individually by the different keys specified for the account. Then, the signatures will be combined into a multisignature which can be used to sign the transaction. If fewer than the threshold number of signatures needed are present, the resultant multisignature is considered invalid.
Generate a Multisig key
K
is the minimum number of private keys that must have signed the transactions that carry the public key's address as signer.
The --multisig
flag must contain the name of public keys that will be combined into a public key that will be generated and stored as new_key_name
in the local database. All names supplied through --multisig
must already exist in the local database.
Unless the flag --nosort
is set, the order in which the keys are supplied on the command line does not matter, i.e. the following commands generate two identical keys:
Multisig addresses can also be generated on-the-fly and printed through the which command:
Signing a transaction
This example uses test1
, test2
, test3
keys from LocalTerra. Import them into your Terrad keystore to follow along.
Step 1: Create the multisig key
As an example, assume that test1
and test2
want to make a multisig account with test3
.
First, import the public keys of test3
into your keyring:
Generate the multisig key with 2/3 threshold:
You can see its address and details:
Then, add 10 LUNA to the multisig wallet:
Step 2: Create the multisig transaction
Send 5 LUNA from your multisig account to terra1fmcjjt6yc9wqup2r06urnrd928jhrde6gcld6n
.
The file unsignedTx.json
contains the unsigned transaction encoded in JSON.
Step 3: Sign individually
Sign with test1
and test2
and create individual signatures.
Step 4: Create multisignature
Combine signatures to sign transaction.
The TX is now signed:
Step 5: Broadcast transaction