#dusk $DUSK @Dusk The first time I looked at Dusk’s transaction layer, having both Moonlight and Phoenix seemed unnecessarily complicated.
Then I looked at what each model is actually solving.
Moonlight uses public, account-based transfers with visible balances and sequential nonces. Phoenix uses shielded notes, nullifiers, and zero knowledge proofs to hide transaction details from observers. Both settle through DuskDS, but they solve very different privacy requirements.
That makes the split easier to understand: Dusk does not assume every financial transaction should expose everything or hide everything.
But there is a deeper trade off. Phoenix requires a different operational model for wallets, custody, scanning, and privacy-preserving transfers. Exchange integrations, for example, are designed around Moonlight because Phoenix requires separate handling.
Interestingly, Dusk’s Boreas upgrade later retired Phoenix transactions on mainnet, making this architecture even more interesting to study.
So the question I’m watching is: what did Dusk learn from Phoenix that will shape its next privacy model?