A guide for creating a 2 of 3 multisig account and sending transactions
To follow this guide you’ll need
cyberdcli installed and connected to any cyberd node (refer to our cli guide). A reminder: this guide covers all types of transactions, not only send transactions. This guide is also relevant for Cosmos Hub Gaiacli users, except for the bandwidth params, in Cosmos we pay a fee using tokens.
Do not forget about the
--chain-id flag in
cyberd, and in the
Cosmos Hub networks. You can always get the current
in the master branch of the repository.
Creating a multisig
The multisig account creation and sending transactions are simple and clear but can be a little long.
- Import or create a thresholder accounts for multisig:
cyberdcli keys add test1 cyberdcli keys add test2
- Add pubkeys of remote thresholder accounts:
cyberdcli keys add test3 --pubkey=
We now have 3 accounts for multisig account generating:
test2 on a local machine that we have access to.
test3 from a remote thresholder that we do not have access to. All the created and imported accounts can be checked with:
cyberdcli keys list
- Now, we can create and test the 2-of-3 multisig account, named for example:
test2on a local machine and
test3on a remote thresholder:
cyberdcli keys add multitest1 --multisig=test1,test2,test3 --multisig-threshold 2
- You should top up the balance of your multisig account. Make sure that you have enough bandwidth to execute transactions later.
Spending out of a multisig account
- Create an unsigned transaction from the multisig account and store it in the
cyberdcli tx send
cyb --from= --chain-id= --generate-only > unsigned.json
- Sign this transaction with the following command and then store the signed file in
cyberdcli tx sign unsigned.json --multisig=
--from= --output-document sign1.json --chain-id=
- You need to send the obtained file to a remote thresholders for signing. You can see the content of the file containing the transaction with:
You may now copy the content that is convenient to your
.json file and send it.
You should also sign the remote thresholder, just like you did two steps above, and send your signed file back. For example
Copy the signed file from the remote thresholder into your cli home directory with the following command:
cp sign2.json $HOME/.cyberdcli
Your cli-home folder should content 3
sign2.json (at least). Those are the necessary and sufficient conditions, because we’ve set up a 2-out-of 3 multisig account.
- Generate a multisig transaction with all of the signatures:
cyberdcli tx multisign unsigned.json multitest1 sign1.json sign2.json --chain-id=
- Finally, we need to broadcast this transaction to the network:
cyberdcli tx broadcast signed.json --chain-id=
If the multisig account has enough bandwidth, the transaction should be broadcasted to the network.