#dusk $DUSK @Dusk
DuskEVM
DuskEVM brings Solidity, EVM-compatible wallets, and familiar Ethereum tooling to Dusk. Existing EVM applications can be deployed on DuskEVM using familiar contracts and development workflows, while using DUSK for gas and DuskDS for settlement and data availability.
Why DuskEVM
- Start with the EVM stack. Use Solidity or Vyper alongside familiar tools such as Foundry, Hardhat, viem, ethers, and standard EVM wallets.
- Use DUSK throughout. DUSK is used to pay for execution and can move 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.
- Connect to the wider Dusk stack. EVM applications can access Dusk L1 assets, infrastructure, and privacy-oriented workflows as those integrations become available.
How It Fits
Component| Role
DuskDS| Consensus, settlement, and data availability
DuskEVM| Ethereum-compatible smart contract execution
Bridge| Moves DUSK and messages between the two environments
A DuskEVM transaction follows a rollup-style lifecycle:
1. The transaction is submitted to the DuskEVM sequencer.
2. The execution layer includes it in an L2 block.
3. The batcher publishes the transaction data to DuskDS.
4. State commitments and fault proofs connect the resulting state to DuskDS settlement.
Transaction inclusion can be fast, but inclusion and settlement are separate stages. Applications moving value between DuskEVM and the Dusk L1 should therefore rely on protocol or wallet status to determine finality rather than assuming finality based simply on how much time has passed.
DuskEVM
DuskEVM brings Solidity, EVM-compatible wallets, and familiar Ethereum tooling to Dusk. Existing EVM applications can be deployed on DuskEVM using familiar contracts and development workflows, while using DUSK for gas and DuskDS for settlement and data availability.
Why DuskEVM
- Start with the EVM stack. Use Solidity or Vyper alongside familiar tools such as Foundry, Hardhat, viem, ethers, and standard EVM wallets.
- Use DUSK throughout. DUSK is used to pay for execution and can move 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.
- Connect to the wider Dusk stack. EVM applications can access Dusk L1 assets, infrastructure, and privacy-oriented workflows as those integrations become available.
How It Fits
Component| Role
DuskDS| Consensus, settlement, and data availability
DuskEVM| Ethereum-compatible smart contract execution
Bridge| Moves DUSK and messages between the two environments
A DuskEVM transaction follows a rollup-style lifecycle:
1. The transaction is submitted to the DuskEVM sequencer.
2. The execution layer includes it in an L2 block.
3. The batcher publishes the transaction data to DuskDS.
4. State commitments and fault proofs connect the resulting state to DuskDS settlement.
Transaction inclusion can be fast, but inclusion and settlement are separate stages. Applications moving value between DuskEVM and the Dusk L1 should therefore rely on protocol or wallet status to determine finality rather than assuming finality based simply on how much time has passed.