Moonlight vs Phoenix: Understanding Dusk's Two Transaction Models
The thing that actually made me pause: pulling 24h transaction data off duskexplorer.com, Moonlight (the transparent, account-based model) outnumbered Phoenix (the shielded model) 231 to 21 over 90% of activity. For a chain whose whole pitch is privacy-preserving finance, that's a lopsided split.
Context matters here. On August 16, Dusk's team flagged suspicious activity on a bridge-operations wallet, paused bridge services, recycled the affected addresses, and added a recipient blocklist to the Web Wallet (per their official incident notice). Bridge activity naturally routes through Moonlight-adjacent, auditable paths easier to monitor, easier to coordinate with exchanges like Binance when something needs tracing. That's a plausible partial explanation for why transparent transactions are dominating right now.
What this tells us: whatever else is happening, users (or at least the volume-driving activity) are currently favoring visibility over privacy possibly compliance-related, possibly bridge-recovery related, possibly just default wallet behavior.
What I can't confirm: whether the Moonlight skew predates the incident or is a direct reaction to it I only have one snapshot, not a week-over-week trend, and duskexplorer's model split for contract calls (89 of them) isn't broken out separately.
Does anyone have a longer time series on the Moonlight/Phoenix ratio pre- and post-August 16?
@Dusk $DUSK #dusk
The thing that actually made me pause: pulling 24h transaction data off duskexplorer.com, Moonlight (the transparent, account-based model) outnumbered Phoenix (the shielded model) 231 to 21 over 90% of activity. For a chain whose whole pitch is privacy-preserving finance, that's a lopsided split.
Context matters here. On August 16, Dusk's team flagged suspicious activity on a bridge-operations wallet, paused bridge services, recycled the affected addresses, and added a recipient blocklist to the Web Wallet (per their official incident notice). Bridge activity naturally routes through Moonlight-adjacent, auditable paths easier to monitor, easier to coordinate with exchanges like Binance when something needs tracing. That's a plausible partial explanation for why transparent transactions are dominating right now.
What this tells us: whatever else is happening, users (or at least the volume-driving activity) are currently favoring visibility over privacy possibly compliance-related, possibly bridge-recovery related, possibly just default wallet behavior.
What I can't confirm: whether the Moonlight skew predates the incident or is a direct reaction to it I only have one snapshot, not a week-over-week trend, and duskexplorer's model split for contract calls (89 of them) isn't broken out separately.
Does anyone have a longer time series on the Moonlight/Phoenix ratio pre- and post-August 16?
@Dusk $DUSK #dusk
