Privacy and transparency don’t always have to compete. #dusk approaches this balance with two transaction models: Phoenix and Moonlight.
Phoenix is designed for private transactions. It focuses on protecting sensitive financial details, helping users transact without unnecessarily exposing information on-chain. This makes it especially interesting for applications where confidentiality matters.
Moonlight, on the other hand, takes a more transparent approach. Transactions remain visible, making it easier to verify activity and maintain public accountability.
The interesting part is that Dusk doesn’t force every use case into one model. Instead, it gives developers a choice based on what their application actually needs.
For regulated finance, that flexibility can be important. Some information needs to remain private, while other activity may need to be auditable and transparent.
Dusk’s approach is ultimately about giving privacy and compliance room to work together not treating them as opposites.
@Dusk_Foundation
$DUSK
$ACE $CYS
Phoenix is designed for private transactions. It focuses on protecting sensitive financial details, helping users transact without unnecessarily exposing information on-chain. This makes it especially interesting for applications where confidentiality matters.
Moonlight, on the other hand, takes a more transparent approach. Transactions remain visible, making it easier to verify activity and maintain public accountability.
The interesting part is that Dusk doesn’t force every use case into one model. Instead, it gives developers a choice based on what their application actually needs.
For regulated finance, that flexibility can be important. Some information needs to remain private, while other activity may need to be auditable and transparent.
Dusk’s approach is ultimately about giving privacy and compliance room to work together not treating them as opposites.
@Dusk_Foundation
$DUSK
$ACE $CYS