I've been sitting with Citadel on Dusk for a while. It's the identity layer they keep pointing at when they talk about regulated assets on-chain without the usual KYC mess.
You check once with a license provider. They verify you off-chain and register an encrypted license. Later you prove you hold a valid one. The contract only confirms a registered license exists. You pass a session cookie to the service. They never see your name, wallet, or which license you used.
It's like showing a stamp that says you're allowed in, instead of handing over your ID every time. Institutions don't store the data. Users don't repeat KYC for every venue. That matters if Dusk wants permissioned markets where eligibility is enforced but positions stay private.
You still trust the issuer to do the check properly. Service providers pick which issuers they accept and when a session dies. The code still carries the not-fully-audited disclaimer. Adoption is the real issue. Someone has to issue licenses and someone has to build services that actually consume the proofs instead of running another form on the side.
Citadel 2 tidied the protocol, but I still don't see much live use.
Will enough regulated players issue and accept these, or does this stay a clean design that never leaves the docs?
WHY CONFIDENTIAL FINANCIAL WORKFLOWS COULD MATTER MORE THAN EVM COMPATIBILITY Spent some time digging into Dusk lately and it changed how I think about L1s.🤔 Everyone chases EVM compatibility because it makes onboarding devs easy. Fair. But after watching how institutions actually behave, I'm not sure that's the winning bet for regulated finance. Real securities workflows need privacy baked in — you can't put a fund's positions on a fully public ledger and expect compliance teams to sign off. Dusk's approach is interesting: zero-knowledge proofs at the protocol level, so things like confidential transactions and regulated asset issuance aren't bolted on, they're native. That's a real differentiator. The trade-off is obvious though. Smaller dev ecosystem, less tooling, slower network effects. If nobody builds, the best privacy tech in the world just sits there. Liquidity is my other concern. Confidential assets are harder to market-make and harder to audit on-chain, which could scare off the exact DeFi activity that drives fees. Still, if tokenized securities actually become a thing, chains built for that from day one might age better than general-purpose ones retrofitted for compliance.