prepare_multisig
and send data to ALL other partiesmake_multisig <threshold> <data1> <data2> .... <dataN>
and send 2nd batch of data to ALL other partiesfinalize_multisig <data1> <data2> ...... <DataM>
with the data from ALL other parties.export_multisig_info <filename>
and send the file to all other partiesimport_multisig_info <filename1> <filename2> ..... <filenameM>
and import files from other partiesmultisig_beldex_tx
which must be sent to any 1 other signersign_multisig multisig_beldex_tx
and the file is updated with the signature.submit_multisig multisig_beldex_tx
.N
empty beldex-wallet-cli
wallets.beldexd
.N
people should open up their beldex-wallet-cli
and generate a new wallet. Make sure you do not have any $beldex within your wallet.N
th person commands in their beldex-wallet-cli
:Multisig…...Vozid
and be sure to capture the whole thing when copying.Multisig…...arg
to each other person, it is suggested to send this information through a private comunication channel.N
people now have the Multisig...arg
text from the other N-1
people. With that, each of them can create their part of the multisig wallet. Before you proceed, note that the wallet will lose access to the underlying wallet when converted to multisig. This is not really a problem, since we started with an empty wallet, and if all goes OK with this step, you won't ever need it unless you want to go through the process again for whatever reason (like HDD died, but you have the seed mnemonic of the underlying wallet and want to reconstruct the multisig wallet).<threshold>
is the number of signers required out of the N
people, <data person 2>
is the output provided by Person 2, and <data person 3>
is the output provided by Person 3, and <data person N>
is the output provided by the N
th person.Multisig....arg
. One is from person 2 and other from person 3, if their is 5 different people their would be 4 different strings of Multisig....arg
. The number at the beginning is the minimum required number of signatures. Since it's a 2/3 scheme - it's 2. <threshold>
that equals 5 and 7 strings of multisig...arg
.make_multisig
command will be similar to:Multisig...arg
info that was just outputted must be passed to ALL other participants (For person 1 they must send it to persons 2 & 3 ... all the way up to person N).Multisig…....arg
strings received from other parties.miN
can be any filename. The output will be:miN
will be located in the shell working folder*mi1
has been saved.*beldex-wallet-cli
and use Person 2, 3, 4 ... N’s download link to run the commands:<link>
with the link Person 2, 3 ... N shared with Person 1 and <filename>
with the filename of the Multisig info file that Person 2, 3 or ... N generated, for example Person 1 will run the command:beldex-wallet-cli
and downloading with the alternative Persons download link, and filename.beldex-wallet-cli
from. There should be a file named multisig_beldex_tx
.multisig_beldex_tx
to one of the people who will sign the TX.multisig_beldex_tx
to the Person 1, 2 or N. Person 3 can send this file through email or alternatively use the transfer.sh commands outside of the wallet:<link>
.beldex-wallet-cli
.beldex-wallet-cli
directory.https://transfer.sh/CJqnM/multisig_beldex_tx
with the link provided by Person 3.beldex-wallet-cli
.Y
, and the output will look like:multisig_beldex_tx
file will need to be signed by the amount of signers required.Y
, and the transaction will be sent. The output will look like:show_transfers
command.The wallet will look for the files and export them to the folder from where it was started, ie where your command prompt / shell was when you calledbeldex-wallet-cli
. It may or may not be the same folder as your actual wallet files orbeldex-wallet-cli
, depending on how you go about it.For example, your wallet could be on some USB drive likef:\temp\
, and your wallet software onc:\beldex\
and your shell working folder could bec:\
.If you remain inc:\
with the shell, you could start the wallet by its full path and specify the wallet file location:c:\beldex\beldex-wallet-cli.exe --wallet-file f:\temp\mywallet
. In this case, all the import/export stuff would be read/written toc:\
because that's still your shell's working folder.It would be probably feel more natural tocd
into the wallet folder. Dof:
to change drive and thencd f:\temp\
. Then, simply start the wallet from that location by its full path again:c:\beldex\beldex-wallet-cli.exe --wallet-file mywallet
. Notice how you don't have to write the full wallet path now as you're already there with your shell. In this case, all the files mentioned above would be written or read from the same folder as the wallet files.