prepare_multisigand send data to each other
export_multisig_info <filename>and send the file to the other party
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.
Multisig...5ozpNand be sure to capture the whole thing when copying.
Multisig…...eJi4FSand send it to person A through a private communication channel.
Multisig...argtext from the other one. 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 account when converted to multisig. This is not really a problem, since we started with an empty one, 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 account and want to reconstruct the multisig wallet).
<filename>can be any filename.
mi1will be located in the shell working folder*
mi2will be located in the shell working folder*
beldex-wallet-cliand use Person B’s download link to run the command:
<Person B link>with the link Person B shared with Person A and
<filename>with the filename of the Multisig info file that Person A generated, for example Person A will run the command:
beldex-wallet-cliand downloading with Person A’s download link, and filename.
beldex-wallet-clifrom. There should be a file named
multisig_beldex_txto the Person B. Person A can send this file through email or alternatively use the transfer.sh commands outside of the wallet:
<link>to pass to Person B.
https://transfer.sh/CJqnM/multisig_beldex_txwith the link provided by Person A.
Y, and the output will look like:
Y, and the transaction will be sent. The output will look like:
Note on folders and file locations, as it could create some confusions. 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 called
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.For example, your wallet could be on some USB drive like
f:\temp\, and your wallet software on
c:\beldex-windows-x64\and your shell working folder could be
c:\.If you remain in
c:\with the shell, you could start the wallet by its full path and specify the wallet file location:
c:\beldex-windows-x64\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.It would be probably feel more natural to cd into 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-windows-x64\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.