The thing I keep noticing with @Dusk_Foundation is that the flexibility between Moonlight and Phoenix is almost too easy to overlook.
Moonlight gives you the familiar account-style flow: visible address, visible balance, straightforward transfer. Phoenix works around notes and zero-knowledge proofs instead. On paper, having both on the same chain sounds great. In practice, the little friction is deciding which lane you actually want to use.
I was poking around Dusk’s transaction activity and one explorer snapshot showed 160 Moonlight transactions versus just 14 shielded transactions over 24 hours. That’s roughly 10–11x more public activity. It doesn’t prove users dislike Phoenix, obviously, but it does make me wonder how often people actually need the extra privacy once the easy public route is sitting there.
The slightly weird part is that Dusk lets value move between the two models, so it’s not really an either/or choice. You can convert between Moonlight balances and Phoenix notes. Technically that’s flexible. From a user perspective, though, it can feel like keeping track of the same DUSK through two different mental models.
I’d probably reach for Moonlight first just because the state is easier to reason about at a glance. Phoenix is the lane I’d use when the transaction itself needs more discretion, not because it’s somehow the “better” default…
$DUSK
#dusk
$AT $GRVT
Moonlight gives you the familiar account-style flow: visible address, visible balance, straightforward transfer. Phoenix works around notes and zero-knowledge proofs instead. On paper, having both on the same chain sounds great. In practice, the little friction is deciding which lane you actually want to use.
I was poking around Dusk’s transaction activity and one explorer snapshot showed 160 Moonlight transactions versus just 14 shielded transactions over 24 hours. That’s roughly 10–11x more public activity. It doesn’t prove users dislike Phoenix, obviously, but it does make me wonder how often people actually need the extra privacy once the easy public route is sitting there.
The slightly weird part is that Dusk lets value move between the two models, so it’s not really an either/or choice. You can convert between Moonlight balances and Phoenix notes. Technically that’s flexible. From a user perspective, though, it can feel like keeping track of the same DUSK through two different mental models.
I’d probably reach for Moonlight first just because the state is easier to reason about at a glance. Phoenix is the lane I’d use when the transaction itself needs more discretion, not because it’s somehow the “better” default…
$DUSK
#dusk
$AT $GRVT