Wasmer is a production-grade WebAssembly runtime with a real track record outside of blockchain. That matters. Most ZK-focused chains build execution environments on top of experimental infrastructure and then spend years fixing the stability problems that experimental infrastructure produces.
Dusk's decision to use Wasmer as Piecrust's execution engine is a choice I read as deliberately conservative in the right direction. You're not inventing a new runtime when a battle-tested one exists and can be adapted.
The adaptation question is what I examined carefully. Wasmer handles general WASM execution cleanly. Zero-knowledge proof generation inside a WASM environment introduces constraints that general runtimes weren't designed around.
How Piecrust manages the boundary between WASM execution and ZK circuit generation is the technical seam worth understanding before assuming the integration is seamless.
#dusk $DUSK @Dusk
Dusk's decision to use Wasmer as Piecrust's execution engine is a choice I read as deliberately conservative in the right direction. You're not inventing a new runtime when a battle-tested one exists and can be adapted.
The adaptation question is what I examined carefully. Wasmer handles general WASM execution cleanly. Zero-knowledge proof generation inside a WASM environment introduces constraints that general runtimes weren't designed around.
How Piecrust manages the boundary between WASM execution and ZK circuit generation is the technical seam worth understanding before assuming the integration is seamless.
#dusk $DUSK @Dusk