#dusk $DUSK Many people put Dusk directly in the “privacy chain” category, and then come to a quick conclusion: once you put assets on it, others can’t see them. I reread the two transfer models in my wallet and found that privacy on this chain is not a default attribute—it’s chosen for each individual transaction.
#dusk$SPCXB
Dusk runs two sets of models at the same time: Phoenix and Moonlight. Phoenix is a UTXO-like shielding structure; the amounts and spend/receive relationships are wrapped in zero-knowledge proofs. Moonlight is a public account model—balances, senders, and recipients can be read directly from block explorers. They share the same set of mnemonic phrases, but they are two separate balance “pockets” that don’t interoperate.
The first easy trap is right here. Your wallet homepage gives you a combined total. You think your entire position is hidden, but the reality may be that half is on the shielded side and half is on the public side—and the public portion has never been hidden. $SNDKB
The second issue is conversion between the two sides. Converting a shielded balance to a public balance (or doing the reverse) is itself a chain action; the amount, timestamp, and the public addresses involved will all leave traces. If you habitually send out the full balance at once from the shielded side, and then spend from the public addresses, chain analysis will actually obtain a fairly clear timeline. The thing that truly leaks information is usually not cryptography—it’s usage cadence.
The third and most practical issue: exchange deposits, staking, and contract calls. The mainstream paths basically all land on Moonlight; using Phoenix costs extra gas due to the proofs. The more someone interacts frequently, the more likely they’ll stay on the public side long-term, even if they believe they’re using a privacy chain.
So when I assess DUSK’s privacy capability, I’m not going to stop at the question of whether it “supports zero-knowledge proofs.” Instead I look at three things: which model new users default to, how frequently cross-model conversions happen, and whether the portion of assets that truly needs to be kept confidential is always staying on the shielded side. The protocol provides choice—that’s the capability. Whether users make the right choice is another matter. @Dusk