Dusk's system evolves into a standardized three-layer architecture, reducing integration costs and timelines while maintaining the privacy and regulatory compliance advantages that distinguish the network. The new architecture includes a Data Consensus/Availability/Settlement layer (DuskDS) beneath the EVM execution layer (DuskEVM) and an upcoming Privacy layer (DuskVM).
Why this change?
It accelerates the deployment of applications;
Integrations with wallets, bridges, exchanges, and service providers have become faster thanks to standard Ethereum tools;
Current decentralized EVM applications are being migrated with minimal code changes, eliminating the need for the custom work that was previously required for the original Dusk;
The codebase becomes smaller, less expensive to maintain, and inherits the proven scalability of EVM from day one.
A single DUSK token feeds all three layers, and a native bridge managed by a validator transfers value between them without the need for wrapped assets or custodians. Since the NPEX licenses for the multi-party trading platform (MTF) and the electronic trading services platform (ECSP) and the broker apply to the entire infrastructure, institutions can issue, trade, and settle real-world assets under a single regulatory umbrella, accelerating the deployment of compliant decentralized finance in the market.
Multi-layer architecture
The multi-layer architecture is verified by integrating EIP-4844 (Proto-Danksharding) into Rusk, implementing the Dusk node, in addition to adding a port for Optimism as an EVM execution layer to stabilize on the Dusk ledger. This provides the following advantages:
DuskDS: Data and Settlement Layer
This system takes responsibility for consensus, storage, data availability, the native bridge, and settlement. A MIPS processor-backed pre-validation system on a DuskDS node (i.e., Rusk) checks state transitions before they reach the chain, so there is no 7-day waiting period as is the case with Optimism.