They provide on-chain privacy via Whirlpool regardless of whether or not they have your xpub. If you think Samourai will collaborate with someone to demix and doxx you, run your own node and don't give them your xpubs.

They've made their position on this very clear (even talked about in a recent pod) - SW have considered forcing users to run their own node, but that would make their on-chain privacy tools unavailable for those who are not able to run their own node. So they opt to provide that as an option for users.

The reason they use xpubs is to make the wallet as light as possible on the client side so that it can perform well on the go, even when using a mobile connection and Tor.

Reply to this note

Please Login to reply.

Discussion

"Making the wallet as light as possible" is not an excuse for Samourai spying on their users' xpubs. Other light wallets like Wasabi use compact block filters so your xpub is never leaked. BIP157/BIP158 provides a private way to run a light wallet even on mobile - https://medium.com/breez-technology/as-free-as-the-breez-building-lightning-to-make-bitcoin-mobile-4f3d2cca22eb

Tell me what is your opinion about this fundamental formula of mixing.

It defines the difference between strong mixing and weak mixing. If you don't understand this difference, you can't understand the design choices made for Whirlpool. And you can't understand why the design choices made for Wasabi will always lead to a weaker form of mixing.

You seem to be incredibly confused: No amount of "strong" or "weak" mixing will ever make you private once your xpub is leaked. That's why privacy wallets like Wasabi use BIP157/BIP158 block filters so your xpub is never leaked. Samourai's wallet collects their users' full past and future transaction history data by default even though it is not required for them to do so.