Walletwasabi: Change from transactions in version 1.1.10.2 not showing up in 1.1.11

[lee-chiffre]

General Description

It appears that change output generated in version 1.1.10.2 maybe earlier does not show up in version 1.1.11 Bitcoins sent INTO my Wasabi wallet but never spent in 1.1.10.2 show up in 1.1.11 fine. But change output from a transaction created IN Wasabi 1.1.10.2 does not show up in 1.1.11. This causes a problem where a user will think they are missing bitcoins. Or they might have bitcoins they are unaware of.

How To Reproduce?

1. Do a transaction in 1.1.10.2 with change. Wasabi will send remaining bitcoins to a change address.
2. Reset the local Wasabi folder to simulate a full sync with version 1.1.11. In the home directory rename or remove directory .walletwasabi/
3. Run Wasabi version 1.1.11 with a full sync.
4. If you run into the same problem I did you will see unspent incoming bitcoin but change output from the prior Wasabi version will be missing.

Operating System

Fedora 29 appvm in Qubes

Wasabi Version

Wasabi Version 1.1.10.2 and 1.1.11 downloaded from http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion and signature verified.

[lee-chiffre]

Is anybody else able to reproduce this issue? Does version 1.1.11 use a different change addresses path?

[lee-chiffre]

This was tested with a trezor t.

[lontivero]

How are you recovering your wallet? Are you using a wallet backup file or the recovery words?
What key gap are you using?

[lontivero]

I didn't see the latest comment. It is possible you need to increase the gap limit. Edit your wallet .json file and change the value of MinGapLimit (increase from 21 to 40) and Height (set to 0)

{
  "MinGapLimit": 40,
  "BlockchainState": {
    "Network": "Main",
    "Height": "0"
  }

After that save the file, launch Wasabi and open the wallet.

[MaxHillebrand]

Thanks for opening the issue here @lee-chiffre, that's easier for the devs than telegram. For reference I forwarded the issue previously in Slack.

I tested on Qubes 4 Debian 10, and I cannot reproduce it...

Mayb try resetting the "Height" as Lucas suggests.

[molnard]

Hi there,

Thank you for your report. First, we need to determine which balance is the correct one.
The questionable coin is unspent? Can you verify that if that coin is unspent?

1. If it is ~0.1 BTC try to enqueue it into a CoinJoin, if it gets registered then it is unspent.
2. You can click on the coin and copy the address, go to any block explorer and check if it is unspent.
3. Create a transaction to yourself. (you have to pay a tx fee in this case!)

Let me know if you need more help with this.

[yahiheb]

IMO just try the 2nd option using Tor and the onion url of a block explorer like https://blockstream.info/ for better privacy.

[lee-chiffre]

@molnard yes the change output is unspent and shows up just fine in version 1.1.10.2 even when completely deleting the ~/.walletwasabi and it re scans 1.1.10.2 picks it up just fine.

I will try @lontivero suggestion and see if Height and gap increase makes it show up in 1.1.11. then go from there. I updated the Trezor version t to 2.3 firmware that Satoshi Labs released today. And I dont think Wasabi is compatible with newest Trezor firmware. When Trezor with Wasabi fix I will try these suggestions.

[lontivero]

Wasabi has to display your correct balance no matter what, it has nothing to do with firmwares, HW models nor anything like that. In fact, wasabi only knows about the extended public key and nothing else. So, edit your wallet .json file, reset the Height to zero and increase the MinGapLimit to 40, 50 or 100 and try loading your wallet. You can also check your dust limit just in case.

[molnard]

I tried my best to reproduce this. Loaded my TestNet wallet several times, playing with the Gap limit and reset the wallet. I am sure there is something strange happening sometimes. Sometimes I got more coins those are fixed or not after several restarts.

I could not even determine if it is related to the version itself.

I cannot reproduce yet, but I am on it.

[molnard]

Closing this https://github.com/zkSNACKs/WalletWasabi/issues/3552#issuecomment-624000192