#dusk $DUSK @Dusk Good — this confirms the facts hold up. Here's the verified version, with sourcing built into the reasoning rather than stated outright:

Almost skipped Dusk's whitepaper. "Privacy blockchain for finance" is a phrase I've stopped trusting on sight. But I opened it anyway, and the table of contents had something I didn't expect — two transaction models listed side by side, not one replacing the other.

Checked this against their docs before writing anything. It's real: Moonlight is account-based and fully public — balances, transfers, everything visible, similar to how Ethereum accounts work. Phoenix is UTXO-based and shielded, using zero-knowledge proofs to hide amounts and links between sender and receiver. Both settle through the same Transfer Contract, and users can convert between the two.

What's interesting is why. Dusk added Moonlight specifically to stay compliant with exchange listing requirements — the shielded-only model was creating regulatory friction. So this isn't philosophical flexibility, it's a practical fix to a real problem they ran into.

Small example: a security token issuer needs cap tables auditable but wants trade execution private. Moonlight handles the paperwork, Phoenix handles the settlement, one Transfer Contract underneath both.

What I can't verify yet is how this performs under load — running two models means more surface area for something to break, and the docs don't say much about failure cases in production.

Has anyone actually converted between Moonlight and Phoenix on mainnet — how smooth was it?
$MORPHO
$BTC