Spent an hour going through Dusk's docs expecting the usual "privacy-first" pitch, and the part that actually stuck was smaller than that. $DUSK #dusk @Dusk frame themselves around "privacy by default, auditability when required," which sounds like two settings a user can toggle. In practice it isn't symmetric. The privacy is protocol level and automatic the moment you transact. The auditability side is not something the transacting party controls at all it depends on who holds the cryptographic attestation keys, meaning compliance visibility is a relationship between the network and a regulator or institution, not a feature you interact with as a user. So the "default vs advanced" framing is really "your default vs someone else's advanced," and you never see which mode you're actually operating under from the user side. It's a sensible design for institutional rails, but it quietly shifts who the interface is built for. Reading it as a retail user made me realize the confidentiality promise and the compliance promise aren't even addressed to the same person. Makes me wonder how that split shows up once actual RWA volume starts moving through it.