#dusk $DUSK @Dusk
Dusk didn’t settle for one transaction model. It runs two.
Moonlight stays account-based—clean balances, familiar smart-contract logic, the path most developers already know. Phoenix goes full UTXO: consume, create, leave less continuous history for the world to follow. One structure for transparent, regulated flows. The other built for privacy-oriented moves that need tighter control over what leaks.
That split is deliberate. Force everything through a single model and you either blunt the privacy tools or twist the transparent side into something awkward. Keeping both gives real flexibility. But every extra model extracts a price: two validity rules, two mental maps, two surfaces wallets and explorers must support. Developers switch contexts. Users pause and ask which kind of transaction they’re looking at. Complexity compounds quietly.
So is the dual architecture worth it? Only if Phoenix delivers capabilities Moonlight simply cannot, and only if those capabilities get used enough to justify the permanent increase in surface area and cognitive load. The design feels intentional. Whether it stays an advantage or becomes dead weight will be decided by what people actually build on it—not by how clever the original choice looked.$DUSK 👇
Dusk didn’t settle for one transaction model. It runs two.
Moonlight stays account-based—clean balances, familiar smart-contract logic, the path most developers already know. Phoenix goes full UTXO: consume, create, leave less continuous history for the world to follow. One structure for transparent, regulated flows. The other built for privacy-oriented moves that need tighter control over what leaks.
That split is deliberate. Force everything through a single model and you either blunt the privacy tools or twist the transparent side into something awkward. Keeping both gives real flexibility. But every extra model extracts a price: two validity rules, two mental maps, two surfaces wallets and explorers must support. Developers switch contexts. Users pause and ask which kind of transaction they’re looking at. Complexity compounds quietly.
So is the dual architecture worth it? Only if Phoenix delivers capabilities Moonlight simply cannot, and only if those capabilities get used enough to justify the permanent increase in surface area and cognitive load. The design feels intentional. Whether it stays an advantage or becomes dead weight will be decided by what people actually build on it—not by how clever the original choice looked.$DUSK 👇