Dusk is no longer only a narrative about privacy focused and regulated finance. The ecosystem now has clear, testable components that show how the stack is meant to work in real conditions. At the center of this is the relationship between DuskEVM as the execution layer and DuskDS as the settlement layer, with $DUSK acting as the native asset across the system.
The DuskEVM public testnet is live. This introduces an EVM compatible execution environment where developers can deploy and interact with smart contracts. These transactions do not live in isolation. They settle back to DuskDS, which is designed to provide finality and security. Alongside this, DuskDS has received important upgrades through Rusk and a DuskVM patch, focused on improving robustness and preparing the chain for increased execution activity.
DuskDS functions as the settlement and data layer. Its role is to remain stable, predictable, and reliable. DuskEVM sits above it as the execution layer, handling application logic and smart contracts. When activity happens on DuskEVM, settlement is finalized on DuskDS. This separation allows Dusk to evolve its execution environment without compromising the guarantees of the settlement layer.
Regulated financial use cases such as tokenized assets and compliant DeFi require more than speed. They require confidentiality for sensitive flows and auditability when oversight is needed. A modular structure like Dusk’s allows privacy aware execution while keeping settlement clear and verifiable. This is where Dusk differentiates itself from fully transparent chains and fully opaque systems.
Builders can bridge testnet $DUSK from DuskDS to DuskEVM using the Web Wallet and use it as gas on the execution layer. This allows real testing of contracts, transactions, and workflows inside the Dusk environment rather than relying on theory or future promises.
The strongest signal from here will be consistent activity on DuskEVM. More contract deployments, more testnet usage, and more experimentation with privacy aware financial logic will show whether the stack is ready for broader adoption.
Do you think the first strong use case on DuskEVM will come from compliant DeFi, tokenized assets, or private settlement flows for institutions?
