Walletwasabi: Restoring wallet from .json, no balance, no history

[Stadicus]

After reinstalling Linux on my work laptop, I want to restore my Wasbi wallet, which I saved as a file in .json format from the .wasabiwallet/client/Wallets folder. It might not be the most up-to-date, so missing a few transaction notes is fine, but it should be able to recover all coins and transactions.

Running Wasabi 1.1.11.0 on Ubuntu, it seems fully synced. I am able to open my wallet, but am not asked to enter a password. History is empty and balance is zero.

I see two receive addresses (derivation path index 4 and 12).

Other than some balance (I can't remember how much it was exactly, fortunately nothing significant), I would expect a lot of metadata, as the JSON file contains almost 200 individual transactions, plus change addresses.

Also strange is that if I import the xpub into Electrum wallet (running against my own Electrum server), there is also no history:

Any help in getting to the bottom of this is appreciated.

[MaxHillebrand]

Please try to modify the wallet file to "Height": "0",, this trigers a rescan and it should pick up everything.

[Stadicus]

Thanks, that solved the issue. Is this working as designed? I think that kind of defeats the purpose of a backup file.

For some context, the Height listed in the .json file was 622966 (as of March 26th, 2020). My wallet goes back to February 2019, however.

Also, what is the xpub listed in the .json file and in Wallet Info? Imported into Electrum wallet it does not return any transactions. The zpub listed in Wallet Info (but not in the .json file) works in Electrum and shows all addresses.

This whole issue was pretty confusing. If I had significant amounts in the wallet, I would definitely have freaked out quite a bit.

[MaxHillebrand]

Yes @stadicus, this is working as designed.
I'm not sure about the exact technicals, but I believe that the "Height" indicates at which block to start scanning the filters and check them for transactions. So, if your height is above the block that you started using the wallet, then it will not scan these blocks and find the transactions.

It is right that this kinda defeats the usability of the backup file... maybe the "Height" of the backup file should be by default 0 - thus triggering a rescan every time it is imported...

I would definitely have freaked out quite a bit.

Sorry about this... but sats are safu - neither private nor public keys leaked :)

[Stadicus]

No worries, all good. UX wise, I'd rethink the whole user story, as it still does not make much sense to me.