Bitcoin Core wallet.dat restore shows wrong amount.

[Tanquen256]

What actually your purpose? Do you want to get the whole balance the same as what you see from your wallet in VM?
Or your purpose is to withdraw them all and transfer them to another wallet?

They are both the same wallet. One is old and unencrypted. I don't want to really move them I was just hoping there was a to update the old unencrypted wallet and get access to the coins. But the old unencrypted wallet is missing the last few transactions that the encrypted wallet has. It sound like no as HCP said when I encrypted wallet for safety reason, it resets the seed/keypool, generates a bunch of new keys/addresses and then "archives" the old keys/addresses (marks them as inactive so they don't get "used" when you generate a new address to receive or for change).

As it looks like there is no way to update the unencrypted version of the wallet. I'd like to know how to simply verify the amount in the encrypted wallet so I can maybe try to work with Dave at http://walletrecoveryservices.com/.

[LoyceV]

I'd like to know how to simply verify the amount in the encrypted wallet

Load it in Bitcoin Core, and let it synchronize the blockchain. It's easy, but slow.

[Tanquen256]

I'd like to know how to simply verify the amount in the encrypted wallet

Load it in Bitcoin Core, and let it synchronize the blockchain. It's easy, but slow.

I have done that a few times but Dave said: "You should be able to verify whether it's legit by looking up one of the addresses holding BTC on blockchain.com to verify the current balance."

And I tried using the getaccountaddress "" command but when I put the output into blockchain.com I get this for the BTC address and BCH address:

This address has transacted 0 times on the Bitcoin blockchain. It has received a total of 0.00000000 BTC ($0.00) and has sent a total of 0.00000000 BTC ($0.00). The current value of this address is 0.00000000 BTC ($0.00).

Has it really been zeroed out somehow?

[HCP]

The last transaction has two output address. It's a little confusing as the last day on the unencrypted wallet I had some sent transactions that I was having an issue sending they and the receiver later returned one. The ID and amount are the same in both but the date/time stamp differs by 4 hours or so.

Unencrypted Wallet
Both outputs have "ismine": false.

Encrypted Wallet
First output has "ismine": false.

Second output has "ismine": true with more info like, "desc" and "pubkey".

As I suspected... at some point after adding the encryption passphrase to the wallet.dat, you have then spent some coins using the "encrypted" wallet.dat... and that transaction has created "change" which was sent to a "change" address that is not in your "old unencrypted" wallet.dat

Effectively, the only way you're going to be able to recover all your coins, is to recover your wallet passphrase... All this to-ing and fro-ing with checking address balances and stuff really doesn't matter.

You've synced the blockchain, and you've rescanned the "encrypted" wallet.dat... you can be confident that the balance it is showing is "correct". However, without the wallet passphrase, you're not going to be able to get the full balance... as there are coins controlled by private keys that you cannot access. As, you have limited access to some of the keys with the "unencrypted" wallet.dat, then you'll only be able to get the balance that is shown in the "unencrypted" wallet (assuming that the unencrypted wallet has been fully synced/rescanned).


So, it now boils down to this:

- Do you have any idea at all what the passphrase might be?
- Did you ever make notes about your passwords?
- Did you use a common set of passphrases for things back when you were using these wallets?
- Did you use a common "structure" to your passphrases (ie. 6 chars starting with 1 uppercase + 4 numbers)?
- Were your passphrases relatively short (<=10 chars)?
- Just letters+numbers or did you use "special" characters like !@#$%^&*()_+ etc?

Your chances of recovering the passphrase depend on the answers to these questions.

[Tanquen256]

So, it now boils down to this:

- Do you have any idea at all what the passphrase might be?
- Did you ever make notes about your passwords?
- Did you use a common set of passphrases for things back when you were using these wallets?
- Did you use a common "structure" to your passphrases (ie. 6 chars starting with 1 uppercase + 4 numbers)?
- Were your passphrases relatively short (<=10 chars)?
- Just letters+numbers or did you use "special" characters like !@#$%^&*()_+ etc?

Your chances of recovering the passphrase depend on the answers to these questions.

Yes to most of those and I've made a list and tried all I can think of with the change passphrase option.

I've sent a message to Dave and he asked that I verify whether the encrypted is legit by looking up one of the addresses holding BTC. I was just trying to do as he asked but not sure I've done it right.

I tried using the getaccountaddress "" command but when I put the output into blockchain.com I get this for the BTC address and BCH address:

This address has transacted 0 times on the Bitcoin blockchain. It has received a total of 0.00000000 BTC ($0.00) and has sent a total of 0.00000000 BTC ($0.00). The current value of this address is 0.00000000 BTC ($0.00).

[HCP]

don't use the getaccountaddress command... just use the output address that you found from the last send transaction that shows "ismine: true" in the "encrypted" wallet.dat (and "ismine: false" in the old wallet.dat)... That address is where the "missing" coins are.

Then simply search that address on blockchain.com and see what the history/balance of that address is.


Also, I suspect you're using an old version of Bitcoin Core... getaccountaddress was deprecated several versions ago (v0.17 and removed in v0.18)...

[Tanquen256]

don't use the getaccountaddress command... just use the output address that you found from the last send transaction that shows "ismine: true" in the "encrypted" wallet.dat (and "ismine: false" in the old wallet.dat)... That address is where the "missing" coins are.

Then simply search that address on blockchain.com and see what the history/balance of that address is.


Also, I suspect you're using an old version of Bitcoin Core... getaccountaddress was deprecated several versions ago (v0.17 and removed in v0.18)...

Thanks for your patience.

"just use the output address that you found from the last send transaction"
Got the last Transaction ID from the encrypted wallet and then got the 2 output addresses the second one has the "ismine: true"

I then use that output address on blockchain.com? It has almost no coin listed???

[BitMaxz]

As it looks like there is no way to update the unencrypted version of the wallet. I'd like to know how to simply verify the amount in the encrypted wallet so I can maybe try to work with Dave at http://walletrecoveryservices.com/.

You just make things complicated why you don't check all addresses on receiving address from an encrypted wallet?

Here's the reference



Gather all addresses from that tab and paste it to notepad as I said recently.
You can check them one by one if what address has balance and calculate it in total so that you can provide it on http://walletrecoveryservices.com/
Dave wants to know if it's worth recovering or it's another wallet.dat file with a fake balance. There are lots of fake wallet.dat(lost password) out there with a huge amount of BTC balance selling on the market. So dave just wants to know if your wallet is not one of them.

If you can provide enough evidence that it has a balance then they will grab it and take the 15%-%20 of the fee after recovery.

You can also do what LoyceV said above and export all transactions in .csv you can provide them to Dave for analysis including all addresses from receiving address tab.

[Tanquen256]

Sorry, I'm just not good at this stuff and without the last post I'd not know about the receiving addresses list and so on.

There are 6 receiving addresses listed.

Only two show a received and sent amount and just one has a final balance of 0.00010000 BTC. The one with a final balance has an amount received that does look like the amount I original stated with in 2012.

That 0.00010000 BTC doesn't match the match the encrypted or the old unencrypted amount.

But I've had this VM saved from the last time I used it and the wallet shows the correct amount even after syncing the blockchain up to date.

I'll try sending Dave the CSV.


Thanks for putting up with me.

[HCP]

Sorry, I'm just not good at this stuff and without the last post I'd not know about the receiving addresses list and so on.

There are 6 receiving addresses listed.

Only two show a received and sent amount and just one has a final balance of 0.00010000 BTC. The one with a final balance has an amount received that does look like the amount I original stated with in 2012.

The problem with the solution offered by BitMaxz, is that I suspect the bulk of your coins are on a change address... NOT a receiving address. Bitcoin Core treats change addresses as "internal only" and tends to hide their existence from you. As such, change addresses will NOT be displayed in the "Receiving Addresses" list


However, you can actually get Bitcoin Core to display ALL your current "Unspent Transaction Outputs" (aka UTXOs) in a fairly easy manner...

1. Set Bitcoin Core to enable "Coin Control Features"
- Goto: Settings -> Options:



- Select the "Wallet" tab... and make sure that "Enable Coin Control Features" is TICKED:



2. View all available UTXOs:
- On the main Bitcoin Core screen, select the "Send" Tab:



- You should now see the new section at the top labelled "Coin Control Features"... click the "Inputs..." button:


Assuming that your Bitcoin Core is fully synced and scanned (like your encrypted wallet should be), You'll see a list of all the coins that your wallet believes are currently available to be spent by your wallet. You will also see any "change" addresses listed with the label "(change)" as per the screenshot above. By default, "receive" addresses will tend to have "(no label)", but they can also have user-defined labels if one was manually added.

Each UTXO will also have the associated address listed with it... which you can easily copy by right clicking on the appropriate line and selecting "copy address" from the pop up menu... you can then paste the address into the blockexplorer of your choice to confirm that the coins/balance are correct etc.

You can also get the Transaction ID for the transaction that created that specific UTXO from the same pop up menu.


Hopefully, this method will allow you to see exactly which addresses your coins are currently associated with, and whether those addresses are "change" addresses, or "receive" addresses.

[nc50lc]

As it looks like there is no way to update the unencrypted version of the wallet. I'd like to know how to simply verify the amount in the encrypted wallet so I can maybe try to work with Dave at http://walletrecoveryservices.com/.

If that's the case, get all of your addresses with balance from the result of:

Lists groups of addresses which have had their common ownership
made public by common use as inputs or as the resulting change
in past transactions

Open the console (Window->Console) and type that command:

Code:

listaddressgroupings

All of your used addresses including change will show up there, the associated balance will display below each addresses.

[Tanquen256]

Dave is now working on finding the password. Maybe he will get lucky and find it soon. Just makes me mad that I have no real recollection of what password I used from just three years ago and that I did make an unencrypted backup but not after the last transaction and that I did not leave a clue to the password or something. Getting old stinks.

[Tanquen256]

FYI - I found an old backup of the wallet on my work laptop of all places and its file name gave me a clue about the correct pass phrase and after 30 tries or so I got it. 

[nc50lc]

FYI - I found an old backup of the wallet on my work laptop of all places and its file name gave me a clue about the correct pass phrase and after 30 tries or so I got it.  

Congratulations,
you might want to contact the service where you've given the other wallet.dat because he might still be working on its password.

There's a "lock topic" button below (lower-left) if you think this thread's issue is solved.

[Tanquen256]

Yeah, I let Dave know as soon as I was in but he said he was not currently working on it after a first pass.