I was reading through Dusk docs today and something stopped me. Most blockchains give you one transaction model. Transparent. Everything visible. That's it.
Dusk gives you two.
Moonlight for public account flows. Phoenix for confidential shielded transfers. Same network. Same consensus. Same settlement layer. But you choose which mode fits the transaction.
That's such a simple idea, but it changes everything about how you'd build financial applications. A treasury payment that needs to be on the record? Moonlight. A position transfer between your own accounts that shouldn't broadcast your portfolio? Phoenix. Both on the same chain, not two chains pretending to be one.
What got my attention even more was the settlement piece. Succinct Attestation — Dusk's consensus protocol — is built around deterministic finality. Once a block is ratified, it's final. No user-facing reorgs. No "wait for six confirmations to be safe." For financial markets, that matters more than speed. You need to know a settlement is actually settled.
I keep thinking about how these pieces fit together. Two transaction models for privacy where needed. Deterministic finality for settlement confidence. Delivery-versus-payment built in, so asset and payment move together atomically. This isn't a general-purpose chain with finance features bolted on. It feels like finance infrastructure that happens to be a blockchain.
I'm still working through what this means in practice. Can institutions actually use both transaction models in the same workflow? Does regulatory reporting work differently for Moonlight vs Phoenix? These feel like the right questions to be asking.
Would you want two transaction modes in the same chain, or is that added complexity for most users?
#dusk $DUSK @Dusk
Dusk gives you two.
Moonlight for public account flows. Phoenix for confidential shielded transfers. Same network. Same consensus. Same settlement layer. But you choose which mode fits the transaction.
That's such a simple idea, but it changes everything about how you'd build financial applications. A treasury payment that needs to be on the record? Moonlight. A position transfer between your own accounts that shouldn't broadcast your portfolio? Phoenix. Both on the same chain, not two chains pretending to be one.
What got my attention even more was the settlement piece. Succinct Attestation — Dusk's consensus protocol — is built around deterministic finality. Once a block is ratified, it's final. No user-facing reorgs. No "wait for six confirmations to be safe." For financial markets, that matters more than speed. You need to know a settlement is actually settled.
I keep thinking about how these pieces fit together. Two transaction models for privacy where needed. Deterministic finality for settlement confidence. Delivery-versus-payment built in, so asset and payment move together atomically. This isn't a general-purpose chain with finance features bolted on. It feels like finance infrastructure that happens to be a blockchain.
I'm still working through what this means in practice. Can institutions actually use both transaction models in the same workflow? Does regulatory reporting work differently for Moonlight vs Phoenix? These feel like the right questions to be asking.
Would you want two transaction modes in the same chain, or is that added complexity for most users?
#dusk $DUSK @Dusk