Walletwasabi: Receive addresses not disappearing

[jgmontoya]

General Description

Receive addresses are not disappearing even with transactions to them in the mempool.

How To Reproduce?

1. Generate Receive Address
2. Close Wasabi Wallet
3. Send some funds to the generated address (broadcast tx)
4. When opening the wallet again, the receive address still shows in the Receive tab.

Expected Behavior

The UTXO should appear under the Send tab as unconfirmed.

Wasabi Version

1.1.6

[benthecarman]

This may be a result of not having finished downloading all of the required block filters. Can you make sure your wallet was fully synced?

[jgmontoya]

That's not it, the wallet is fully synced.

I've tried restarting it and letting it sync for a long time and the receive addresses still stay there.

This actually happened to me before, last time the addresses disappeared when the tx got confirmed. I expect it will do the same again.

[benthecarman]

Weird, maybe the transaction isn't entering your mempool.

[jgmontoya]

I can query it correctly with getmempoolentry <txid>

[benthecarman]

Your wasabi mempool will be different than your bitcoin core node's I believe

[jgmontoya]

Oh I didn't know that. Is there a way I can query the wasabi mempool to check if this is the problem?

[lontivero]

Wasabi doesn't download/synchronize the whole mempool from peers when it starts because it could be hundreds megabytes, however, Wasabi will detect the transaction once it is confirmed and then the address will disappear. In other words, it works as designed.

[MaxHillebrand]

Yes, @lontivero is right - although this is still bad UX that confuses users...

Thinking about this - might it be possible that Wasabsi server sends a BIP158 style "mempool filter"? The mempool is only downloaded when there is a hit. This way the user has "instant" feedback if there is a transaction of interest - or not.

I'm not sure if this works, cause each mempool is a unique snowflake :snowflake: :laughing:...

[lontivero]

Sending a filter would make possible to discover the user's wallet. Also, BIP158 filters are not updatable so, every time you find a new transaction you have to create and send a new filter. BIP158 filters don't help to create a good user experience.