Maksym Zavershynskyi (Apr 21 2020 at 00:38): Maksym Zavershynskyi (Apr 21 2020 at 00:38):Hey! We have created the following community group to discuss Wasm for blockchains: https://github.com/wasm-blockchain/. It currently involves Parity, Near Protocol, Cosmos, and Wasmer. It would be super useful if someone working on Wasmtime could look into this matrix and edit or add missing information about Wasmtime: https://github.com/wasm-blockchain/runtimes Thank you, Max
Yury Delendik (Apr 21 2020 at 01:21):/me wonders how WASI is useful/relevant for blockchains.
Maksym Zavershynskyi (Apr 21 2020 at 01:31):Standardization of APIs, since many blockchains have key-value storage interface that they expose to the contracts.
Till Schneidereit (Apr 21 2020 at 10:44):Thanks for reaching out! Here's what those tables look like for Wasmtime + Cranelift:
WASI :check:
Metering :repeat: (I know of multiple projects on this, not sure if they're public)
SIMD :repeat:
Multi-return value :check:
OS Support :check: for all
Spec tests :check:
cargo-fuzz :check:
(note on fuzzers: I don't think having multiple fuzzer configurations is a meaningful differentiator. What's more important is how well the fuzzers are configured, and how fuzzing is run. The former is a qualitative measure, but the latter is a lot about quantity—how much in the way of resources you throw at it. Wasmtime is the first Rust project to be accepted into Google's OSS-Fuzz, which means it gets a significant amount of fuzzing resources thrown at it on an ongoing basis.)
Here are some additional things that might be interesting to people evaluating runtimes:
Debugging in gdb/lldb :check:
Openly governed :check:
License gives a patent grant :check:
Maksym Zavershynskyi (Apr 21 2020 at 16:42):Thank you @Till Schneidereit !
Till Schneidereit (Apr 21 2020 at 17:04):of course! :slight_smile:
Last updated: Nov 22 2024 at 17:03 UTC