#dusk $DUSK @Dusk
DuskEVM
DuskEVM brings Ethereum-compatible smart contracts to Dusk, allowing developers to use Solidity, familiar EVM wallets, and established Ethereum tools. DUSK is used for gas, while DuskDS handles settlement and data availability.
Why DuskEVM?
Familiar EVM tools
Build with Solidity or Vyper using Foundry, Hardhat, ethers, viem, and standard EVM wallets.
DUSK for execution
DUSK pays transaction fees and can move between Dusk L1 and DuskEVM through the bridge.
Settlement on DuskDS
Transaction batches and state commitments connect DuskEVM activity to Dusk’s consensus and data-availability layer.
Connect with Dusk
EVM applications can access Dusk L1 assets, infrastructure, and privacy-focused capabilities where supported.
How It Works
DuskEVM handles smart contract execution, while DuskDS provides consensus, settlement, and data availability. The bridge allows DUSK and messages to move between Dusk L1 and DuskEVM.
A typical transaction follows these steps:
1. The transaction is sent to the DuskEVM sequencer.
2. It is processed and included in an L2 block.
3. Transaction data is grouped into batches and published to DuskDS.
4. State commitments and fault proofs link the resulting state to DuskDS settlement.
Fast inclusion does not necessarily mean final settlement. When moving value between DuskEVM and Dusk L1, applications should rely on protocol or wallet status rather than elapsed time alone.
Choosing an Execution Environment
Choose DuskEVM for Solidity applications, EVM wallets, Ethereum libraries, and existing EVM infrastructure.
Choose DuskVM for Rust/WASM contracts that need direct access to Dusk L1, its transaction model, protocol assets, privacy features, or zero-knowledge capabilities.
Both environments provide different ways to build within the Dusk ecosystem.
DuskEVM
DuskEVM brings Ethereum-compatible smart contracts to Dusk, allowing developers to use Solidity, familiar EVM wallets, and established Ethereum tools. DUSK is used for gas, while DuskDS handles settlement and data availability.
Why DuskEVM?
Familiar EVM tools
Build with Solidity or Vyper using Foundry, Hardhat, ethers, viem, and standard EVM wallets.
DUSK for execution
DUSK pays transaction fees and can move between Dusk L1 and DuskEVM through the bridge.
Settlement on DuskDS
Transaction batches and state commitments connect DuskEVM activity to Dusk’s consensus and data-availability layer.
Connect with Dusk
EVM applications can access Dusk L1 assets, infrastructure, and privacy-focused capabilities where supported.
How It Works
DuskEVM handles smart contract execution, while DuskDS provides consensus, settlement, and data availability. The bridge allows DUSK and messages to move between Dusk L1 and DuskEVM.
A typical transaction follows these steps:
1. The transaction is sent to the DuskEVM sequencer.
2. It is processed and included in an L2 block.
3. Transaction data is grouped into batches and published to DuskDS.
4. State commitments and fault proofs link the resulting state to DuskDS settlement.
Fast inclusion does not necessarily mean final settlement. When moving value between DuskEVM and Dusk L1, applications should rely on protocol or wallet status rather than elapsed time alone.
Choosing an Execution Environment
Choose DuskEVM for Solidity applications, EVM wallets, Ethereum libraries, and existing EVM infrastructure.
Choose DuskVM for Rust/WASM contracts that need direct access to Dusk L1, its transaction model, protocol assets, privacy features, or zero-knowledge capabilities.
Both environments provide different ways to build within the Dusk ecosystem.
