Spent an afternoon reading through Dusk's docs instead of the landing page, and the thing that stuck wasn't the privacy pitch, it was how much of the "confidential" part is opt-in rather than default. $DUSK — the pitch is private data, public settlement, but in practice most flows still resemble a transparent chain unless you deliberately reach for the shielded contract path. That's not a flaw exactly, it's a design choice: make privacy available without forcing complexity on everyone on day one. But it does mean the headline feature is closer to a capability sitting off to the side than something baked into the default experience most users will touch first. Watching how the confidential transfer path required more explicit setup than the standard one, I kept thinking about how often "privacy-preserving" ends up meaning "privacy-possible" instead. Makes sense from an adoption standpoint. Still leaves me wondering how many people who hold the token ever actually use the part that's supposed to be the point.
#dusk $DUSK @Dusk