thanks for the great answer.
Topic: [Solved] migrating legacy wallets (Read 62 times)
Migration of a wallet does not invalidate keys. It only changes how things are stored and organized in the wallet. While you will get newly generated keys and all previous keys are "retired", those keys are still in the wallet and can still be used to send and receive Bitcoin.
Migration is a local operation that happens on a wallet file. It will not change any other wallet file, even ones that share the same keys. There is no signal nor anything observable that some other wallet on another node would be able to tell that a wallet has been migrated. However, if you have 2 copies of the same wallet, migrating both of them will result in a completely new and different set of keys being generated from that point on. After the migration, they will no longer generate the same addresses, although all previously generated addresses (and their keys) remain, as stated earlier.
Migration is a local operation that happens on a wallet file. It will not change any other wallet file, even ones that share the same keys. There is no signal nor anything observable that some other wallet on another node would be able to tell that a wallet has been migrated. However, if you have 2 copies of the same wallet, migrating both of them will result in a completely new and different set of keys being generated from that point on. After the migration, they will no longer generate the same addresses, although all previously generated addresses (and their keys) remain, as stated earlier.
I have 2 separate nodes (version 26) running, each using their own wallet.dat file. the wallet.dat files have the same keys though.
if i migrate the legacy wallet on one of the nodes does it affect the other node's wallet? meaning do the legacy wallet's keys become invalid at all?
if i migrate the legacy wallet on one of the nodes does it affect the other node's wallet? meaning do the legacy wallet's keys become invalid at all?
Jump to: