highperfocused/bitcoin
1
0
Fork 0
mirror of https://github.com/bitcoin/bitcoin.git synced 2025-08-25 13:01:11 +02:00
Code Issues Packages Projects Releases Wiki Activity

doc: add note for watch-only wallet migration

Browse Source 
This was suggested in a previous PR 31423.
This commit is contained in:
rkrux
2025-07-03 17:25:16 +05:30
parent 49d5f1f2c6
commit 5888b4a2a5
1 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
doc/managing-wallets.md
View File

@@ -144,12 +144,15 @@ If the wallet passphrase is too complex and is subsequently forgotten or lost, t
Legacy wallets (traditional non-descriptor wallets) can be migrated to become Descriptor wallets
through the use of the `migratewallet` RPC. Migrated wallets will have all of their addresses and private keys added to
a newly created Descriptor wallet that has the same name as the original wallet. Because Descriptor
wallets do not support having private keys and watch-only scripts, there may be up to two
a newly created Descriptor wallet that has the same name as the original wallet. As Descriptor
wallets do not support having both private keys and watch-only scripts, there may be up to two
additional wallets created after migration. In addition to a descriptor wallet of the same name,
there may also be a wallet named `<name>_watchonly` and `<name>_solvables`. `<name>_watchonly`
contains all of the watchonly scripts. `<name>_solvables` contains any scripts which the wallet
knows but is not watching the corresponding P2(W)SH scripts.
contains all of the watchonly scripts. `<name>_solvables` contains any scripts that the wallet
knows but for which it is not watching the corresponding P2(W)SH scripts. If the legacy wallet
contains only watch-only scripts and no private keys, then only the `<name>_watchonly` wallet
will be created and the descriptor wallet with the same name will not be created. Additionally,
the created watch-only descriptor wallet will not have private keys enabled.
Migrated wallets will also generate new addresses differently. While the same BIP 32 seed will be
used, the BIP 44, 49, 84, and 86 standard derivation paths will be used. After migrating, a new