Help Needed: Different Balances on Two Devices Using Wasabi Wallet

[left1338]

Hi everyone,

I'm having an issue with my Wasabi Wallet that I can't seem to resolve, and I’m hoping someone here can help me out. I'm using Wasabi on two different devices, but the wallet shows two different balances on each. Specifically, there is one transaction missing from the device that shows the lower balance. It’s a CoinJoin transaction of around 0.02XXXXXX BTC.

Here’s what I’ve tried so far:

I reset the block height to 0 on both wallets and re-synced the wallet.

I’ve also adjusted the MinGapLimit to 100, but nothing has changed.

No matter what I do, one device always shows more balance than the other. The missing transaction (the CoinJoin) just won’t show up on the device with the lower balance.

Has anyone encountered this issue before or know what could be causing it? Any advice on how I can resolve this would be greatly appreciated!

Thanks in advance!

[turbolay]

Hello, if you are not on latest version try to update and launch wasabi
If you are on latest. version, please delete your IndexStore.sqlite file (Search for data dir in Wasabi's search bar, close wasabi, then BitcoinStore/Main/IndexStore/IndexStore.sqlite)

[ghscuuo]

Maybe your wallets equilibrated after a while.

I'm a new wasabi user.

I was trusting but verifying Wasabi by watching my coins in parallel in Sparrow, and I noticed they were out of sync for a while. After several minutes they synced up fine. (There's a lot going on within a coinjoin.)

Maybe it's a Red coin, Dust threshold, or other similar feature that suppresses some coins on some app screens and functions, due to size or anonymity or age or other aspect? And so, in addition to checking the transactions, maybe also check the coins listing?

Good luck! Let us know.

[turbolay]

The only differences should be:

• IIRC, Sparrow only checks either SegWit either Taproot, Wasabi both
• Wasabi doesnt show pending coins if the transaction was made while wasabi was offline
• Wasabi doesn't show coins sent on a reused address lower than a threshold (Dust Threshold)

Then functions should be the same.

[ghscuuo]

Stumbled upon this, not sure it applies:
./.walletwasabi/client/{coinjoin coordinator}/PrisonedCoins.json

[turbolay]

no