$DUSK
I was comparing the transaction models in Dusk’s Core Components documentation when one detail corrected my earlier assumption.
Phoenix is not described as a privacy application sitting above Dusk.
It sits inside DuskDS.
The documentation confirms that DuskDS supports two models: Moonlight for transparent public accounts and Phoenix for shielded transfers.
Phoenix is UTXO-based, while both models can transfer DUSK, pay gas and enter contract execution.
That placement matters more than the usual “private transactions” description.
On a standard public account model, someone does not always need your name to learn something useful. Repeated transfers, changing balances and interactions with the same contracts can build a recognizable settlement pattern.
Phoenix changes the information available underneath that activity. A zero-knowledge proof can demonstrate that a valid output is being spent, while a nullifier prevents it from being spent again.
The network can verify the transaction without reproducing the same public account trail.
I initially wanted to describe that as private settlement for every asset on Dusk. The documents do not support that broad claim.
Phoenix specifically handles shielded DUSK flows. Privacy for regulated securities still depends on the application design, DuskVM contracts, identity rules and selective disclosure.
So the narrower conclusion is probably the stronger one: Phoenix protects the base movement entering settlement and execution. It does not make the whole financial workflow disappear.
#dusk @Dusk
I was comparing the transaction models in Dusk’s Core Components documentation when one detail corrected my earlier assumption.
Phoenix is not described as a privacy application sitting above Dusk.
It sits inside DuskDS.
The documentation confirms that DuskDS supports two models: Moonlight for transparent public accounts and Phoenix for shielded transfers.
Phoenix is UTXO-based, while both models can transfer DUSK, pay gas and enter contract execution.
That placement matters more than the usual “private transactions” description.
On a standard public account model, someone does not always need your name to learn something useful. Repeated transfers, changing balances and interactions with the same contracts can build a recognizable settlement pattern.
Phoenix changes the information available underneath that activity. A zero-knowledge proof can demonstrate that a valid output is being spent, while a nullifier prevents it from being spent again.
The network can verify the transaction without reproducing the same public account trail.
I initially wanted to describe that as private settlement for every asset on Dusk. The documents do not support that broad claim.
Phoenix specifically handles shielded DUSK flows. Privacy for regulated securities still depends on the application design, DuskVM contracts, identity rules and selective disclosure.
So the narrower conclusion is probably the stronger one: Phoenix protects the base movement entering settlement and execution. It does not make the whole financial workflow disappear.
#dusk @Dusk