Cartesi Machine
A reproducible RISC-V virtual machine that boots Linux and runs familiar languages, libraries, and tools.
Technical Plan / 2026
Cartesi is open source and general purpose. The foundations are in place. Our current work focuses on security hardening, efficiency, and ease of use.
Cartesi combines a general Linux execution environment with permissionless dispute resolution on Ethereum.
A reproducible RISC-V virtual machine that boots Linux and runs familiar languages, libraries, and tools.
The PRT dispute system runs on Ethereum mainnet. One honest participant can enforce the correct result.
An independent maturity classification for the live PRT Honeypot rollup.
View on L2BEATEach application receives dedicated compute and can be deployed as an L2, an L3, or a sovereign rollup.
Status describes the work as of 3 August 2026. This page will change as tests complete and priorities move. To make technical progress easier to follow, we are publishing engineering reports (opens in a new tab) highlighting key developments and milestones.
Recovery paths and dispute resolution designed to hold under adversarial conditions.
Give users a path to recover funds if an application stops or funds are at risk.
Support multiple validator implementations to reduce correlated implementation risk.
Integrate hardened settlement and tournament logic across the rollups stack.
External review, extended live testing, and sophisticated adversarial testing.
Make risk models, simulations, and statistical analysis practical enough to run every block.
Faster state hashing, disk-backed state, and more efficient proofs for long computations.
Investigate a zero-knowledge route that can reduce delay without constraining computation.
Use sequencing for fast soft confirmations while fraud-proof settlement remains behind them.
Make familiar Linux tooling translate into a shorter path from idea to working application.
Multi-application throughput, restart resilience, and production diagnostics.
An MCP server and Cartesi skills for AI-assisted development workflows.
Local development, mainnet forking, and clearer node inspection.
Reference implementations for risk engines, curves, vaults, and advanced order types.
As the focus moved toward DeFi, work on Bitcoin execution, the EigenLayer coprocessor, Lambada, alternative data-availability and sequencer integrations, ENS resolution, and browser-based rollups was discontinued. The code remains open source for anyone who wants to continue those directions.
Explore the code