Re: Is a newly migrated Wallet contain the same private key for re-funding ?

You can use

Code:

migratewallet

to migrate your legacy wallet (BDB) to HD wallet.

1. Bitcoin Core Wallet should NOT be in prune mode. Per my test, it will crash if the wallet is in a prune mode.
2. Open Bitcoin Core Wallet and import your data
3. run command

Code:

migratewallet {legacy_wallet_name} {the wallet's password}

Wait for a few minutes, it's done.

If you have some private keys to import, my idea is to import them to a legacy wallet with a lower version Bitcoin Core Wallet, e.g. V24, then migrate the legacy wallet in V26.

Quote from: FredCailloux on March 07, 2024, 05:58:40 PM

I read this Subject from OP digital_mine: https://bitcointalk.org/index.php?topic=5475186.0

And now I am running Bitcoin Core V26 with a wallet created on V22. Let's call it OutletWallet.
Everytime I open OutletWallet I get a warning message:

Code:

the legacy wallet type is being deprecated...migrate...

So, I proceeded with Migrate Wallet so that I can function with an uptodate Wallet on V26.

I still have my Paper Wallet with Public/Private key and QR code printed way back when I printed that sheet.

Will the new migrated OutletWallet still receive funds when I will utilize my QR code paper wallet to fund again ?

If I want a new paper document to backup my new OutletWallet, what informations should be printed so that I can retreive my funds in case of possible problems with computer or else ? Is there a function in the Console that I can utilize to show such information ?
Thanks