|
Title: Is it OK to use one Core client for two Core wallets? Post by: Gorilla22 on September 25, 2022, 10:04:00 PM I have 2 old Core wallets on the old PC.
Right now I am syncing a new Core on the new PC. Is it OK to use the new Core for both of old wallets just by changing "wallet.dat"? Will it work? Title: Re: Is it OK to use one Core client for two Core wallets? Post by: hosseinimr93 on September 25, 2022, 11:17:51 PM There is no problem with doing that.
You can have as many as wallet you want in a single device. Just take note that if you have downloaded the blockchain in pruned mode, you have to redownload it every time you import a new wallet.dat file. Title: Re: Is it OK to use one Core client for two Core wallets? Post by: Gorilla22 on September 25, 2022, 11:24:53 PM hosseinimr93,
you wrote "Just take note that if you have downloaded the blockchain in pruned mode, you have to redownload it every time you import a new wallet.dat file" Then it does not make any sense unfortunately :-( Because the idea was not to sync 2 Core for 2 wallets. My idea was to do initial syncing on new PC only once. Now I have understood that it will not work. Title: Re: Is it OK to use one Core client for two Core wallets? Post by: hosseinimr93 on September 26, 2022, 12:00:05 AM Now I have understood that it will not work. I feel you didn't understand me correctly. (Or maybe, I am not understanding you)In the case you import both of your wallets and then start syncing, you need to download the blockchain only once, even if pruning is enabled. If you run a full node (pruning is not enabled and you keep the entire blockchain), you can import as many as new wallets you want without any need to redownload the blockchain. Title: Re: Is it OK to use one Core client for two Core wallets? Post by: Gorilla22 on September 26, 2022, 12:42:30 AM hosseinimr93,
This is what I understood: Available option 1: Download full node, then you can replace wallet.dat as often as you want without necessity to do initial syncing again. No need to sync the whole blockchain. One can have 2 or more wallet.dat and use one today, another tomorrow, then the first one again etc. Available option 2: Place chosen wallet.dat into Core first, then sync in prune mode. This option doesn't enable to change wallet.dat that easily because every time you replace wallet.dat you need to sync the whole blockchain again. Option 3, unavailable and impossible: Sync in prune mode and replace wallet.dat as often as you want without need to sync the whole blockchain. Did I understand you correct? Title: Re: Is it OK to use one Core client for two Core wallets? Post by: tranthidung on September 26, 2022, 01:45:25 AM If you want to replace the wallet.dat file, you must have multiple backups first. You must name it transparently so that you can know what a file is for what specific wallet, just like wallet1.dat, wallet2.dat (you must know what 1, 2 represents for).
Because when you copy & paste that backup to the folder, you must rename it to wallet.dat to be readable. Then if you don't have previous note about that, you will not know what that wallet.dat represents for your specific wallet. Title: Re: Is it OK to use one Core client for two Core wallets? Post by: Gorilla22 on September 26, 2022, 02:40:08 AM About pruned sync node:
"You have to resync your wallet with blockchain if you import a wallet.dat file that contains data synchronised outside the data stored in your prune node. This is very annoying, IMO" From here: https://bitcointalk.org/index.php?topic=5213552.0 |