Spent an hour going through Dusk $DUSK docs for a #creatorpad piece and got stuck on one detail: it's not actually "private" in the way I assumed going in. @Dusk doesn't hide everything by default privacy is set at the transaction and smart contract level, so a developer can choose exactly what's confidential, what's fully public, and what's disclosable only under certain conditions (think an auditor request). That's a different design decision than the usual "everything's shielded" pitch you get from most privacy chains. I kept trying to find the actual toggle or parameter where that choice gets made in a contract like, is it a flag set at deployment, or something adjustable per call and the docs describe the behavior clearly but I couldn't pin down the exact mechanism from the outside. Feels like a meaningful distinction if you're thinking about compliance use cases, since "selective disclosure" and "anonymous by default" solve pretty different problems. Anyone who's actually written a contract on this where does that disclosure setting actually live?
#dusk