MPVM — Deterministic Parallel WebAssembly
Research into executing many transactions at once while guaranteeing every node reaches exactly the same result.
Why parallel, why deterministic
Sequential execution limits throughput to a single core. Naive parallelism risks nodes producing different results. MPVM investigates scheduling independent transactions across parallel lanes while preserving a canonical, reproducible outcome.
Illustrative
Execution pipeline
- 01Ordered block
- 02Access-set analysis
- 03Dependency graph
- 04Parallel lanes
- 05Conflict check
- 06Deterministic commit
Key research areas
WebAssembly runtime
A deterministic Wasm subset with no floating-point nondeterminism or host-dependent behavior.
Dependency management
Declared and inferred read/write sets build a dependency graph before execution.
Conflict resolution
Conflicting transactions are re-ordered or re-executed in canonical block order.
Resource metering
Per-instruction metering bounds compute and storage, resisting denial-of-service.
Sandboxing
Isolated execution contexts prevent contracts from affecting each other or the host.
Reproducibility
Every honest node must derive the same state root from the same ordered block.
MPVM is at the research and specification stage. No public runtime, SDK, or performance results are available yet.