@Dusk I used to think blockchain identity was something you built around a network, not something the network itself really needed.
Then I started looking at Dusk’s approach to regulated assets, and that assumption became harder to defend.
A blockchain can tell me which address owns an asset. But in a regulated market, ownership is only part of the question.
Can this participant legally hold it?
Can they receive it?
Are they allowed to transfer it?
Those questions require information about the participant, not just the wallet.
That is where Citadel caught my attention. Dusk treats identity and access as infrastructure through credentials and selective disclosure. For example, a participant could prove something like residency, an age bracket, or accreditation without exposing unrelated personal information.
That distinction matters.
A normal blockchain workflow might ask, “Which address owns this?”
A regulated workflow may need to ask, “Is this participant permitted to perform this action?”
Those sound similar, but they solve completely different problems.
And the more I think about tokenized financial assets, the more identity starts to look less like an extra application feature and more like part of the underlying infrastructure.
That is probably what I find most interesting about Citadel.
It connects the identity of the participant with the rules governing what they can actually do on-chain.
#dusk $DUSK
Then I started looking at Dusk’s approach to regulated assets, and that assumption became harder to defend.
A blockchain can tell me which address owns an asset. But in a regulated market, ownership is only part of the question.
Can this participant legally hold it?
Can they receive it?
Are they allowed to transfer it?
Those questions require information about the participant, not just the wallet.
That is where Citadel caught my attention. Dusk treats identity and access as infrastructure through credentials and selective disclosure. For example, a participant could prove something like residency, an age bracket, or accreditation without exposing unrelated personal information.
That distinction matters.
A normal blockchain workflow might ask, “Which address owns this?”
A regulated workflow may need to ask, “Is this participant permitted to perform this action?”
Those sound similar, but they solve completely different problems.
And the more I think about tokenized financial assets, the more identity starts to look less like an extra application feature and more like part of the underlying infrastructure.
That is probably what I find most interesting about Citadel.
It connects the identity of the participant with the rules governing what they can actually do on-chain.
#dusk $DUSK