#dusk $DUSK @Dusk Something small in the Citadel docs kept pulling me back.
Per Dusk’s own documentation, personal attributes never get written to the blockchain. The on-chain session leaves out the wallet key, the license itself, the provider key, the signed attributes, and the proof path. A service only gets what its own policy specifically asks for.
I’d mostly associated privacy with hidden balances. This sits one layer quieter. Someone can prove they meet an eligibility rule without the underlying personal record becoming part of the public chain state.
For regulated financial applications that need both privacy and verification, that distinction feels practical.
I keep wondering how often these selective disclosures will actually get requested once XSC contracts are running live, and how much of that check stays off-chain.
Per Dusk’s own documentation, personal attributes never get written to the blockchain. The on-chain session leaves out the wallet key, the license itself, the provider key, the signed attributes, and the proof path. A service only gets what its own policy specifically asks for.
I’d mostly associated privacy with hidden balances. This sits one layer quieter. Someone can prove they meet an eligibility rule without the underlying personal record becoming part of the public chain state.
For regulated financial applications that need both privacy and verification, that distinction feels practical.
I keep wondering how often these selective disclosures will actually get requested once XSC contracts are running live, and how much of that check stays off-chain.