Okay. So I’ve a bitcoin core pockets from round August, 2012. I do not suppose I backed it up “correctly” in that I simply copied the pockets.dat file, zipped it and caught it in cloud storage.
I’ve some change in 2 of the addresses, which I’ve later discovered cut up into BTC Money as effectively.
I’ve loaded Bitcoin Core 22.0.0 and have fully synced the blockchain. No wallets loaded or new wallets created at this level. Then I attempted to restore the old-wallet.dat and after about 20+ minutes, I get this popup error:
And the db.log within the AppDataRoaming..old-wallet reveals
file pockets.dat has LSN 1/76511, previous finish of log at 1/476
Generally brought on by shifting a database from one database atmosphere
to a different with out clearing the database LSNs, or by eradicating all of
the log information from a database atmosphere
[..... these 4 lines repeat 48 times]
the debug.log
2024-03-02T17:22:43Z Utilizing BerkeleyDB model Berkeley DB 4.8.30: (April 9, 2010)
2024-03-02T17:22:43Z Utilizing pockets C:Customers...AppDataRoamingBitcoinwalletsOld-Walletwallet.dat
2024-03-02T17:22:43Z BerkeleyEnvironment::Open: LogDir=C:Customers...AppDataRoamingBitcoinwalletsOld-Walletdatabase ErrorFile=C:Customers...AppDataRoamingBitcoinwalletsOld-Walletdb.log
2024-03-02T17:22:43Z init message: Loading pockets…
2024-03-02T17:22:43Z [Old-Wallet] Pockets file model = 10500, final shopper model = 260000
2024-03-02T17:22:43Z [Old-Wallet] Legacy Pockets Keys: 0 plaintext, 206 encrypted, 0 w/ metadata, 206 complete.
2024-03-02T17:22:43Z [Old-Wallet] Descriptors: 0, Descriptor Keys: 0 plaintext, 0 encrypted, 0 complete.
2024-03-02T17:22:43Z [Old-Wallet] Pockets accomplished loading in 56ms
2024-03-02T17:22:43Z init message: Rescanning…
2024-03-02T17:22:43Z [Old-Wallet] Rescanning final 493953 blocks (from block 338894)...
2024-03-02T17:22:43Z [Old-Wallet] Rescan began from block 00000000000000000ff6f346bea61d1c87e455e2dd4e1da154e830dcfddba1f9... (sluggish variant inspecting all blocks)
2024-03-02T17:23:43Z [Old-Wallet] Nonetheless rescanning. At block 350638. Progress=0.066077
2024-03-02T17:23:43Z [Old-Wallet] Saving scan progress 350638.
2024-03-02T17:24:43Z [Old-Wallet] Nonetheless rescanning. At block 361394. Progress=0.074327
2024-03-02T17:24:43Z [Old-Wallet] Saving scan progress 361394.
2024-03-02T17:25:43Z [Old-Wallet] Nonetheless rescanning. At block 368839. Progress=0.081201
2024-03-02T17:25:43Z [Old-Wallet] Saving scan progress 368839.
2024-03-02T17:26:43Z [Old-Wallet] Nonetheless rescanning. At block 377874. Progress=0.089103
2024-03-02T17:26:43Z [Old-Wallet] Saving scan progress 377874.
2024-03-02T17:27:43Z [Old-Wallet] Nonetheless rescanning. At block 385876. Progress=0.097212
2024-03-02T17:27:43Z [Old-Wallet] Saving scan progress 385876.
2024-03-02T17:28:43Z [Old-Wallet] Nonetheless rescanning. At block 392935. Progress=0.105676
2024-03-02T17:28:43Z [Old-Wallet] Saving scan progress 392935.
2024-03-02T17:29:43Z [Old-Wallet] Nonetheless rescanning. At block 398759. Progress=0.113347
2024-03-02T17:29:43Z [Old-Wallet] Saving scan progress 398759.
2024-03-02T17:30:43Z [Old-Wallet] Nonetheless rescanning. At block 404095. Progress=0.121186
2024-03-02T17:30:43Z [Old-Wallet] Saving scan progress 404095.
2024-03-02T17:31:43Z [Old-Wallet] Nonetheless rescanning. At block 410007. Progress=0.129667
2024-03-02T17:31:43Z [Old-Wallet] Saving scan progress 410007.
2024-03-02T17:32:43Z [Old-Wallet] Nonetheless rescanning. At block 415252. Progress=0.137660
2024-03-02T17:32:43Z [Old-Wallet] Saving scan progress 415252.
2024-03-02T17:33:43Z [Old-Wallet] Nonetheless rescanning. At block 420359. Progress=0.145469
2024-03-02T17:33:43Z [Old-Wallet] Saving scan progress 420359.
2024-03-02T17:34:43Z [Old-Wallet] Nonetheless rescanning. At block 424845. Progress=0.152556
2024-03-02T17:34:43Z [Old-Wallet] Saving scan progress 424845.
2024-03-02T17:35:43Z [Old-Wallet] Nonetheless rescanning. At block 429990. Progress=0.160343
2024-03-02T17:35:43Z [Old-Wallet] Saving scan progress 429990.
2024-03-02T17:36:43Z [Old-Wallet] Nonetheless rescanning. At block 435183. Progress=0.168730
2024-03-02T17:36:44Z [Old-Wallet] Saving scan progress 435183.
2024-03-02T17:37:44Z [Old-Wallet] Nonetheless rescanning. At block 439881. Progress=0.176782
2024-03-02T17:37:44Z [Old-Wallet] Saving scan progress 439881.
2024-03-02T17:38:44Z [Old-Wallet] Nonetheless rescanning. At block 444238. Progress=0.185090
2024-03-02T17:38:44Z [Old-Wallet] Saving scan progress 444238.
2024-03-02T17:39:44Z [Old-Wallet] Nonetheless rescanning. At block 448552. Progress=0.193078
2024-03-02T17:39:44Z [Old-Wallet] Saving scan progress 448552.
2024-03-02T17:40:44Z [Old-Wallet] Nonetheless rescanning. At block 453098. Progress=0.201544
2024-03-02T17:40:44Z [Old-Wallet] Saving scan progress 453098.
2024-03-02T17:41:44Z [Old-Wallet] Nonetheless rescanning. At block 457196. Progress=0.209873
2024-03-02T17:41:44Z [Old-Wallet] Saving scan progress 457196.
2024-03-02T17:42:44Z [Old-Wallet] Nonetheless rescanning. At block 461365. Progress=0.217692
2024-03-02T17:42:44Z [Old-Wallet] Saving scan progress 461365.
2024-03-02T17:43:44Z [Old-Wallet] Nonetheless rescanning. At block 465338. Progress=0.225723
2024-03-02T17:43:44Z [Old-Wallet] Saving scan progress 465338.
2024-03-02T17:44:44Z [Old-Wallet] Nonetheless rescanning. At block 469048. Progress=0.233615
2024-03-02T17:44:44Z [Old-Wallet] Saving scan progress 469048.
2024-03-02T17:45:44Z [Old-Wallet] Nonetheless rescanning. At block 473171. Progress=0.241268
2024-03-02T17:45:44Z [Old-Wallet] Saving scan progress 473171.
2024-03-02T17:46:07Z [Old-Wallet] AddToWallet 4306eb4278cd03af36b9b4bb2bbfceaa2297acad4293c724255c792d8c02d9ac new Confirmed (block=000000000000000000dc975c23fd082c77d57feef2f98ec23a27f907616101ba, peak=475104, index=548)
2024-03-02T17:46:07Z Flushed price estimates to fee_estimates.dat.
2024-03-02T17:49:13Z New block-relay-only v1 peer linked: model: 70016, blocks=832847, peer=33
-
So I observed that Bitcoin QT by no means prompted me for the encryption password when importing this
pockets.dat…or no less than I by no means remembered seeing the immediate. Unsure if meaning something. -
I used to be in a position to make use of this pockets key instrument to view the
old-wallet.datfile. (I used to be prompted for the encryption key every time I needed to decrypt it). So IMO, the database cannot be that corrupt if a reader is ready to open it.It gave the impression to be a listing of strings. One column had addresses, one other column had non-public keys related to every tackle, and one other column had what gave the impression to be tackle labels that I keep in mind giving to a few of the addresses. The
date createdcolumn would not seem correct.
However there have been extra addresses than I created (I had both 6 or 8 addresses, however there have been greater than 200 rows of addresses/key combos).
So listed below are my questions:
-> Is it potential utilizing Bitcoin Core to get this old-wallet.dat file to import correctly and addresses present up within the GUI.
-> Is there a strategy to rebuild the pockets.dat file? It appears to crash as newer transactions might have extra columns that the older database would not have.
-> is there one other strategy to power import the addresses/keys? (in Bitcoin core or like utilizing a unique pockets) to the place I can sweep/entry the bitcoins?
-> why was third occasion instrument capable of learn .dat file (after decrypting) however Bitcoin Core can’t? Or why is not there a merely manner to do that?
