#dusk $DUSK @Dusk

I’ve been looking at how smart contracts actually run on Dusk, and Piecrust is one part I found pretty interesting.

Most people know the EVM model, where Solidity and a huge developer ecosystem make building easier. Dusk takes another route with DuskVM, where contracts are written in Rust and compiled to WASM before execution.

What I like about Piecrust is that it was built specifically around Dusk’s execution needs instead of simply copying the usual VM design. It supports things like custom memory management, Dusk’s ABI and inter-contract calls. Dusk also worked on reducing unnecessary VM re-execution and improving performance. In one earlier testnet update, Dusk reported handling around 70–150 transactions in a block on low-spec cloud systems.

There is also a 64KB argument buffer in the current DuskVM contract model, which is a small technical detail but shows how specifically the execution environment is designed.

But I don’t think Piecrust automatically beats EVM. EVM has the advantage of compatibility, tools and developers.

For me, the real question is whether Dusk can turn this specialized design into real adoption.

specialized VM or EVM compatibility?