Anonset show as 214748... v2.0.6 about walletwasabi HOT 17 CLOSED

I wonder if this is just a UI bug, or if the wallet file has these wrong values as well, can you please check?

I can't see anonscore in wallet.json files.

It's become very hard to document all behaviors

Balance, and Privacy is doing random stuff almost every load.

I'm at 8+ different behaviors depending on which wallet I open first, even reopening the same wallet produce different result on reload.

Sometime wallet will only show the Non-private coins, Sometime it'll show private coins as 1 anon, sometime it'll show nonprivate as 214748....

Showing 214748 only happens when loading a 2nd or 3rd wallet with same seed.

from walletwasabi.

Showing 214748 only happens when loading a 2nd or 3rd wallet with same seed.

Wasabi doesn't support loading several wallets with the same seed. If your issue only happens in that case, please close it.

OTOH, yes I think that cross-wallet privacy computation features should be removed, it's too confusing and a very little benefit.

from walletwasabi.

I wonder if this is just a UI bug, or if the wallet file has these wrong values as well, can you please check?

The UI takes the double value and converts it to an integer. I don't know why it resulted in MaxValue.

AnonScore = (int)coin.HdPubKey.AnonymitySet;

from walletwasabi.

Not a UI issue. When you load the second instance of a wallet, its coins will have 2147483647 as anonscore.

from walletwasabi.

Had this happen to me too once, when I recovered the same wallet twice

from walletwasabi.

from walletwasabi.

I wonder if this is just a UI bug, or if the wallet file has these wrong values as well, can you please check?

from walletwasabi.

2147483647? It's int.MaxValue . There have been such issue in the past - #7453.

from walletwasabi.

I'm at 8+ different behaviors depending on which wallet I open first, even reopening the same wallet produce different result on reload.

This is the same as #6905

from walletwasabi.

Wasabi doesn't support loading several wallets with the same seed. If your issue only happens in that case, please close it.

I think a check should be done not to count score of the same seed, Or even simpler, If 2147483647 == 1

At least that'd cover the risk spending non-private coins thinking they are private. Very few people would ctrl-c-d and notice the red flag that something is wrong.

There's no plausible scenario where an anonscore can be anywhere this high, so
I suggest using this as a trigger to stop misleading illusion of privacy.

from walletwasabi.

Wasabi doesn't support loading several wallets with the same seed.

from walletwasabi.

Wasabi doesn't support loading several wallets with the same seed.

Wasabi does support that.

from walletwasabi.

🤦‍♂️

Has anyone read my suggestion to avoid that problem?

Just set anon to 1 whenever it's beyond too high.

Nobody come read here to see what's supported or not. Two similar wallet just seems to works ... but it disable the privacy protection and foot-gun!

from walletwasabi.

Trying to hotfix these kinds of issues when the concept is fundamentally not supported is a lot of hard work.

If in the future se decide to deal with this complexity, then well get back to this issue.

from walletwasabi.

What is not supported exactly, loading the same wallet twice? You can do that currently.

And there are many other problems not AS related, like not seeing the tx in the tx list when sending form the secondly loaded wallet.

from walletwasabi.

Please reopen this until we've fixed either the high privacy problem or detect and restrict that the same seed has been imported twice.

from walletwasabi.

Please reopen this until we've fixed either the high privacy problem or detect and restrict that the same seed has been imported twice.

#12765

from walletwasabi.