At first, I thought Phoenix and Moonlight were two separate chains with no relation—or maybe even just two layers of the same network. Many people also frame it as a choice between a “privacy version” and a “transparent version.”
Only when I read through the whitepaper did I realize: they’re two different transaction models on the same ledger. Phoenix handles privacy transfers, staking, claiming rewards, unstaking, and converting from Phoenix to Moonlight. Moonlight, on the other hand, is a transparent account system—meant for cases where public disclosure is required or where you want to use a centralized exchange.
Under the hood, Phoenix is built on UTXO + Pedersen commitments + zero-knowledge proofs + stealth addresses, hiding the amount, the sender, the recipient, and the transaction graph. Moonlight is more like a traditional account model, where every transaction can be clearly checked. Assets can be converted between the two, turning “privacy” and “auditable” into two switches you can freely toggle.
It’s like a bank account that supports both “public reconciliation” and “anonymous authorization”—using the public ledger for external statements, and using the private ledger for internal rebalancing, with the switch happening in a single action.
The problem is the conversion logic itself. When assets move from Phoenix to Moonlight, could it expose the linkages between the two sides? I haven’t seen enough security analysis in the whitepaper, and that’s the question I most want to ask.
#dusk $DUSK @Dusk
Only when I read through the whitepaper did I realize: they’re two different transaction models on the same ledger. Phoenix handles privacy transfers, staking, claiming rewards, unstaking, and converting from Phoenix to Moonlight. Moonlight, on the other hand, is a transparent account system—meant for cases where public disclosure is required or where you want to use a centralized exchange.
Under the hood, Phoenix is built on UTXO + Pedersen commitments + zero-knowledge proofs + stealth addresses, hiding the amount, the sender, the recipient, and the transaction graph. Moonlight is more like a traditional account model, where every transaction can be clearly checked. Assets can be converted between the two, turning “privacy” and “auditable” into two switches you can freely toggle.
It’s like a bank account that supports both “public reconciliation” and “anonymous authorization”—using the public ledger for external statements, and using the private ledger for internal rebalancing, with the switch happening in a single action.
The problem is the conversion logic itself. When assets move from Phoenix to Moonlight, could it expose the linkages between the two sides? I haven’t seen enough security analysis in the whitepaper, and that’s the question I most want to ask.
#dusk $DUSK @Dusk