prepare_multisigand send data to ALL other parties
make_multisig <threshold> <data1> <data2>and send 2nd batch of data to ALL other parties
finalize_multisig <data1> <data2>with the data from ALL other parties.
export_multisig_info <filename>and send the file to all other parties
import_multisig_info <filename1> <filename2>and import files from other parties
multisig_beldex_txwhich must be sent to any 1 other signer
sign_multisig multisig_beldex_txand the file is updated with the signature.
beldex-wallet-cliand generate a new wallet. Make sure you do not have any $beldex within your wallet.
Multisig…...Vozidand be sure to capture the whole thing when copying.
Multsig...argto Person 2 and 3, Person 2 to send their output to Person 1 and 3 and Person 3 to send their output to Person 1 and 2.
Multisig...argtext from the other 2. 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 3 people,
<data person 2>is the output provided by Person 2, and
<data person 3>is the output provided by Person 3.
Multisig....arg. One is from person 2 and other from person 3. The number at the beginning is the minimum required number of signatures. Since it's a 2/3 scheme - it's 2.
make_multisigcommand will be similar to:
Multisig...arginfo must be passed to ALL other participants (persons 2 & 3).
Multisig…....argstrings received from other parties.
mi1can be any filename. The output will be:
mi1will be located in the shell working folder*
mi1has been saved.*
beldex-wallet-cliand use Person 2 and 3’s download link to run the commands:
<link>with the link Person 2 and 3 shared with Person 1 and
<filename>with the filename of the Multisig info file that Person 2 or 3 generated, for example Person 1 will run the command:
beldex-wallet-cliand downloading with the alternative Persons download link, and filename.
beldex-wallet-clifrom. There should be a file named
multisig_beldex_txto either person 1 or 2.
multisig_beldex_txto the Person 1 or 2. Person 3 can send this file through email or alternatively use the transfer.sh commands outside of the wallet:
https://transfer.sh/CJqnM/multisig_beldex_txwith the link provided by Person 3.
Y, and the output will look like:
Y, and the transaction will be sent. The output will look like:
beldex-wallet-cli. It may or may not be the same folder as your actual wallet files or
beldex-wallet-cli, depending on how you go about it.
f:\temp\, and your wallet software on
c:\beldex\and your shell working folder could be
c:\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 to
c:\because that's still your shell's working folder.
cdinto the wallet folder. Do
f:to change drive and then
cd 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.