MultiChain Developer Q&A - Recent questions tagged backupwallet

Export/import wallet

Thu, 23 Dec 2021 12:35:18 +0000

Hi,

I'm trying to export a node's wallet & to import it on another, freshly stated node. I'm performing these steps described in the documentation:

1) Export wallet using the backupwallet function
2) Import the wallet on the new node using importwallet
3) Restart the new node to ensure the wallet is loaded properly

Now, if I use the command listaddresses on the new node no addresses have been added.

Am I missing something or is the backup/import wallet function not working correctly?

backupwallet crashes/stops server

Sun, 07 Apr 2019 17:57:56 +0000

On my running node:

$ multichain-cli sid backupwallet "backup.dat"

Expected outcome: A backed-up copy of the wallet.

Actual Outcome:

{"method":"backupwallet","params":["backup.dat"],"id":"64255931-1554659205","chain_name":"sid"}

error: no response from server

Any further CLI calls will give me a "error: no response from server". I have manually start the chain again.

Any idea on how to solve this?

Store privateKey in encrypted stream

Mon, 27 Aug 2018 20:16:24 +0000

I'm thinking about storing the created wallets privateKey in an encrypted stream only readable by the node. This stream could be subscripted from a backup-node. As a result the nodes gets more dynamic, backup of wallet.dat is not required anymore..

Any shortcomings of this ?

wallet.dat seems not to be written properly (after startup?)

Wed, 28 Feb 2018 10:29:10 +0000

At the moment I try to figure out a reasonable way to setup MultiChain clustering.

Now I stumbled across the following problem:

- creating master node

- try to connect second node (slave) -> gets info (need to join)

- cp wallet.dat from master node to slave node

- connect again -> getting message: Error: wallet.dat corrupt, salvage failed

This does not happen if I do a "backupwallet" before using the original wallet.dat:

What I have noticed:

- create and start a node

- md5sum(wallet.dat) = X

- trigger backupwallet "wallet.bkp"

- md5sum(wallet.dat) == md5sum(wallet.bkp) != X

So the wallet.dat changes after triggering backupwallet, and then I am also able to copy the original wallet.dat to the second node and the currupt error is gone.

I don't know what exactly is wrong here, but it seems that the wallet.dat is not usable until it is written again (in my case after triggering backupwallet, since this does not only write the backup but also changes the original wallet.dat)

Any idea?

Trying to run second node on behalf of another node

Mon, 02 Oct 2017 09:28:56 +0000

I am trying to create a second node with full admin permissions(admin,mine,connect) and all addresses and private keys that are in the first node that can act on behalf of another node. I require this in a very specific scenario and understand the risks involved.

I have tried the following:

Create wallet backup using backupwallet [filename]
Import wallet backup using importwallet [filename]

This only imported all addresses with mine:true, this i expected. All data is there at the time like balances and addresses.

However, I have no permissions for said addresses on this second node, I have to grant permissions again(send/receive).

Transactions are now seperated from the rest of the network, for example:

Node 1(original node) sends assets to an address which is now in both nodes but Node2(new node), has an imported wallet, the transaction only appears in node 1 and not in node 2.
Anything i do in Node1 does not reflect in Node2 and vice versa.

I am not sure if this is mining not happening or the way i imported the data but it does not show in node 2 when checking with listaddresstransactions.

There seems to be a case where the two nodes are not disconnected and do not share data anymore nor do they mine each others data even though they are connected to each other.

Could this be because i imported the wallet and now both act independantly or have i simply imported the data incorrectly and now there is an inconsistancy?