7 releases (breaking)

0.5.0 Nov 5, 2024
0.4.0 Oct 29, 2024
0.3.0 Sep 30, 2024
0.2.1 Aug 27, 2024
0.0.0-release Jul 8, 2024

#496 in Development tools

Download history 88/week @ 2024-07-22 59/week @ 2024-07-29 19/week @ 2024-08-05 292/week @ 2024-08-12 257/week @ 2024-08-19 410/week @ 2024-08-26 174/week @ 2024-09-02 126/week @ 2024-09-09 163/week @ 2024-09-16 136/week @ 2024-09-23 321/week @ 2024-09-30 253/week @ 2024-10-07 831/week @ 2024-10-14 96/week @ 2024-10-21 531/week @ 2024-10-28 421/week @ 2024-11-04

1,889 downloads per month
Used in 23 crates (via essential-asm-gen)

Apache-2.0

16KB
246 lines

Essential ASM Specification.

Crates.io Documentation license Build Status

This crate parses the Essential ASM specification from YAML and provides a structured model for deserializing and traversing the tree of operations.

The primary use is to assist in generating the official ASM declaration and implementations, though is likely useful for other tooling based on the essential ASM spec.

Operation Declaration

Each operation is identified by a unique name and contains the following fields:

  • opcode: A hexadecimal representation of the operation code, uniquely identifying the operation.
  • description: A brief explanation of what the operation does.
  • panics (optional): A list of reasons why the operation might cause the virtual machine to panic.
  • num_arg_bytes (optional): Specifies the number of bytes expected as arguments for the operation.
  • stack_in: Defines the inputs taken from the stack before operation execution. This is a list of symbolic identifiers representing the expected values. If stack_in is omitted, an empty list is assumed.
  • stack_out: Describes the outputs pushed onto the stack after operation execution. The stack output can either be "fixed" or "dynamic".
    • fixed: Used when the number of items pushed to the stack is constant. Represented as a list of strings representing the output values.
    • dynamic: Used when the number of items pushed to the stack can vary. Represented as a mapping with the following fields:
      • The elem field is a symbolic identifier representing the output values.
      • The len field specifies which stack_in word the length is derived from.

Examples

Push:
  opcode: 0x01
  description: Push one word onto the stack.
  num_arg_bytes: 8
  stack_out: [word]
ReadWordRange:
  opcode: 0x60
  description: |
    Read a range of words from state starting at the key.

    Reads the state key and the number of words from the stack input.

    Returns the memory address at which the data was written via the stack output.
  panics:
    - Not enough memory allocated to store the read state.
  stack_in: [key_w0, key_w1, key_w2, key_w3, n_words]
  stack_out: [mem_addr]

Operation Group

An operation group organizes related operations. It can include:

  • description: A brief overview of the group's purpose.
  • group: A mapping from names to operations (or other groups) within this group.

Example

    Stack:
      description: Operations related to stack manipulation.
      group:
        # Push:
        # etc

Multi-word Values

When a multi-word value (like a state key or an address) is read from the stack, the most-significant bits are assumed to have been pushed to the stack first.

Dependencies

~1.9–2.7MB
~57K SLoC