Open jo2h2 opened 3 years ago
I'd probably try this:
You can move the old wallet.db to the new machine. We store the passwords in docker secrets. You can recreate the requisite docker secrets on the new machine that you should have saved from the old machine. If you've already initialized the new machine's wallet, you can erase the existing docker secrets from that machine using docker secret rm HOT_WALLET_PASS
, etc, then put in your old ones this way:
`printf <your old wallet pass> | docker secret create HOT_WALLET_PASS -`,
`printf '<your old cipher seed>' | docker secret create HOT_WALLET_SEED -`,
`printf <your old btc address> | docker secret create HOT_WALLET_ADDRESS -`
The wallet should unlock using the new gateway's unlocker when you run the new system. Then the new system will be using your old wallet.
If this doesn't work, I'd say you should take the init script from gateway and modify it to accept your existing password and seed instead of generating a new one in this method: https://github.com/chainpoint/chainpoint-gateway/blob/master/init/index.js#L115
Please be advised that we can't provide much further support than this about the basics of bitcoin wallets. Additionally, when doing anything involving real btc, I'd advise taking backup snapshots of the hard disks in case you mess up, so that you can just revert to a backup disk image.
Thanks for your quick reply Jacob !
Will give this a try :-).
Hi,
during my first attempt with chainpoint gateway I loaded my ~/.chainpoint/gateway/.lnd/data/chain/bitcoin/mainnet$ wallet.db with some 0.0... BTC - but I screwed up this machine and I started (successfully) with a 2nd machine.
But now I have this wallet.db in a non working environment containing "some" BTC ...
What can I do to transfer these BTC from this wallet.db back into my main wallet ?
Thanks for any hint :-).
Best wishes, Jo ...