What Is DuskEVM? Dusk's EVM-Equivalent Execution Layer
DuskEVM is Dusk's EVM-equivalent execution layer. It runs Solidity smart contracts with standard Ethereum tooling, uses DUSK for gas and settles on DuskDS, the consensus, settlement and data-availability layer of the Dusk Layer 1. Hedger, Dusk's privacy module, brings confidential balances and transfer amounts to applications on DuskEVM.
Many onchain applications are written for the EVM. DuskEVM lets EVM developers bring the contracts, wallets and libraries they already use to Dusk and connect them to confidential balances and transfer amounts, review by authorized parties and settlement on DuskDS.
How does DuskEVM work?
DuskEVM is built on the OP Stack and follows a rollup lifecycle. A transaction goes to the DuskEVM sequencer and the execution layer includes it in an L2 block. A batcher then publishes the transaction data to DuskDS, and state commitments and fault proofs tie the resulting state to DuskDS settlement.
Inclusion and settlement are separate stages. A transaction is included quickly, but applications that move value between DuskEVM and the Dusk L1 should read protocol or wallet status rather than infer finality from elapsed time.
Three components share the work:
| Component | Role |
|---|---|
| DuskEVM | Ethereum-compatible smart-contract execution |
| DuskDS | Consensus, settlement and data availability |
| Bridge | Moves DUSK and messages between the Dusk L1 and DuskEVM |
Builders write contracts in Solidity or Vyper and work with Foundry, Hardhat, viem, ethers and standard EVM wallets over the standard Ethereum JSON-RPC interface. DUSK pays for execution and moves between the Dusk L1 and DuskEVM through the bridge. The DuskEVM quickstart walks through deploying and verifying a first contract.
Dusk offers a second execution environment for different needs. DuskEVM suits Solidity applications, EVM wallets and existing Ethereum libraries. DuskVM runs Rust/WASM contracts directly on the Dusk L1, for contracts that need close access to its transaction models (Moonlight and Phoenix), protocol assets and zero-knowledge capabilities.
EVM compatibility lowers the cost of building. The regulated-finance fit comes from what DuskEVM connects to, with Hedger for confidential balances and transfer amounts with authorized auditing, and DuskDS for settlement. A Solidity team can start with standard contracts and add confidential flows through Hedger where its users need them. Dusk's Apps & Products page lists DuskEVM alongside DuskDS, the Dusk wallets and the developer tools.
Common questions about DuskEVM
Is DuskEVM a separate blockchain?
DuskEVM is an execution layer that publishes its data to DuskDS and settles there. The Dusk L1 is DuskDS plus DuskVM, and DuskEVM sits on top of it as the environment for EVM contracts.
What token pays for gas on DuskEVM?
DUSK. The same token pays for transactions on the Dusk L1 and moves between the two environments through the bridge.
Are DuskEVM transactions private?
A standard DuskEVM contract behaves like any EVM contract, with public state. Deploying a contract doesn't make its data confidential. Applications use Hedger to keep balances and transfer amounts confidential, with support for authorized auditing.
Should I build on DuskEVM or DuskVM?
Choose DuskEVM for Solidity contracts and existing EVM infrastructure. Choose DuskVM for Rust/WASM contracts that should run directly on the Dusk L1 and work closely with its transaction models, such as Phoenix shielded transfers.
Start building: read the DuskEVM overview in the Dusk docs