SOLIDITY OR PRIVACY?

DuskEVM just gave developers a choice.

Use Solidity on DuskEVM (Ethereum-compatible execution layer).

Or use Rust/WASM on DuskVM (privacy-first, Dusk L1 execution).

This matters more than it looks.

On traditional Ethereum: Everyone uses Solidity. It's the default. No choice.

On Dusk: You can go two paths.

Path 1 (DuskEVM): Familiar. Solidity. Hardhat, Foundry, ethers, viem. Existing Ethereum apps port in minutes. Settles on Dusk L1 (DuskDS). Fast. Comfortable.

Path 2 (DuskVM): Rust/WASM. Privacy-native. Integrate directly with Dusk's privacy layer (Hedger). Access transaction models designed for compliance. More work. Better privacy.

Here's what concerns me:

Will Solidity's gravity (familiarity, speed, existing libraries) pull all developers to DuskEVM?

And if so, do most applications ever activate the privacy layer (Hedger)?

Or is DuskEVM just "Arbitrum with better settlement" (fast, but not actually using Dusk's privacy?

The distinction matters because it determines if Dusk becomes:
A) Infrastructure for regulated finance (privacy + compliance)
B) Just another EVM rollup (faster, but privacy is optional)

POLL: Which execution environment will developers choose?

A) DuskEVM (Solidity, familiar, easy) - 70%+ will go here
B) DuskVM (Rust, privacy-native, harder) - Only for specialized apps
C) Hybrid (They'll use both depending on needs)
D) It depends on what Dusk prioritizes in marketing

Which are you building on? And will you actually use the privacy layer?

@Dusk $DUSK #dusk