Practical overview
When it fits
Use FuelVM when developing or debugging Rust-based infrastructure or tooling that implements or targets the FuelVM specification, particularly workflows connected to fuel-core or Sway.
Who it is for
- Rust developers integrating Fuel execution into a Fuel-based environment.
- Sway and compiler-tooling developers working with FuelVM opcodes.
- Developers investigating VM opcode behavior or building test transactions.
Documented uses
- Integrate the VM implementation into a Fuel execution environment.
- Work with the instruction set used by Sway and the VM.
- Validate, estimate and execute Create and Script transactions through fuel-core’s block-execution component.
- Reproduce opcode behavior with VM tests and custom script test utilities.
- Build test transactions using the Fuel transaction builder.
Requirements & limits
The implementation is available in a public GitHub repository.
- The project is a Rust codebase and crate collection, rather than a hosted service.
- The
fuel-vmcrate executesfuel-asmopcodes; related crates cover transactions, storage, types, cryptography, Merkle trees and compression. - The README documents test helpers and a CI-check script, but notes that CI checks require pre-installed tools.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Add an opcode-focused VM test case
Create a test case for an opcode behavior in the FuelVM test suite.
Before you start
- The FuelVM repository and its test utilities.
- A specific opcode behavior to reproduce.
Steps
Review the VM unit tests for a relevant opcode and identify reusable test utilities.
Add a test case using the repository’s test-case pattern.
Run the specific test or the test suite, as appropriate.
Expected outcome
A test that reproduces or checks the selected opcode behavior in the VM test suite.
Guide limitations
- The README does not provide a complete command for running an individual test.
- This describes the repository’s documented workflow, not a verified execution.
Run a custom script in a VM test
Exercise a custom opcode sequence through the repository’s test helper and inspect its receipts.
Before you start
- The FuelVM repository and its test utilities.
- A Rust test containing the opcode sequence to exercise.
Steps
Build the opcode sequence using the instruction helpers shown in the README.
Call
test_helpers::run_scriptwith the sequence.Inspect the returned receipts; use
assert_panicswhen checking for the documented panic outcome.
Expected outcome
A test can examine the receipts produced by running the custom script, including an expected panic when asserted.
Guide limitations
- The README’s example is a test-code pattern, not a standalone runner.
- The repository’s required tools and exact test invocation are not specified here.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 17 October 2026
- Original website title
- FuelLabs/fuel-vm · Official homepage title · retained in its source language

