Been going through Dusk's docs today, and something that trips people up is the assumption that this is just "a private blockchain," full stop. It's actually running two separate transaction models at once.

Phoenix is the shielded side — UTXO-based, where your funds sit as encrypted "notes" rather than a balance in an account. Moonlight is the other side: fully transparent, account-based, checked with plain BLS signatures, no zero-knowledge proofs anywhere near it. You can move DUSK back and forth between the two.

Here's the part I didn't expect: Phoenix itself isn't uniformly private either. Inside it, there are obfuscated notes and non-obfuscated ones, both sitting in the same Merkle tree but treated as distinct types, you can't spend one as the other. Things like gas refunds or staking rewards actually tend to move as non-obfuscated notes, even inside the "private" system.

So the misconception is basically: people hear "privacy coin" and picture everything hidden all the time. What Dusk seems to be going for instead is selective disclosure. You can hand someone a view key so they see your outputs (and the amounts, if obfuscated) without ever getting the ability to spend anything. Feels aimed squarely at the compliance/auditing side of the XSC standard rather than a simple on/off privacy switch.

Genuinely curious though: does handing out a view key actually satisfy a regulator, or does it just relocate the trust problem to whoever's holding that key?

@Dusk_Foundation #dusk $DUSK
$TUT
$STAR