Dusk foundation
dusk mission is to unlock economic inclusion by bringing institution-level assets to anyone's wallet.
Dusk has the only privacy-first technology to bring classic finance and real-world assets on-chain.
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.
- problem dusk is solving
.institutional centric landscape
.Issuers only have access to fragmented liquidity
.Institutions must retain custody of users’ assets to ensure legitimate and compliant service transactions
.Classic users cannot access and compose all services.
.Crypto users do not have access to asset-backed tokens
- the solution
.user centric landscape
.Issuers are exposed to global, consolidated liquidity
.Institutions have access to instant clearance and settlement without custodianship liabilities
.There is no distinction between classic and crypto users;
.Everyone has access to all market sectors. Including crypto
dusk network
/01
Productized and profitable smart contracts
/02
Tokens governed by privacy-preserving smart contracts
/03
Compliant with global regulations and local legislation
/04
Instant settlement of transactions
Investors
.Cosimo
.XCosimo XRR2 Capital
.Blockwall ManagementBlockwall Management
.BitfinexBitfinex
- Businesses
Easily access financing, trade and automate via smart contracts, outsource costly processes.
- Institutions
Access instant clearance and settlement, use automated compliance, and reduce the fragmentation of liquidity.
- Users
Unprecedented access to diverse, institutional-level assets, directly from a wallet and retaining self-custody.
further more
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.
See: Cryptography and Transaction Models on Dusk.
Fast, final settlement
The Succinct Attestation consensus protocol is a proof‑of‑stake, committee‑based design:
Deterministic finality once a block is ratified
No user‑facing reorgs in normal operation
Designed for high throughput and low‑latency settlement suitable for markets
For the full consensus specification, see Section 3 “Consensus mechanism” of the Dusk Whitepaper (2024).
Modular & EVM-friendly
Dusk separates settlement from execution, making it easier to match the right environment to each use case:
DuskDS – consensus, data availability, settlement, and the privacy‑enabled transaction model
DuskEVM – an Ethereum‑compatible execution layer where DUSK is the native gas token
Native bridging between layers so assets can move where they’re most useful
See: Core Components and DuskEVM Developer Docs.
What can you build on Dusk?
Some example use cases Dusk was designed for:
Regulated digital securities
Tokenized equity, debt, or funds with embedded compliance rules
On‑chain corporate actions and transparent yet privacy‑respecting cap tables
Institutional DeFi
Lending, AMMs, and structured products that must enforce KYC/AML
Separation of public market signals from private position details
Payment & settlement rails
Confidential payments between institutions
Delivery‑versus‑payment (DvP) settlement of tokenized assets
Self‑sovereign identity & access control
Permissioned venues where access is controlled via verifiable credentials
Compliance checks enforced in smart contracts instead of manual back‑office processes
