I’m looking at Dusk as infrastructure rather than an app chain. It’s designed around the idea that markets need confidentiality and compliance at the same time. At the base, DuskDS handles consensus and settlement using a proof-of-stake design called SBA, built on a ‘proof of blind bid’ style leader selection that can keep validators less exposed. Smart contracts can run in more than one way: DuskVM executes WASM contracts, while DuskEVM is EVM-equivalent so teams can reuse Ethereum contracts and tooling. In practice, you use DUSK for fees and staking, then interact through wallets and apps that expose only what you need—confidential details for users, and audit views when a regulator or counterparty must verify. Since mainnet went live, they’ve been adding connective pieces like a two-way bridge that moves native DUSK to BEP20 on BSC and back. On the regulated side, they’re building rails with partners: NPEX for an on-chain exchange model and Quantoz Payments to bring EURQ, a MiCA-compliant digital euro (an EMT). The long-term goal is a stack where institutions can issue, trade, clear, and settle RWAs on-chain, with privacy by default but accountability on demand. Their modular stack lets execution layers plug in without changing consensus.
