#dusk $DUSK @Dusk I keep looking at @Dusk and thinking that its privacy model is trying to solve a harder problem than simply hiding transactions.

Absolute anonymity sounds attractive, but regulated finance needs something else too.

Phoenix hides balances, participants, and transferred amounts using shielded notes and zero knowledge proofs, while still allowing information to be selectively revealed through viewing keys when auditing or regulation requires it.

That distinction matters.

Moonlight takes the opposite route with public, account based transactions. Having both models on the same settlement layer means applications can choose what should remain confidential and what needs to stay observable, instead of forcing every workflow into one privacy model.

That’s the part I’m watching.

The trade off is complexity. Selective disclosure only works if access controls, cryptography, and the surrounding application logic remain reliable. So Dusk is not really promising hide everything it is building around controlled visibility.


Could that evidence based approach prove more useful for real financial markets than absolute anonymity?