Skip to content
Blockchain LabTHE VENTURE STUDIO

LibraryScaling2023Design paperCorpus record

FuelVM: a virtual machine for parallel transaction execution

Fuel Labs. Fuel Labs.

Fuel's design bet is a UTXO-like state model and a virtual machine built so transactions that do not touch the same state can execute together.

A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.

Fuel's design bet is a UTXO-like state model and a virtual machine built so transactions that do not touch the same state can execute together.
Evidence
Primary paper
Re-measured
No
Assumptions
3
Records linked
5

01 Claim ledger

What the paper is allowed to say

Each row is a sentence already in the study. The status is the same on every row: a model claim, not a live measurement.

  1. Claim 01 · Paper model

    The defect

    A chain that says parallel execution but still forces a global sequential read-write set has kept the slogan.

  2. Claim 02 · Paper model

    The proposal

    Fuel's design bet is a UTXO-like state model and a virtual machine built so transactions that do not touch the same state can execute together.

  3. Claim 03 · Paper model

    The mechanism

    The state model decides which transactions conflict. The virtual machine does not discover parallelism after the fact if every call shares one account.

  4. Claim 04 · Paper model

    The bound

    This note does not quote throughput.

02 Three cuts

Observation, model, falsifier

A desk does not stop at the summary. Each claim is cut three ways, using only this study's own assumptions and checks. Nothing here is a new figure.

  1. 01 The defect

    Observation

    What the study says

    A chain that says parallel execution but still forces a global sequential read-write set has kept the slogan.

    Model

    What has to hold

    You are reading the Fuel book and specs, not a benchmark.

    Falsifier

    What would retire it

    Which state objects does a transaction declare it will touch?

  2. 02 The proposal

    Observation

    What the study says

    Fuel's design bet is a UTXO-like state model and a virtual machine built so transactions that do not touch the same state can execute together.

    Model

    What has to hold

    The document is the one at the source URL. A marketing page with the same brand is not this text.

    Falsifier

    What would retire it

    Which state objects does a transaction declare it will touch?

  3. 03 The mechanism

    Observation

    What the study says

    The state model decides which transactions conflict. The virtual machine does not discover parallelism after the fact if every call shares one account.

    Model

    What has to hold

    No price, supply, yield, or adoption figure is added by this desk.

    Falsifier

    What would retire it

    Which state objects does a transaction declare it will touch?

  4. 04 The bound

    Observation

    What the study says

    This note does not quote throughput.

    Model

    What has to hold

    You are reading the Fuel book and specs, not a benchmark.

    Falsifier

    What would retire it

    Which state objects does a transaction declare it will touch?

03 Sequence

One action, as an operating tape

  1. 01The state model decides which transactions conflict. The virtual machine does not discover parallelism after the fact if every call shares one account.
  2. 02Predicates and scripts are different objects in the docs. A predicate authorises spending. A script is execution.
  3. 03Fuel can settle as a rollup or stand alone. The security assumption follows that choice and has to be named.

04 Load-bearing

The argument, and where a pitch drops it

  1. What the name has to mean

    The cut

    Fuel's design bet is a UTXO-like state model and a virtual machine built so transactions that do not touch the same state can execute together.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    A UTXO model is not automatically private, and it is not Bitcoin.

  2. What actually moves

    The cut

    Predicates and scripts are different objects in the docs. A predicate authorises spending. A script is execution.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    Parallel execution does not remove the need for a consensus or settlement rule.

  3. What a later deployment may change

    The cut

    Fuel can settle as a rollup or stand alone. The security assumption follows that choice and has to be named.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    A later client, parameter or reward formula is a different object from this paragraph.

05 Register

What has to be true

  • Model · Not re-measured

    You are reading the Fuel book and specs, not a benchmark.

  • Model · Not re-measured

    The document is the one at the source URL. A marketing page with the same brand is not this text.

  • Model · Not re-measured

    No price, supply, yield, or adoption figure is added by this desk.

06 Divergence

What happened after the paper

Parallel execution does not remove the need for a consensus or settlement rule.

A later client, parameter set, or reward formula is a different object. Cite this paper for the mechanism. Cite a primary release for the network. This desk has not re-run the proof.

07 Pre-mortem

What to check before you use the idea

  4. 0 of 3 marked on this browser. A mark is a reading note, not a pass, a rating, or a recommendation.

08 Anatomy

The paper, in the order a builder needs

The problem it names

A chain that says parallel execution but still forces a global sequential read-write set has kept the slogan.

What the design proposes

  • The state model decides which transactions conflict. The virtual machine does not discover parallelism after the fact if every call shares one account.
  • Predicates and scripts are different objects in the docs. A predicate authorises spending. A script is execution.
  • Fuel can settle as a rollup or stand alone. The security assumption follows that choice and has to be named.

How the mechanism is specified

  • The state model decides which transactions conflict. The virtual machine does not discover parallelism after the fact if every call shares one account.
  • Predicates and scripts are different objects in the docs. A predicate authorises spending. A script is execution.
  • Fuel can settle as a rollup or stand alone. The security assumption follows that choice and has to be named.

What this page does not treat as proven

  • This note does not quote throughput.
  • A UTXO model is not automatically private, and it is not Bitcoin.
  • Parallel execution does not remove the need for a consensus or settlement rule.

Why the desk still reads it

Fuel's design bet is a UTXO-like state model and a virtual machine built so transactions that do not touch the same state can execute together.

09 Lexicon

Terms, opened into the record

FuelVM
The machine described in the Fuel docs. It is not the EVM.
Conflict set
The state a transaction says it will touch. Overlap is what blocks parallel execution.

10 Repository

Every linked record on this page

Underlined words open a page that already exists: a concept, a protocol profile, a failure record, or another paper. If a word is not underlined, this desk does not have a record for it.

Protocols

This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.

Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.