DuskEVM
DuskEVM brings Solidity, EVM wallets, and Ethereum tooling to Dusk. Existing EVM applications can target DuskEVM with familiar contracts and workflows while using DUSK for gas and DuskDS for settlement and data availability.
Why DuskEVM
Section titled “Why DuskEVM”- Start with the EVM stack. Use Solidity or Vyper with Foundry, Hardhat, viem, ethers, and standard EVM wallets.
- Use DUSK throughout. DUSK pays for execution and moves between the Dusk L1 and DuskEVM through the bridge.
- Settle on DuskDS. Batches and state commitments anchor DuskEVM activity to Dusk’s consensus and data-availability layer.
- Reach the wider Dusk stack. EVM applications can connect to Dusk L1 assets, infrastructure, and privacy-oriented workflows as those integrations require.
How it fits
Section titled “How it fits”| Component | Role |
|---|---|
| DuskDS | Consensus, settlement, and data availability |
| DuskEVM | Ethereum-compatible smart contract execution |
| Bridge | Moves DUSK and messages between both environments |
A DuskEVM transaction follows a rollup lifecycle:
- The transaction is submitted to the DuskEVM sequencer.
- The execution layer includes it in an L2 block.
- The batcher publishes the transaction data to DuskDS.
- State commitments and fault proofs connect the resulting state to DuskDS settlement.
Transaction inclusion is fast, but inclusion and settlement are different stages. Applications that move value between DuskEVM and the Dusk L1 should use protocol or wallet status rather than infer finality from elapsed time.
Choose an execution environment
Section titled “Choose an execution environment”Choose DuskEVM for Solidity applications, EVM wallets, existing Ethereum libraries, and EVM infrastructure.
Choose DuskVM for Rust/WASM contracts that should execute directly on the Dusk L1 or integrate closely with its transaction models, protocol assets, privacy, or zero-knowledge capabilities. See the DuskVM overview and DuskVM contract guide.