I have been looking at Dusk’s WASM side again and the recent developer activity caught my attention. DuskVM is the native execution path for running Rust and WASM smart contracts directly on the Dusk L1.
The interesting part is that Dusk is not treating this as a standalone VM. The network now has two paths. DuskEVM is there for Solidity and familiar EVM tooling, while DuskVM is aimed at applications that need native Dusk execution, privacy and custom contract logic.
The developer tooling is also moving. Dusk Forge provides a simpler way to build WASM contracts generate the needed interfaces and test them before deployment.I also noticed recent activity across the core repositories. Piecrust, the WASM VM project, was updated in July, while the DuskEVM genesis repository also saw activity in late July.Feels quiet lately, but the development side is still moving. Something is building maybe.
@Dusk
#dusk
$DUSK
The interesting part is that Dusk is not treating this as a standalone VM. The network now has two paths. DuskEVM is there for Solidity and familiar EVM tooling, while DuskVM is aimed at applications that need native Dusk execution, privacy and custom contract logic.
The developer tooling is also moving. Dusk Forge provides a simpler way to build WASM contracts generate the needed interfaces and test them before deployment.I also noticed recent activity across the core repositories. Piecrust, the WASM VM project, was updated in July, while the DuskEVM genesis repository also saw activity in late July.Feels quiet lately, but the development side is still moving. Something is building maybe.
@Dusk
#dusk
$DUSK
