#dusk $DUSK @Dusk

Been reading through the docs today and got stuck on something in Dusk's transaction model that's easy to skim past — the difference between a View Key and a Secret Key.

In Phoenix, Dusk's UTXO-based model, you can hand someone your View Key so they can spot which outputs belong to you, and if a note is obfuscated, even see the value hidden inside it. But that key doesn't let them touch your funds. Spending only works with a separate Secret Key, one that stays with you alone.

That distinction is easy to gloss over, but it changes a lot. Giving someone visibility isn't the same as giving them control. You can let an auditor look without ever putting your assets at risk.

I think most people hear "privacy blockchain" and assume it means total secrecy from everyone, no exceptions. Dusk doesn't really work that way. Transactions still prove they're valid — no double spends, enough funds — using zero-knowledge proofs, without exposing the details by default. But the option to selectively reveal information through a viewing key is built into the system, not added on as an afterthought for regulators.

It's also worth noting Phoenix isn't the whole picture. There's Moonlight too, which is account-based and public, running alongside it. So privacy on Dusk feels less like a fixed property of the chain and more like a setting you choose per transaction.

Curious whether other privacy chains separate "who can see" from "who can spend" this cleanly, or if Dusk's approach is unusual here.

$TAC $TMX