Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Asterisc support guide #1189

Open
wants to merge 8 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from 4 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions pages/stack/fault-proofs/_meta.json
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@
"explainer": "Fault proofs explainer",
"fp-components": "FP system components",
"cannon": "FPVM: Cannon",
"asterisc": "Asterisc",
bradleycamacho marked this conversation as resolved.
Show resolved Hide resolved
"challenger": "OP-Challenger",
"mips": "MIPS.sol",
"fp-security": "FP Mainnet security"
Expand Down
76 changes: 76 additions & 0 deletions pages/stack/fault-proofs/asterisc.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,76 @@
---
title: Asterisc
lang: en-US
description: Learn about Asterisc
---

# Asterisc

[Asterisc](https://github.com/protolambda/asterisc/tree/master) is an alternative fault-proof VM for the OP Stack, crafted to validate RISC-V program execution via an interactive fraud-proof mechanism. Asterisc bridges simplicity and functionality, delivering a minimalist yet powerful solution for optimistic rollup fraud-proofing. Leveraging the RISC-V architecture, it offers:

* Support for 64-bit operations
* Concurrent yet deterministic threading
* Compatibility with RISC-V's expanding ecosystem
bradleycamacho marked this conversation as resolved.
Show resolved Hide resolved

Read more about fault-proofs in our [Fault-proof explainer](/stack/fault-proofs/explainer)

## How it works

Asterisc enables parties to reach consensus on shared execution trace states. In cases of dispute, it identifies the diverging execution step. Commitments are generated for memory, registers, CSR, and VM states across the execution trace, with disputed steps emulated within the EVM to resolve inconsistencies.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Similar to a comment above, it's not Asterisc alone that "enables parties to reach consensus on shared execution trace states". It's the fault proof program (Kona in this case) running in a fault proof VM (Asterisc in this case) that does this.


Ready to dive in? Keep reading or head over to the [Asterisc repo](https://github.com/protolambda/asterisc/tree/master).
bradleycamacho marked this conversation as resolved.
Show resolved Hide resolved

## Getting started

1. Read through the [additional repo docs](https://github.com/protolambda/asterisc/tree/master/docs).
bradleycamacho marked this conversation as resolved.
Show resolved Hide resolved
2. Use Foundry to compile the associated smart contracts.
3. Compile test binaries using the [`Makefile`](https://github.com/protolambda/asterisc/blob/master/tests/go-tests/Makefile).
bradleycamacho marked this conversation as resolved.
Show resolved Hide resolved
4. Execute `rvgo` tests to validate both on-chain and off-chain operations through RISC-V unit tests.

## Key components

* **`rvgo`:** A Go-based RISC-V emulator with two operational modes:
* **`Fast Mode`:** Executes one instruction per step on the VM state.
* **`Slow Mode`:** Emulates one instruction per step using a VM state oracle.
* **`rvsol`:** A Solidity/Yul implementation of the slow-mode step for EVM compatibility.

### Yul in Solidity

Yul is chosen for its simplicity and precision, offering direct mirroring with Go code while retaining critical features like underflow/overflow behavior and untyped operations.

[See the repo](https://github.com/protolambda/asterisc/blob/master/README.md#why-use-yul-in-solidity) for a deeper dive on Yul and fast/slow modes.
bradleycamacho marked this conversation as resolved.
Show resolved Hide resolved

## Supported RISC-V subsets

Here's a few key subsets. For the complete list, see the [repo](https://github.com/protolambda/asterisc?tab=readme-ov-file#risc-v-subset-support).

* `RV32I`: Base 32-bit instruction set
* `RV64I`: 64-bit instruction set
* `RV32M` and `RV64M`: Multiplication
* `RV32A` and `RV64A`: Atomics
* Compact instructions for Rust: Work in progress

Unsupported operations are implemented as no-ops, ensuring compatibility with the Go runtime.

## FAQ

The following section highlights specific advantages that Asterisc provides over other fault-proof systems.

### Benefits over Cannon

[Cannon](https://github.com/ethereum-optimism/cannon/), originally developed by [`geohot`](https://github.com/geohot/) and now maintained by Optimism, offers similar functionality but has key differences:

* Cannon operates on a 32-bit MIPS architecture, whereas Asterisc uses RISC-V.
* Asterisc supports 64-bit operations and deterministic threading, making it more future-ready.

### Benefits over Cartesi

[Cartesi](https://github.com/cartesi/) provides RISC-V fraud-proofing for a full machine, including numerous additional features. However, this added complexity can introduce risks. Asterisc focuses on simplicity by running single-process executions with minimal system calls.

### Benefits over WebAssembly

Arbitrum's WebAssembly-based fraud-proofing leverages a business-source license and transformation to WAVM, limiting its general usability. In contrast, Asterisc is open-source under the MIT license, offering broader applicability.

## Contributing

Asterisc is designed to run Go programs for fraud-proofing optimistic rollups. Contributions that align with its goals of simplicity, minimalism, and compatibility are highly encouraged.
Loading