Went back through Citadel's 2023 launch notes and one line stuck: the "trustless" framing skips over who issues the license in the first place.
$DUSK #dusk Citadel design lets you prove eligibility — age, jurisdiction, accreditation — without exposing your full data to whoever's checking. That part's real. But the proof still traces back to a single license provider who verified your actual financial data upfront. The zero-knowledge layer hides your history from the verifier, not from the issuer.
What changed for me was realizing this doesn't remove trust, it relocates it. You're not handing your file to every counterparty anymore — you're trusting one party to have checked it right, and to keep checking. Dusk's own materials floated periodic re-confirmation to keep licenses current, which, if it works as proposed, still leaves a window where a proof reads valid on-chain while the underlying facts have moved.
Worth flagging: this is based on the original 2023 design writeup, not confirmed current production behavior — Dusk's roadmap has shifted toward market infrastructure and tokenized settlement since then.
Next thing I'd check: whether Citadel ships in that newer stack, and how @Dusk_Foundation handles license revocation before a refresh cycle closes
$DUSK #dusk Citadel design lets you prove eligibility — age, jurisdiction, accreditation — without exposing your full data to whoever's checking. That part's real. But the proof still traces back to a single license provider who verified your actual financial data upfront. The zero-knowledge layer hides your history from the verifier, not from the issuer.
What changed for me was realizing this doesn't remove trust, it relocates it. You're not handing your file to every counterparty anymore — you're trusting one party to have checked it right, and to keep checking. Dusk's own materials floated periodic re-confirmation to keep licenses current, which, if it works as proposed, still leaves a window where a proof reads valid on-chain while the underlying facts have moved.
Worth flagging: this is based on the original 2023 design writeup, not confirmed current production behavior — Dusk's roadmap has shifted toward market infrastructure and tokenized settlement since then.
Next thing I'd check: whether Citadel ships in that newer stack, and how @Dusk_Foundation handles license revocation before a refresh cycle closes