What struck me digging into DUSK $DUSK #dusk @Dusk wasn't the privacy pitch itself, it was who actually gets to use it by default. The compliant-by-design confidential transactions are framed as the headline feature, but in practice they sit behind an advanced setup path, while the default flow on most integrations still routes through transparent transactions because that's what's plug-and-play for wallets and exchanges right now. So the thing being marketed as the core differentiator is, today, the thing fewer users actually touch. It's not deception, more like sequencing, the compliance layer seems built for institutions who will configure it deliberately, not for a retail user clicking through a wallet setup. Makes me wonder how much of "privacy + compliance" narratives generally describe a roadmap state rather than a shipped default, and whether adoption numbers anyone cites are quietly measuring the easy path, not the one the project is actually betting on.