When I re-examined Dusk, I thought I was only seeing a privacy-focused L1 with added EVM compatibility.

But what I found is that the real change is in the architecture.

Dusk is gradually separating application execution from financial settlement.

Now, DuskDS serves as the underlying settlement and data availability layer, while DuskEVM provides an EVM-equivalent environment based on OP Stack—so that Solidity and mainstream Ethereum tooling can enter Dusk. At the same time, DuskVM still preserves the native Rust/WASM path, supporting applications that need direct access to the L1, privacy, or ZK capabilities.

This has reshaped how I understand Dusk’s original positioning.

In the past, the core narrative was more like: privacy + compliance + financial assets.

Now the direction is much closer to: enabling regulated financial infrastructure to be compatible with the existing developer ecosystem.

This is important, because what institutions need is not just privacy technology.

They also need wallets, developer tools, liquidity, applications, settlement, and interoperability to work together.

Dusk now clearly targets tokenized assets and DeFi with DuskEVM, and Hedger brings privacy-related functionality into the EVM environment. Meanwhile, at the base layer, DuskDS still keeps the transaction model of Phoenix and Moonlight.

But there is also a reality that must be faced.

On January 16, 2026, Dusk experienced a security incident in which a bridged signed-wallet was compromised. Dusk stated that this was not a failure of the consensus layer or the core protocol. After that, the bridge architecture was redesigned, including signature isolation, event-handling isolation, stricter security boundaries, and reducing exposure of the hot wallet.

Subsequently, AEGIS discovered and addressed 39 security issues, including 7 severe ones related to the VM, serialization, Phoenix fee mechanisms, and BLS cryptography.

So what I’m really focused on now is no longer whether Dusk can “support EVM.”

Instead, it’s whether this modular architecture can truly turn EVM compatibility into real-world regulated financial activity.

Will DuskEVM ultimately become the key bridge connecting crypto-native liquidity with Dusk’s compliant settlement layer?#dusk $DUSK @Dusk