Deterministic Wasm for Web3
summary
Proposal to run deterministic WebAssembly as the chain VM with static verification and metering: bytecode stays standard Wasm (no changes) but contracts that use disallowed features like floating point are rejected, and nodes run a static metering pass that splits cost into precomputed block charges and runtime state costs by inserting use-gas checks. Example: Go “hello world” compiles to ~1 MB today because of bundled GC support; plan is testnet relaunch, add he wasn't runtime hooks and optional pre-compiles to replace slow EVM behavior.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:09Why WebAssembly for Web3
- 8:40WebAssembly beyond browser
- 12:39WebAssembly flexibility and extensibility
- 14:50EVM limitations
- 15:11Introducing Deterministic Wasm
- 16:14Removing non-determinism
- 17:20Metering costs
- 21:55Gas costs for Wasm
- 23:35Benchmarking Wasm
- 25:10Next steps
related talks
33mKeeping the asm in Wasm – Running high-level languages on a low-level VM
01h 08mOn WebAssembly
36mBringing honest computing to the WASM world
22mThe state of WebAssembly
40mWebAssembly - The Future of Distributed Computing
43mMeet Your Future - WebAssembly
26mWebAssembly for a Reactive Internet of Things
33mThe Buzz About Green Tech: WebAssembly's Impact on Carbon Footprint Reduction
