Core Components
The Dusk network uses a modular architecture built for regulated finance: privacy where it is needed, transparency where it is useful, and deterministic settlement where market workflows require it.
At a high level:
| Component | Role | Where to go next |
|---|---|---|
| DuskDS | Settlement and data-availability foundation: consensus, finality, and Dusk transaction models | Transaction Models, Run a node |
| Rusk | The Rust node implementation for the Dusk L1 | HTTP API, GitHub |
| DuskVM | Rust/WASM smart-contract execution directly on the Dusk L1 | DuskVM deep dive, DuskVM contracts |
| DuskEVM | OP Stack-based EVM execution settled through DuskDS | DuskEVM overview, DuskEVM quickstart |
| Citadel | Identity and access primitives (selective disclosure) | Digital Identity protocol |
DuskDS
Section titled “DuskDS”DuskDS is the Dusk Data Availability and Settlement layer. It is the consensus, finality, and data-availability foundation of the Dusk L1, and includes the Moonlight and Phoenix transaction models used to transfer DUSK and pay for execution.
DuskDS is not a name for the complete Dusk network. The Dusk L1 also includes DuskVM smart-contract execution, while DuskEVM is an EVM-compatible execution layer that settles and publishes data through DuskDS.
DuskDS supports two transaction models: Moonlight for transparent public accounts and Phoenix for confidential shielded transfers. See: Transaction Models on Dusk.
Rusk is the Rust node implementation for the Dusk L1. It runs DuskDS consensus, maintains chain state, executes DuskVM contracts, and exposes the HTTP API and RUES event system used by wallets, indexers, and integrators.
Succinct Attestation
Section titled “Succinct Attestation”Succinct Attestation (SA) is DuskDS’s permissionless, committee-based proof-of-stake consensus protocol. It uses randomly selected provisioners to propose, validate, and ratify blocks, providing fast, deterministic finality suitable for financial markets.
At a high level, each round goes through three steps:
- Proposal – a provisioner creates and broadcasts a candidate block.
- Validation – a committee checks the block’s validity.
- Ratification – another committee confirms the validation outcome and finalizes the block.
For the full protocol specification and security analysis (including committee selection, finality, and slashing), see Section 3 “Consensus mechanism” of the Dusk Whitepaper (2024).
Transactions in DuskDS
Section titled “Transactions in DuskDS”Transactions in DuskDS are managed by the Transfer contract, which supports both public and shielded transfers.
Moonlight is account-based and public. Phoenix is UTXO-based and shielded. Both are used to transfer DUSK, pay gas, and act as the entry point for contract execution.
Execution environments
Section titled “Execution environments”Dusk provides two smart-contract environments at different layers of the architecture.
DuskVM
Section titled “DuskVM”DuskVM is the Wasmtime-based execution environment for Rust/WASM contracts that run directly on the Dusk L1. It is the path for contracts that need direct access to L1 assets, transaction models, privacy, or zero-knowledge capabilities.
DuskEVM
Section titled “DuskEVM”DuskEVM is an OP Stack-based EVM-equivalent execution environment. It lets you deploy Solidity contracts using standard EVM tooling while using DuskDS for settlement and data availability.
Network Layer: Kadcast
Section titled “Network Layer: Kadcast”Kadcast is Dusk’s P2P networking layer. It uses a structured overlay (instead of random gossip) to reduce bandwidth and improve latency predictability.
Genesis Contracts
Section titled “Genesis Contracts”Dusk ships with two genesis contracts:
- Stake: tracks provisioners, stakes, rewards, and validator set management. (source)
- Transfer: transfers
DUSKand is the entry point for transaction execution and gas payment. (source)
For node operators: Run a provisioner node.
Applications
Section titled “Applications”On top of the base protocol, Dusk supports application-layer protocols and tools for regulated markets.
Dusk Trade
Section titled “Dusk Trade”Dusk Trade is the application layer for tokenized financial assets on Dusk. It is being built around real market workflows: investor onboarding, wallet binding, controlled transfers, payment coordination, and compliant settlement.
Zedger / Hedger
Section titled “Zedger / Hedger”Zedger and Hedger are protocols for issuing and managing regulated assets with built-in compliance and privacy constraints.
- Zedger uses DuskVM contracts on the Dusk L1.
- Hedger runs on DuskEVM to offer an EVM-first developer experience.
Citadel
Section titled “Citadel”
Citadel is Dusk’s identity and access layer. It supports selective disclosure so users can prove attributes (e.g. residency, age bracket, accreditation) without revealing more than necessary.