#dusk $DUSK @Dusk Many people who look at Dusk for the first time reduce Phoenix and Moonlight to a simple toggle - private mode and public mode. I kept thinking that framing misses what is actually interesting about how these two models sit inside the same protocol.
Phoenix is not just "private." It is a completely different transaction architecture. Funds do not live in balances - they live as encrypted notes. When you spend, you consume existing notes and create new ones, proving with zero-knowledge proofs that no double spend happened and that the amounts add up, without revealing who sent what to whom or how much moved. The receiver sees the note. Nobody else does, unless you share a viewing key.
Moonlight works the opposite way - account-based, fully transparent, sender and recipient and amount all visible on-chain. The kind of model most people already understand from Ethereum.
What caught my attention is that both models settle through the same Transfer Contract on DuskDS. They are not separate chains or separate ledgers. A Phoenix transaction and a Moonlight transaction can both exist inside the same block, finalized by the same consensus round, without either model needing to know about the other's internal logic.
The part worth sitting with is what this means for regulated assets. A securities transaction might need full transparency for the regulator and full privacy from the counterparty. Phoenix viewing keys make selective disclosure possible - you reveal exactly what you must, to exactly who requires it, nothing more. Moonlight handles flows where transparency is the requirement by default.
What I find harder to answer is whether regulators will accept viewing-key-based disclosure as equivalent to traditional audit trails. The cryptography works. Whether the legal frameworks catch up is a different question entirely.
Phoenix is not just "private." It is a completely different transaction architecture. Funds do not live in balances - they live as encrypted notes. When you spend, you consume existing notes and create new ones, proving with zero-knowledge proofs that no double spend happened and that the amounts add up, without revealing who sent what to whom or how much moved. The receiver sees the note. Nobody else does, unless you share a viewing key.
Moonlight works the opposite way - account-based, fully transparent, sender and recipient and amount all visible on-chain. The kind of model most people already understand from Ethereum.
What caught my attention is that both models settle through the same Transfer Contract on DuskDS. They are not separate chains or separate ledgers. A Phoenix transaction and a Moonlight transaction can both exist inside the same block, finalized by the same consensus round, without either model needing to know about the other's internal logic.
The part worth sitting with is what this means for regulated assets. A securities transaction might need full transparency for the regulator and full privacy from the counterparty. Phoenix viewing keys make selective disclosure possible - you reveal exactly what you must, to exactly who requires it, nothing more. Moonlight handles flows where transparency is the requirement by default.
What I find harder to answer is whether regulators will accept viewing-key-based disclosure as equivalent to traditional audit trails. The cryptography works. Whether the legal frameworks catch up is a different question entirely.