The word "standard" is what made me pause. A standard implies something other people adopt without needing to think about it, but everything I read about Dusk's selective disclosure model still requires deliberate configuration by whoever deploys the contract. $DUSK #Dusk @duskfoundation is being talked about as though it could become the default grammar of institutional finance, yet the mechanism only activates when someone chooses to set it up, viewing keys assigned, disclosure rules written, permissions scoped case by case. That's closer to a toolkit than a standard. A real standard tends to emerge when the default behavior becomes so common that opting out looks unusual, and right now Dusk's privacy is the opposite, something you have to reach for rather than something you're handed. It made me think about how many infrastructure narratives borrow the language of inevitability before the adoption curve actually earns it. Being technically capable of becoming a standard and functioning as one in practice are different claims, and the gap between them is usually where the real story sits. What would actually have to happen, in terms of who configures it and how often, before this stops being a feature and starts being assumed.
#dusk $DUSK @Dusk