Been digging into Dusk and $DUSK this week and one thing stuck with me more than the usual privacy blockchain pitch. It's the #dusk @Dusk keeps pushing the network lets you choose per transaction whether it's transparent or shielded, not just a blanket privacy on by default setup like most ZK chains go for. That's a small design choice but it changes the whole compliance story: an institution can run an auditable, fully visible transfer right next to a shielded one from the same wallet, same block. I tried to trace how that toggle actually gets enforced at the protocol level rather than just the wallet UI, and the docs get vague fast about whether the choice is baked into the transaction type itself or left to client-side implementation. If it's the former, that's a real technical claim worth checking against the code. If it's the latter, it's more of a UX promise than a protocol guarantee. Anyone who's actually read through the transaction spec know which one it is?