#dusk $DUSK @Dusk
I was looking through DuskDS transactions and one thing genuinely made me stop, DUSK doesn’t have to move through the same transaction model every time.
That sounds like a technical detail, but I think it says a lot about what @dusk is trying to build.
DuskDS uses the Transfer contract with two models. Moonlight is account-based and public. Phoenix is UTXO-based and shielded. Both can transfer DUSK, pay gas, and serve as an entry point for contract execution. Same network. Same asset. Very different assumptions about what should be visible.
Personally, that makes more sense to me than treating privacy like an on/off feature for an entire blockchain. Some activity benefits from being public and easy to inspect. Other transactions may contain information that simply doesn’t need to be exposed broadly. $DUSK gives both paths at the transaction layer.
But there’s a catch people may overlook. Choice only helps when users and developers understand what they’re choosing. Using Moonlight first and thinking about confidentiality later doesn’t undo information already made public.
That’s the part I’m watching with @dusk.
The technology can provide two transaction models. Making the right one feel obvious at the right moment is a different challenge.
I was looking through DuskDS transactions and one thing genuinely made me stop, DUSK doesn’t have to move through the same transaction model every time.
That sounds like a technical detail, but I think it says a lot about what @dusk is trying to build.
DuskDS uses the Transfer contract with two models. Moonlight is account-based and public. Phoenix is UTXO-based and shielded. Both can transfer DUSK, pay gas, and serve as an entry point for contract execution. Same network. Same asset. Very different assumptions about what should be visible.
Personally, that makes more sense to me than treating privacy like an on/off feature for an entire blockchain. Some activity benefits from being public and easy to inspect. Other transactions may contain information that simply doesn’t need to be exposed broadly. $DUSK gives both paths at the transaction layer.
But there’s a catch people may overlook. Choice only helps when users and developers understand what they’re choosing. Using Moonlight first and thinking about confidentiality later doesn’t undo information already made public.
That’s the part I’m watching with @dusk.
The technology can provide two transaction models. Making the right one feel obvious at the right moment is a different challenge.