One Network, Two Ways to Move Value

@Dusk_Foundation takes an interesting approach to transaction design by supporting two native models on DuskDS.

Moonlight uses public, account-based balances, making transaction details visible and suitable for flows where transparency is required. Phoenix takes the opposite approach, using shielded notes and zero-knowledge proofs to keep sensitive transfer details confidential.

The important part is that these are not separate networks. Both models settle through the same DuskDS infrastructure, while the Transfer Contract handles the corresponding transaction logic.

For financial applications, that flexibility matters. Some workflows need visibility for reporting or operational purposes, while others require stronger confidentiality.

Rather than choosing one model for every situation, Dusk provides different transaction paths within the same settlement layer.

$DUSK #dusk
$PORTAL
$AIO