edit: I resolved this by downloading the 32 bit wallet, backing up the previous Clam data directory and reinstalling. This time both wallets imported without issue and I have my Clams. Still curious as to what happened... Thanks again to tryphe for all the help!
-
I'm having an issue with digging. I dug 2 valid (afaik) wallet files but received no clams. However, several addresses entered from this same wallet on the FreeBitcoins.com site were shown as diggable, and I just dug one address via that site (
https://freebitcoins.com/clamchecker/digs/fcc24c32fc8a2d6e96af82bcd4de5d4a23c8257332844d08ffb1e10317942fb4/) - still waiting on payment but it seemed successful.
I downloaded Clams Client (clam-1.4.17-win64.zip - SHA256 E1206F....D492) yesterday from the GitHub link on the CLAMclient.com site. I then downloaded the bootstrap file (SHA256 checksum matched) and let it sync fully.
Next, I tried to import both an old Bitcoin and Litecoin wallet.dat. Although the wallets held addresses used before May 2014, no Clams were received in my wallet, which shows 0 balance and no visible transactions. I tried both digging both wallets multiple times, both via Import File in the wallet and from the importwallet command in the wallet's console. The console gave no output after running the importwallet command, just a red minus line with no text. The receive tab in my wallet displays a bunch of importwallet addresses, none of which match the addresses in the debug.log file.
I spoke to tryphe in #clams on freenode, he was very helpful but we weren't able to resolve the issue. He told me to examine the debug.log file and I found about 20 DIG entries. The weird thing is these entries link to transactions which occurred arround the time I was digging but lead to addresses not under my control (or at least not visible in the receive tab of my client). From the comments on clamsight, it looks like some of these addresses were dug via freebitcoins.com, others via a wallet, and most of them were spent to an exchange.
I'm really confused, can anyone help me understand what's going on here?
Having a "DIG" piped into your debug file doesn't suggest that the 'dig' has anything to do with you.
It is a common debug line which occurs any time a distribution output is moved - yours or anyone else's.
If you have a transaction that is signed with your keys, but you didn't sign it, you need to take
immediate security steps as the machine is compromised.
Remove any and all crypto from any and all keys stored on that machine.
Concerning the issue with digging, you might try expanding your key pool.
keypoolrefill ###
Replace '###' with a suitably large number.
Edit:
Alternatively, you could try the repairwallet command.