I tried walking through Dusk’s privacy transaction flow from the perspective of a regular user.
No technical docs.
Just the operational steps.
The result: privacy isn’t free.
@Dusk offers two transaction models: Moonlight is a transparent account—simple like a normal transfer; Phoenix is a privacy account, hiding the amount and the relationship between transactions with zero-knowledge proofs. It sounds like users can choose freely.
But choosing itself is a cost.$BTC

If I’m a new user, how do I know when I should use Moonlight and when I should use Phoenix? If I use Phoenix to send a transaction, can the recipient’s wallet directly see the sender’s funds? If the recipient uses a Moonlight account, will this transfer become public at some point in the process?
A more practical issue is key management.
Phoenix’s privacy relies on encrypted notes and a viewing key. If I want an auditor to view certain transactions, I need to generate a viewing key and authorize access; if I want to revoke authorization, what’s the procedure? If the viewing key leaks, will all of my historical transactions be exposed?
Traditional blockchain wallet setups don’t need to answer questions like these.
Users only need to remember the seed phrase—when sending, they fill in the address, fill in the amount, and confirm.
But in #dusk ’s privacy model, users have to understand the differences between the two account types, manage additional keys, and decide what scenarios require selective disclosure. If the wallet UI doesn’t hide this complexity well, most people will just choose Moonlight because “it’s simple.”
I tried a few wallet demos that support DuskDS—the interface does indeed simplify things. But how much it’s simplified depends on product design, not something the protocol layer can fully solve.
So when I look at Phoenix’s privacy capabilities, I’m not just asking, “Can it be done technically?”
I care more about three experience hurdles: can ordinary users switch between Moonlight and Phoenix without feeling it, can generating and managing the viewing key be done with one click, and are the confirmation speed and gas cost for privacy transactions in the same ballpark as transparent transactions? Even if the privacy tech is strong, if users have to answer choice questions every time they send, remember extra keys, and wait longer for confirmations, then its actual usage rate will be constrained by the friction of the user experience.
So far, how much money do wallets actually solve this kind of user-side friction?
#dusk @Dusk $DUSK