Moonlight vs Phoenix: Dusk’s Two Transaction Models
The interesting part isn’t simply public vs private. The two models are built around different assumptions about what a transaction should reveal.
Moonlight is account-based and transparent: balances, sender, receiver and amount can be inspected. Phoenix uses shielded notes and zero-knowledge proofs, so the network can verify validity without exposing the underlying transfer details.
The recent explorer snapshot around block #4,178,605 shows Dusk producing roughly 8,635 blocks/day, while the latest block itself carried 0 transactions. The explorer also showed only 236 transactions over 24h at that snapshot. That gap between block production and transaction activity is more interesting to me than the raw TPS narrative.
It suggests the network is currently doing far more consensus work than user-transfer work.
My uncertainty is whether that changes materially as Dusk’s regulated-asset applications mature.
@Dusk_Foundation $DUSK #dusk
The interesting part isn’t simply public vs private. The two models are built around different assumptions about what a transaction should reveal.
Moonlight is account-based and transparent: balances, sender, receiver and amount can be inspected. Phoenix uses shielded notes and zero-knowledge proofs, so the network can verify validity without exposing the underlying transfer details.
The recent explorer snapshot around block #4,178,605 shows Dusk producing roughly 8,635 blocks/day, while the latest block itself carried 0 transactions. The explorer also showed only 236 transactions over 24h at that snapshot. That gap between block production and transaction activity is more interesting to me than the raw TPS narrative.
It suggests the network is currently doing far more consensus work than user-transfer work.
My uncertainty is whether that changes materially as Dusk’s regulated-asset applications mature.
@Dusk_Foundation $DUSK #dusk