Quote from: BlackHatCoiner on Today at 09:58:35 AM

Does that mean there are default round parameters hardcoded in the client?

The way it works is that the round has a "MaxSuggestedAmount" and "LiquidityClue". You can read more about it here: https://github.com/WalletWasabi/WalletWasabi/issues/12500

Here's what round splitting looks like in practice - All 3 of these coinjoins were created at the ~same time with a total of 626 inputs and confirmed in block 845572:

https://mempool.space/tx/4a8fc729fb6aa879db47af7a3b3e34743888650da7bd6f9812c10950634c1189
https://mempool.space/tx/94ab6e19edc63bf29dc586a9c5447a3eb6f00100301212c199837f4d5b20ff84
https://mempool.space/tx/1d423480f59c27d8136f8a1d022461317fa1227860547e62ef5b212dd972f2da

You can see the first tx has 65 BTC while the other two have 10 BTC, so the whales mostly managed to get into the same round as one another. This sorting is a result of the "MaxSuggestedAmount" being set lower in one round than another.

Quote from: BlackHatCoiner on Today at 09:58:35 AM

Theoretically, it would might be recommended to avoid them, but practically, there is no internal function within the client that would let me know they're running rounds in parallel, AFAIU. That's something I need to manually check. For example, I need to notice that my coins belong to different coinjoins. Isn't that correct?

Your wallet won't register inputs to two different rounds at once, it only registers inputs for the same round.