kyc

#dusk is the privacy blockchain for regulated finance.

It lets you launch and use markets where:

Institutions can meet real regulatory requirements on‑chainUsers get confidential balances and transfers instead of full public exposureDevelopers build with familiar EVM tools plus native privacy and compliance primitives

Dusk combines:

Zero‑knowledge technology for confidentialityOn‑chain compliance for MiCA / MiFID II / DLT Pilot Regime / GDPR‑style regimesSuccinct Attestation, a PoS consensus protocol for fast, final settlementA 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 complianceCounterparty privacyExecution 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 RWAsIdentity and permissioning primitives that let you differentiate between public and restricted flowsOn‑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, andShielded 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 ratifiedNo user‑facing reorgs in normal operationDesigned 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 modelDuskEVM – an Ethereum‑compatible execution layer where DUSK is the native gas tokenNative 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 rulesOn‑chain corporate actions and transparent yet privacy‑respecting cap tables

Institutional DeFi

Lending, AMMs, and structured products that must enforce KYC/AMLSeparation of public market signals from private position details

Payment & settlement rails

Confidential payments between institutionsDelivery‑versus‑payment (DvP) settlement of tokenized assets

Self‑sovereign identity & access control

Permissioned venues where access is controlled via verifiable credentialsCompliance checks enforced in smart contracts instead of manual back‑office processes

For more inspiration, see Dusk’s use cases and Additional Resources.

Architecture at a glance

Here’s how the main components fit together:

ComponentRole in the systemLearn moreDuskDSSettlement, consensus, data availability, and native transaction modelCore ComponentsDuskEVMEVM execution environment where DUSK is the gas tokenDeploy on DuskEVMRuskReference node implementation that runs Succinct AttestationRun a nodeCitadelIdentity & access primitives for compliant, permissioned flowsCore Components

If you want a deeper technical dive, start with Cryptography or the Dusk Whitepaper.

Start building on Dusk

Choose how you want to get involved:

Use DuskSet up the Dusk Web Wallet and start interacting with the network.

Stake DUSKSecure the network as a staker and earn protocol rewards.

Join the CommunityGet support, share ideas, and stay up to date with Dusk on#Discord.

Uno dei portafogli decentralizzati più popolari, Trust Wallet, ha annunciato l'implementazione di misure di verifica dell'identità (KYC) per determinate funzionalità. Questa decisione è stata una diretta conseguenza di un significativo aumento delle false dichiarazioni da parte degli utenti, che affermavano di essere stati vittime di furto di fondi, mentre in realtà si erano comportati in modo negligente con le proprie chiavi private o erano stati oggetto di attacchi di phishing.

📅 22 ottobre | Canada
Il governo canadese ha appena inviato un avvertimento brutale all'ecosistema crypto: Cryptomus, una delle piattaforme di scambio più attive del paese, è stata sanzionata con una multa record per non aver rispettato le normative sul riciclaggio di denaro (AML) e sulla verifica dell'identità (KYC). Il colpo—considerato il più severo nella storia del paese per uno scambio digitale—chiarisce che il Canada non tollererà lacune normative o negligenza nella supervisione delle transazioni crypto.

Guarda, abbiamo sempre associato la blockchain con un accesso completo per tutti. Se hai un portafoglio, puoi partecipare ovunque. Nessuno chiede chi sei, quanti anni hai o da dove vieni. Ma non appena la crittografia ha cominciato a scontrarsi con il mondo reale, sono emerse domande scomode: sei sicuro di essere un adulto? Non vieni da un paese soggetto a sanzioni? Sei persino umano?
E qual è il risultato? Tutti hanno seguito il percorso standard: KYC, scansioni di passaporti, backend fragili e tonnellate di dati utente che nessuno vuole conservare, ma che tutti devono per qualche motivo. Di conseguenza, ogni progetto Web3 che ha solo bisogno di controllare "se questa persona può venire qui" è costretto a reinventare una bicicletta con ruote quadrate.