Walletwasabi: Re-mixing: do not dequeue and/or wait n rounds before re-mixing

[kenny47]

I have anon set above 100 to ensure at least 2 rounds for each UTXO. Sometimes my coins are dequeued because the amount is lower than minimum required for the current round.

1. Would it be possible to not dequeue lower amount (that is not too low, but say within couple thousands sats of the current minimum)?

2. If everybody uses the anon set >100, isn't the probability of coins being mixed with same peers high? Could we have a configurable delay ("wait x rounds before registering coinjoined utxo again")? Alternatively, can coordinator make sure there is not high percentage of utxos from the same previous round?

[MaxHillebrand]

1. This is already happening, but eventually there is a cut-off line...
2. I had the same intuition and would also like to see a time staggered delay between re-mixes. But we need to do more research here.

[nopara73]

Would it be possible to not dequeue lower amount (that is not too low, but say within couple thousands sats of the current minimum)?

Yes, it's possible. Check out the daemon. Mix with the --keepalive option:
dotnet run -- --mix --keepalive --wallet WalletName.

If everybody uses the anon set >100, isn't the probability of coins being mixed with same peers high? Could we have a configurable delay ("wait x rounds before registering coinjoined utxo again")? Alternatively, can coordinator make sure there is not high percentage of utxos from the same previous round?

Generally speaking, if one waits intentionally many rounds before remixing he'll get close to exponential anonset growth (although we'll still show as it'd be linear) but he'll also pay more, because the round denomination would go more than enqueueing sooner.

[MaxHillebrand]

FYI, just added a quick explanation of the daemon to the docs.

I'm still a big fan of optional time staggering of re-registers...