multiversx-chain-vm-executor
| Crates.io | multiversx-chain-vm-executor |
| lib.rs | multiversx-chain-vm-executor |
| version | 0.5.1 |
| created_at | 2023-06-15 09:47:06.360949+00 |
| updated_at | 2026-01-20 16:33:19.362972+00 |
| description | MultiversX VM executor interface |
| homepage | https://multiversx.com/ |
| repository | https://github.com/multiversx/mx-vm-executor-rs |
| max_upload_size | |
| id | 890977 |
| size | 256,068 |
Bianca Ialangi (BiancaIalangi)
documentation
https://docs.multiversx.com/
README
multiversx-chain-vm-executor
The MultiversX VM is composed of two parts:
- A high-level VM, that connects to the protocol and manages the environment of the smart contract execution
- A low-level component, called "executor", whose sole purpose is running WebAssembly code, as given. The only current implementation of this component is a wrapper around Wasmer 2.2.
This crate contains the Rust implementation of the interface between the two VM layers.
There are two parts of this interface:
- The one going "forwards", from high-level, to low-level, used for starting execution:
Executor,Instance. - The one going "backwards", from low-level, to high-level, used by the executor to request data:
VMHooks.
Two interfaces
There are currently 2 interfaces provided by this crate:
- A legacy interface, currently used in production, via the CAPI crate.
- A new set of traits, currently only used in the Rust VM.
We intend to migrate to the new interface in the CAPI as well, but this requires additional implementation efforts, as well as testing.