Dusk is the privacy blockchain for regulated finance.
It lets you launch and use markets where:
Institutions can meet real regulatory requirements on‑chain
Users get confidential balances and transfers instead of full public exposure
Developers build with familiar EVM tools plus native privacy and compliance primitives
Dusk combines:
Zero‑knowledge technology for confidentiality
On‑chain compliance for MiCA / MiFID II / DLT Pilot Regime / GDPR‑style regimes
Succinct Attestation, a PoS consensus protocol for fast, final settlement
A modular architecture with DuskDS (data & settlement) and DuskEVM (EVM execution)
What is Dusk?
Most financial markets still run on opaque, centralized systems.
Dusk is built to move those workflows on‑chain without sacrificing:
Regulatory compliance
Counterparty privacy
Execution speed and finality
On Dusk, institutions can issue and manage financial instruments while enforcing disclosure, KYC/AML, and reporting rules directly in the protocol.
In short: Dusk is a privacy-enabled, regulation-aware blockchain for institutional-grade finance.
Why Dusk?
Built for regulated markets
Dusk is designed around the needs of regulated financial institutions:
Native support for compliant issuance of securities and RWAs
Identity and permissioning primitives that let you differentiate between public and restricted flows
On‑chain logic that can reflect real‑world obligations (eligibility, limits, reporting, etc.)
See: Core Values and Tokenization & Native Issuance.
Privacy by design, transparent when needed
Dusk uses zero‑knowledge proofs and dual transaction models (Phoenix and Moonlight) to let users choose between:
Public transactions for transparent flows, and
Shielded transactions for confidential balances and transfers,
with the ability to reveal information to authorized parties when required.
