Dusk is one of those projects that starts simple then gets more interesting the deeper you look.
i went into @Dusk_Foundation expecting phoenix and moonlight to be the usual pick your privacy level toggle. spent a while testing both before i understood what's different.
moonlight is account-based and public balances, senders, amounts, all visible, easy to reconcile. nothing surprising there, it behaves like most chains.
phoenix is the one that took longer to click. funds sit as shielded notes, zero-knowledge proofs confirm a spend is valid without revealing amounts or linking old notes to new ones. but it's not anonymous the receiver still knows who sent the funds, and view keys let you open specific transactions to an auditor without exposing everything else. on testnet, watching a phoenix transaction settle without an amount showing anywhere on the explorer was the moment it actually landed for me.
what stuck with me is that dusk built a shield/unshield function so you can move value between the two models yourself. that's when it stopped feeling like public chain vs private chain and started feeling like one settlement layer where visibility is a setting, not an architecture choice.
it's not free, though. phoenix means scanning for your own notes and generating proofs locally, more overhead than moonlight's plain account read.
which side would you actually trust more with your own funds?
#dusk $DUSK #Dusk
@Dusk_Foundation
$PORTAL $SKYAI
i went into @Dusk_Foundation expecting phoenix and moonlight to be the usual pick your privacy level toggle. spent a while testing both before i understood what's different.
moonlight is account-based and public balances, senders, amounts, all visible, easy to reconcile. nothing surprising there, it behaves like most chains.
phoenix is the one that took longer to click. funds sit as shielded notes, zero-knowledge proofs confirm a spend is valid without revealing amounts or linking old notes to new ones. but it's not anonymous the receiver still knows who sent the funds, and view keys let you open specific transactions to an auditor without exposing everything else. on testnet, watching a phoenix transaction settle without an amount showing anywhere on the explorer was the moment it actually landed for me.
what stuck with me is that dusk built a shield/unshield function so you can move value between the two models yourself. that's when it stopped feeling like public chain vs private chain and started feeling like one settlement layer where visibility is a setting, not an architecture choice.
it's not free, though. phoenix means scanning for your own notes and generating proofs locally, more overhead than moonlight's plain account read.
which side would you actually trust more with your own funds?
#dusk $DUSK #Dusk
@Dusk_Foundation
$PORTAL $SKYAI