Thanks for the replies. I will just re-sync.
Topic: Copying pruned blockchain with new wallet (Read 616 times)
Interesting. I haven't run a pruned wallet yet, and I didn't realize that you couldn't start a new wallet with a pruned blockchain.
It applies for importing private keys as well.ranochigo states that "the client cannot accurately obtain all the transactions related to your wallet", but if its a new wallet then there shouldn't be any transactions related to the wallet yet.
Additionally, doesn't a pruned node still keep the full UTXO? If so, it should still be able to figure out which unspent transaction outputs are yours.
To my understanding, Bitcoin Core automatically assumes the addresses that were imported in after or during the synchronization to have transactions associated with it already. This applies for the changing of wallet.dat.Additionally, doesn't a pruned node still keep the full UTXO? If so, it should still be able to figure out which unspent transaction outputs are yours.
They do.
It would be helpful for users to indicate if the address have transaction before the point of Blockchain prune but it may complicate things for the user if they don't understand it.
Interesting. I haven't run a pruned wallet yet, and I didn't realize that you couldn't start a new wallet with a pruned blockchain.
ranochigo states that "the client cannot accurately obtain all the transactions related to your wallet", but if its a new wallet then there shouldn't be any transactions related to the wallet yet.
Additionally, doesn't a pruned node still keep the full UTXO? If so, it should still be able to figure out which unspent transaction outputs are yours.
I'm sure there must be a reason not to allow creation of a new wallet.dat, I'm just not yet certain what that reason is.
ranochigo states that "the client cannot accurately obtain all the transactions related to your wallet", but if its a new wallet then there shouldn't be any transactions related to the wallet yet.
Additionally, doesn't a pruned node still keep the full UTXO? If so, it should still be able to figure out which unspent transaction outputs are yours.
I'm sure there must be a reason not to allow creation of a new wallet.dat, I'm just not yet certain what that reason is.
There is no workaround for that. Since the blockchain is pruned, it only has a limited number of blocks stored. The client has to rescan everytime you import an address. Without looking into every single block, the client cannot accurately obtain all the transactions related to your wallet and hence might omit some transactions.
I notice that if I copy a verified data directory that has a pruned blockchain, I can't create a new wallet without triggering a full re-sync.
Anyone have a workaround for this? Thanks.
Anyone have a workaround for this? Thanks.
Jump to: