#dusk $DUSK @Dusk
Been digging into Dusk’s Moonlight vs Phoenix setup, and honestly, the two-model approach is what caught my attention.
Moonlight is transparent and account-based, pretty close to Ethereum.
Phoenix goes the other way — notes, Merkle trees and ZK proofs keep transaction details private while nullifiers stop double spending.
What I find interesting is that Dusk didn’t force users into one model.
Transparent when compliance needs it, private when it doesn’t.
There’s definitely more complexity here, but for regulated finance, that tradeoff might actually make sense.
Still figuring out how useful this becomes in practice.
$ACE
$BTW
Which Dusk model would you use?
Been digging into Dusk’s Moonlight vs Phoenix setup, and honestly, the two-model approach is what caught my attention.
Moonlight is transparent and account-based, pretty close to Ethereum.
Phoenix goes the other way — notes, Merkle trees and ZK proofs keep transaction details private while nullifiers stop double spending.
What I find interesting is that Dusk didn’t force users into one model.
Transparent when compliance needs it, private when it doesn’t.
There’s definitely more complexity here, but for regulated finance, that tradeoff might actually make sense.
Still figuring out how useful this becomes in practice.
$ACE
$BTW
Which Dusk model would you use?
Moonlight — Transparent
83%
Phoenix — Private
0%
Both — Depends
0%
Neither — Too complex
17%
6 дауыс • Дауыс беру жабық