#dusk $DUSK @Dusk
Previously, I thought a blockchain’s virtual machine was just the place where smart contracts “run.” Looking deeper into Dusk changed that view.
Piecrust was built as Dusk’s WASM virtual machine, with "piecrust" handling contract execution and "piecrust-uplink" providing the developer layer for creating and working with contracts. The interesting part is not the name of the VM. It is the design choice behind it: using WASM and Rust to create a controlled execution environment for Dusk smart contracts.
Today, Dusk’s documentation describes this execution path as DuskVM, based on the Wasmtime runtime with custom support for Dusk’s execution model. It runs Rust/WASM contracts directly on the Dusk L1, including applications that need direct access to Dusk’s transaction model, assets, privacy, or zero knowledge capabilities.
That distinction matters.
Dusk now presents developers with two different paths: DuskVM for Rust/WASM applications requiring native L1 capabilities, and DuskEVM for Solidity and Ethereum compatible tooling.
So I no longer see the VM as merely a technical component. It is part of the decision about what kind of application Dusk can support natively.
The question I’m watching is whether this dual execution model can give developers flexibility without making the ecosystem harder to understand.
@Dusk $DUSK
Previously, I thought a blockchain’s virtual machine was just the place where smart contracts “run.” Looking deeper into Dusk changed that view.
Piecrust was built as Dusk’s WASM virtual machine, with "piecrust" handling contract execution and "piecrust-uplink" providing the developer layer for creating and working with contracts. The interesting part is not the name of the VM. It is the design choice behind it: using WASM and Rust to create a controlled execution environment for Dusk smart contracts.
Today, Dusk’s documentation describes this execution path as DuskVM, based on the Wasmtime runtime with custom support for Dusk’s execution model. It runs Rust/WASM contracts directly on the Dusk L1, including applications that need direct access to Dusk’s transaction model, assets, privacy, or zero knowledge capabilities.
That distinction matters.
Dusk now presents developers with two different paths: DuskVM for Rust/WASM applications requiring native L1 capabilities, and DuskEVM for Solidity and Ethereum compatible tooling.
So I no longer see the VM as merely a technical component. It is part of the decision about what kind of application Dusk can support natively.
The question I’m watching is whether this dual execution model can give developers flexibility without making the ecosystem harder to understand.
@Dusk $DUSK