Skip to main content

Introduction

The backend of a Cartesi dApp processes requests in the following manner:

  • Finish — Called via /finish, indicates that any previous processing has been completed and the backend is ready to handle the next request. The subsequent request is returned as the call's response and can be of the following types:

    • Advance — Provides input to be processed by the backend to advance the Cartesi Machine state. When processing an Advance request, the backend can call the /voucher, and /report endpoints. For such requests, the input data contains both the payload and metadata, including the account address that submitted the input.

    • Inspect — Submits a query about the application's current state. When running inside a Cartesi Machine, this operation is guaranteed to leave the state unchanged, as the machine reverts to its exact previous condition after processing. For Inspect requests, the input data contains only a payload, and the backend can only call the /report endpoint.

  • Exception — Called by the backend when it encounters an unrecoverable error during request processing. This signals to the Rollup HTTP Server that the current request processing failed and should be terminated. See /exception for more details.

Advance and Inspect

Here is a simple boilerplate application that handles Advance and Inspect requests:

const rollup_server = process.env.ROLLUP_HTTP_SERVER_URL;
console.log("HTTP rollup_server url is " + rollup_server);

async function handle_advance(data) {
console.log("Received advance request data " + JSON.stringify(data));
return "accept";
}

async function handle_inspect(data) {
console.log("Received inspect request data " + JSON.stringify(data));
return "accept";
}

var handlers = {
advance_state: handle_advance,
inspect_state: handle_inspect,
};

var finish = { status: "accept" };

(async () => {
while (true) {
const finish_req = await fetch(rollup_server + "/finish", {
method: "POST",
headers: {
"Content-Type": "application/json",
},
body: JSON.stringify({ status: "accept" }),
});

console.log("Received finish status " + finish_req.status);

if (finish_req.status == 202) {
console.log("No pending rollup request, trying again");
} else {
const rollup_req = await finish_req.json();
var handler = handlers[rollup_req["request_type"]];
finish["status"] = await handler(rollup_req["data"]);
}
}
})();

An Advance request involves sending input data to the base layer via JSON-RPC, allowing it to reach the dApp backend to change the application's state.

img

Here is how an advance request works in the dApp architecture:

  • Step 1: Send an input to the addInput(address, bytes) function of the InputBox smart contract.

  • Step 2: The HTTP Rollups Server reads the data and sends it to the Cartesi Machine for processing.

  • Step 3: After computation, the machine state is updated, and the results are returned to the rollup server.

An Inspect request involves making an external HTTP API call to the rollups server to read the dApp state without modifying it.

img

You can make a simple inspect call from your frontend client to retrieve reports.

To perform an Inspect call, make a HTTP POST request to <address of the node>/inspect/<application name> with a payload in the request body. For example:

curl -X POST http://localhost:8080/inspect/<application name> \
-H "Content-Type: application/json" \
-d '{"payload": "0xdeadbeef"}'

The payload should be a hex-encoded string starting with '0x' followed by pairs of hexadecimal numbers.

After receiving the call's response, the payload is extracted from the response data, allowing the backend code to examine it and produce outputs as reports.

The direct output types for Advance requests are vouchers, notices, and reports, while Inspect requests generate only reports.

We use cookies to ensure that we give you the best experience on our website. By using the website, you agree to the use of cookies.