dharitri-vm-executor

Crates.iodharitri-vm-executor
lib.rsdharitri-vm-executor
version
sourcesrc
created_at2025-01-09 09:59:55.075423
updated_at2025-01-11 16:26:12.413976
descriptionDharitri VM executor interface
homepagehttps://dharitri.org/
repositoryhttps://github.com/TerraDharitri/drt-rs-vm-executor
max_upload_size
id1509762
Cargo.toml error:TOML parse error at line 20, column 1 | 20 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include`
size0
(mangonui)

documentation

https://docs.dharitri.org/

README

dharitri-vm-executor

The Dharitri 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.
Commit count: 8

cargo fmt