Bitcoin Forum
August 15, 2022, 12:55:16 PM *
News: Latest Bitcoin Core release: 23.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Wallet.dat file not working on .12 version pune mode  (Read 571 times)
Icon
Hero Member
*****
Offline Offline

Activity: 821
Merit: 503



View Profile
February 24, 2016, 02:35:06 AM
 #1

So... used my full node and prune it got it 100% sync update using the -prune=550 option.

Then copied my hot wallet thats ~ 2 years old into the data folder loaded up qt in prune mode to get error says could not access wallet.dat file due to the 2 gb limit being out of range and need to reindex/redown load the entire blockchain.

Correct me if i am wrong but isnt .12 client suppose to work with wallets transactions?

Wallet: Pruning
---------------

With 0.12 it is possible to use wallet functionality in pruned mode.
This can reduce the disk usage from currently around 60 GB to
around 2 GB.

Thanks

Icon
icon
Automate your trading like a pro. Lightning fast execution.
Start trading
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1660568116
Hero Member
*
Offline Offline

Posts: 1660568116

View Profile Personal Message (Offline)

Ignore
1660568116
Reply with quote  #2

1660568116
Report to moderator
gmaxwell
Staff
Legendary
*
Offline Offline

Activity: 3696
Merit: 6457



View Profile
February 24, 2016, 02:48:01 AM
 #2

Pruning works fine with a wallet. But you cannot just switch in an old out of date wallet and have it work: The wallet has no knowledge of any transactions that might have happened while it was offline, and so to catch it up the node must rescan... but a pruned node cannot rescan.

If you had put the wallet in first before starting the node with pruning the wallet would be fine and fully functional. The same goes for importing keys, you can only import loose keys without rescan.

In the future there may exist rescanning servers that can give you the transactions you're missing (if any), but doing this privately is quite tricky; and I doubt Core would rush in to a half-solution which destroyed your privacy when you have the option of not using pruning or not installing a cold wallet after pruning has taken effect. The initial work has started to enable such a thing with an API to import single transactions along with proofs that show they were in the blockchain.
Icon
Hero Member
*****
Offline Offline

Activity: 821
Merit: 503



View Profile
February 24, 2016, 03:13:53 AM
 #3

ok i can understand how that is a problem, got a question, can i use my cold wallet in my full node load and sync close the qt copy the data folder over onto 2nd pc, load qt in prune mode leaving the wallet.dat file in place?

Afterwards say after 2 months reload the prune qt client with the same wallet.dat file loaded and everything work, IE: not changing the wallet.dat file out at all.

Basically i could copy the entire data folder on a usb drive and keep it "offline" i am guessing.

Thanks

Icon



PRab
Member
**
Offline Offline

Activity: 98
Merit: 10


View Profile
February 24, 2016, 04:30:39 AM
 #4

Basically i could copy the entire data folder on a usb drive and keep it "offline" i am guessing.

That should work. As long as the wallet is in place before bitcoin core has a chance to prune anything it will work properly. The trouble comes when bitcoin core prunes something before the wallet had a chance to look at it.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!