I went back through Dusk's core components page last night, trying to map out where Dusk Trade actually sits relative to everything underneath it, because I'd been treating it as just another app without thinking about what it's built on.
At the bottom is DuskDS, handling consensus, settlement, data availability, and finality, running on Rusk as the node implementation, Succinct Attestation as the consensus mechanism, and Kadcast for peer to peer networking. Above that sit the two execution paths, DuskEVM for Solidity and standard EVM tooling, DuskVM for native Rust and WASM contracts, both settling back down to DuskDS. Then there's Citadel handling identity, credentials, and selective disclosure, and Dusk Connect handling wallet discovery and account connection. Dusk Trade sits at the very top, the actual product layer, turning all of that into something a user experiences as onboarding, buying, selling, and settlement.
What struck me is how much has to be coordinated correctly just for Dusk Trade to function as one clean workflow. Identity from Citadel, wallet state from Dusk Connect, execution from EVM or VM, and finality from DuskDS all have to line up behind a single trade action.
Is that tight coordination actually the hard engineering problem here, harder than any single layer on its own?
#dusk $DUSK @Dusk $BTW $HEMI
At the bottom is DuskDS, handling consensus, settlement, data availability, and finality, running on Rusk as the node implementation, Succinct Attestation as the consensus mechanism, and Kadcast for peer to peer networking. Above that sit the two execution paths, DuskEVM for Solidity and standard EVM tooling, DuskVM for native Rust and WASM contracts, both settling back down to DuskDS. Then there's Citadel handling identity, credentials, and selective disclosure, and Dusk Connect handling wallet discovery and account connection. Dusk Trade sits at the very top, the actual product layer, turning all of that into something a user experiences as onboarding, buying, selling, and settlement.
What struck me is how much has to be coordinated correctly just for Dusk Trade to function as one clean workflow. Identity from Citadel, wallet state from Dusk Connect, execution from EVM or VM, and finality from DuskDS all have to line up behind a single trade action.
Is that tight coordination actually the hard engineering problem here, harder than any single layer on its own?
#dusk $DUSK @Dusk $BTW $HEMI