#dusk $DUSK @Dusk Spent twenty minutes on Dusk's docs expecting the usual "privacy chain" boilerplate. Found something I didn't expect: a convert function that atomically swaps DUSK between a public account and a shielded one. Not a bridge. Not a wrapped token. Same protocol, one function call.

Here's why that caught me. Moonlight is the plain account model — balances visible, easy to audit, basically Ethereum-style. Phoenix is the UTXO side, shielded with ZK proofs, nullifiers, commitments. Amounts hidden, sender-receiver links broken. Two completely different data structures, living under one Transfer Contract.

Picture a treasury desk moving funds for payroll versus moving funds for an OTC settlement. Payroll can sit in Moonlight, fully visible for audit trails. The OTC leg shields into Phoenix so counterparties aren't broadcasting position size to the whole chain. Same wallet, same asset, different transaction type depending on what the situation needs.

Worth noting — Dusk also made Phoenix reveal the sender to the receiver by default now, specifically to stay compliant with EU rules. That's a deliberate concession, not a bug. Privacy-preserving, not anonymous.

What I haven't been able to pin down is usage split. Docs describe the mechanism well. They don't show me how much real volume runs through Phoenix versus Moonlight post-mainnet.

Has anyone actually pulled that split from the block explorer? Which model is seeing more real traffic right now?
$TUT
$ETH