Skip to content

Latest commit

 

History

History
167 lines (115 loc) · 11.2 KB

main.md

File metadata and controls

167 lines (115 loc) · 11.2 KB
Raw

Fuel VM Specification

Introduction

This document provides the specification for the Fuel Virtual Machine (FuelVM). The specification covers the types, opcodes, and execution semantics.

Parameters

name type value note
CONTRACT_MAX_SIZE uint64 Maximum contract size, in bytes.
MEM_MAX_ACCESS_SIZE uint64 Maximum memory access size, in bytes.
VM_MAX_RAM uint64 2**26 64 MiB.

Semantics

FuelVM instructions are exactly 32 bits (4 bytes) wide and comprise of a combination of:

  • Opcode: 8 bits
  • Register/special register (see below) identifier: 6 bits
  • Immediate value: 12, 18, or 24 bits, depending on operation

Of the 64 registers (6-bit register address space), the first 16 are reserved:

value register name description
0x00 $zero zero Contains zero (0), for convenience.
0x01 $one one Contains one (1), for convenience.
0x02 $of overflow Contains overflow/underflow of addition, subtraction, and multiplication.
0x03 $pc program counter The program counter. Memory address of the current instruction.
0x04 $ssp stack start pointer Memory address of bottom of current writable stack area.
0x05 $sp stack pointer Memory address on top of current writable stack area (points to free memory).
0x06 $fp frame pointer Memory address of beginning of current call frame.
0x07 $hp heap pointer Memory address below the current bottom of the heap (points to free memory).
0x08 $err error Error codes for particular operations.
0x09 $ggas global gas Remaining gas globally.
0x0A $cgas context gas Remaining gas in the context.
0x0B $bal balance Received balance for this context.
0x0C $is instrs start Pointer to the start of the currently-executing code.
0x0D $ret return value Return value or pointer.
0x0E $retl return length Return value length in bytes.
0x0F $flag flags Flags register.

Integers are represented in big-endian format, and all operations are unsigned. Boolean false is 0 and Boolean true is 1.

Registers are 64 bits (8 bytes) wide. Words are the same width as registers.

Persistent state (i.e. storage) is a key-value store with 32-byte keys and 32-byte values. Each contract has its own persistent state that is independent of other contracts. This is committed to in a Sparse Binary Merkle Tree.

Flags

value name description
0x01 F_UNSAFEMATH If bit is set, safe arithmetic and logic is disabled.
0x02 F_WRAPPING If bit is set, wrapping does not cause panic.

Opcodes

A complete list of opcodes in the Fuel VM is documented here.

VM Initialization

Every time the VM runs, a single monolithic memory of size VM_MAX_RAM bytes is allocated, indexed by individual byte. A stack and heap memory model is used, allowing for dynamic memory allocation in higher-level languages. The stack begins at 0 and grows upward. The heap begins at VM_MAX_RAM - 1 and grows downward.

To initialize the VM, the following is pushed on the stack sequentially:

  1. Transaction hash (byte[32], word-aligned), computed as defined here.
  2. MAX_INPUTS pairs of (color: byte[32], balance: uint64), of:
    1. For predicate verification, zeroes.
    2. For script execution, the free balance for each color seen in the transaction's inputs, ordered in ascending order. If there are fewer than MAX_INPUTS colors, the pair has a value of zero.
  3. Transaction length, in bytes (uint64, word-aligned).
  4. The transaction, serialized.

Then the following registers are initialized (without explicit initialization, all registers are initialized to zero):

  1. $ssp = 32 + MAX_INPUTS*(32+8) + size(tx)): the writable stack area starts immediately after the serialized transaction in memory (see above).
  2. $sp = $ssp: writable stack area is empty to start.
  3. $hp = VM_MAX_RAM - 1: the heap area begins at the top and is empty to start.

Contexts

There are 3 contexts in the FuelVM: predicates, scripts, and calls. A context is an isolated execution environment with defined memory ownership and can be external or internal:

  • External: predicate and script. $fp will be zero.
  • Internal: call. $fp will be non-zero.

Returning from a context behaves differently depending on whether the context is external or internal.

Predicate Verification

For any input of type InputType.Coin, a non-zero predicateLength field means the UTXO being spent is a P2SH rather than a P2PKH output.

For each such input in the transaction, the VM is initialized, then:

  1. $pc and $is are set to the start of the input's predicate field.

During predicate mode, hitting any of the following opcodes causes predicate verification to halt, returning Boolean false:

  1. Any contract opcode.
  2. JI or JNEI with jump-to value less than or equal to $pc (these would allow loops). In other words, $pc must be strictly increasing.

In addition, during predicate mode if $pc is set to a value greater than the end of predicate bytecode (this would allow bytecode outside the actual predicate), predicate verification halts returning Boolean false.

A predicate that halts without returning Boolean true does not pass verification, making the entire transaction invalid. Note that predicate validity is monotonic with respect to time (i.e. if a predicate evaluates to true then it will always evaluate to true in the future).

Script Execution

If script bytecode is present, transaction validation requires execution.

The VM is initialized, then:

  1. $pc and $is are set to the start of the transaction's script bytecode.
  2. $bal is set to the free balance.
  3. $ggas and $cgas are set to tx.gasLimit.

Following initialization, execution begins.

For each instruction, its gas cost gc is first computed. If gc > $cgas, deduct $cgas from $ggas and $cgas (i.e. spend all of $cgas and no more), then revert immediately without actually executing the instruction. Otherwise, deduct gc from $ggas and $cgas.

Call Frames

Cross-contract calls push a call frame onto the stack, similar to a stack frame used in regular languages for function calls (which may be used by a high-level language that targets the FuelVM). The distinction is as follows:

  1. Stack frames: store metadata across trusted internal (i.e. intra-contract) function calls. Not supported natively by the FuelVM, but may be used as an abstraction at a higher layer.
  2. Call frames: store metadata across untrusted external (i.e. inter-contract) calls. Supported natively by the FuelVM.

Call frames are needed to ensure that the called contract cannot mutate the running state of the current executing contract. They segment access rights for memory: the currently-executing contracts may only write to their own call frame and their own heap.

A call frame consists of the following, word-aligned:

bytes type value description
Unwritable area begins.
32 byte[32] to Contract ID for this call.
32 byte[32] color Color of forwarded coins.
8*64 byte[8][64] regs Saved registers from previous context.
8 uint16 codesize Code size in bytes, padded to word alignment.
8 byte[8] param1 First parameter.
8 byte[8] param2 Second parameter.
1* byte[] code Zero-padded to 8-byte alignment, but individual instructions are not aligned.
Unwritable area ends.
* Call frame's stack.

Ownership

Whenever memory is written to (i.e. with SB or SW), or write access is granted (i.e. with CALL), ownership must be checked.

If the context is external, the owned memory range is:

  1. [$ssp, $sp): the writable stack area.
  2. ($hp, VM_MAX_RAM - 1]: the heap area allocated by this script or predicate.

If the context is internal, the owned memory range for a call frame is:

  1. [$ssp, $sp): the writable stack area of the call frame.
  2. ($hp, $fp->$hp]: the heap area allocated by this call frame.