Language-agnostic specification for Cartesi Rollups v2 backend application logic. Defines deterministic state transitions, payload contracts, finish-loop correctness, and verifiable output emission under replay and dispute conditions.
Build Cartesi Rollups v2 backend applications in JavaScript and TypeScript with shared fundamentals: finish loop, typed payload parsing, advance/inspect handler separation, output emitters, asset deposits/withdrawals (Ether, ERC20, ERC721), and tests. Use when backend runtime is Node.js and the stack is JS or TS.
Build Cartesi Rollups v2 backend applications in Python with production-shaped structure: finish loop, advance/inspect handlers, payload codecs, output emitters, state modules, tests, and operational checks. Use when the target backend stack is Python.
Wire L1 smart contracts into a Cartesi Rollups v2 application via the InputBox contract. Use this when the user needs inputs to originate from on-chain contracts (oracles, governance, bridges, feeds), wants to write Solidity contracts that call InputBox.addInput, needs to execute vouchers on-chain, or wants to validate on-chain outputs. Triggers on: "L1 contract", "InputBox", "addInput", "on-chain input", "oracle", "governance", "bridge", "voucher execution", "validate output", "Solidity contract", "Foundry", "on-chain ingress", "portal", "ERC20 bridge", "Ether bridge".
Diagnose and fix errors across the Cartesi Rollups v2 stack. Use this whenever the user hits an error, unexpected behaviour, or a failed operation at any layer — CLI version confusion, build, run, node startup, application deployment, advance processing, inspect, voucher execution, or blockchain interaction. Triggers on: "error", "failed", "not working", "stuck", "wrong output", "inspect returns nothing", "advance not processed", "deploy failed", "deploy command not found", "chain id mismatch", "port", "container", "docker", "node won't start", "debug", "troubleshoot", "cartesi run fails", "wrong version", "command not found".
Deploy a Cartesi Rollups v2 application to a self-hosted rollups node for testnet or production-style deployment using Docker Compose. Covers CLI version detection, project version detection, building the machine image, downloading and configuring the Mugen-Builders compose setup, setting up the .env file, starting the node services, and registering the application. Also covers application lifecycle management (list, status, remove, execution parameters) and the node components reference. Triggers on: "deploy", "self-hosted", "testnet", "rollups node", "docker compose", "compose.local", "register application", "node setup", "Sepolia", "mainnet deployment", "production node", "Mugen-Builders".
Build Cartesi Rollups v2 frontend applications with clear module boundaries and predictable runtime behavior: wallet integration, app I/O, configuration, and optional asset bridging. Use this whenever the user asks for React/Next.js/ Angular (or any web frontend) that connects wallets, sends inputs to InputBox, reads machine state via Cartesi JSON-RPC, or uses @cartesi/wagmi and @cartesi/viem packages. If the user provides or references a project DESIGN.md, treat it as the primary visual design authority and follow Google DESIGN.md format/spec conventions.
Query a running Cartesi Rollups v2 node via its JSON-RPC 2.0 API (port 10011). Use this whenever you need to list or fetch applications, epochs, inputs, outputs (notices, vouchers, DELEGATECALL vouchers), reports, or node metadata programmatically. Covers all cartesi_ prefixed methods, type definitions, pagination and filtering patterns, error handling, and complete TypeScript interface reference. Triggers on: "JSON-RPC", "cartesi_listInputs", "cartesi_getOutput", "cartesi_listReports", "query node", "JSON-RPC API", "port 10011", "query outputs", "fetch notices", "fetch vouchers", "list epochs", "get processed inputs", "node version", "chain id", "jsonrpc-api service".