NoNodo is a development node for the Cartesi Rollups that was designed to work with applications running in the host machine instead of the Cartesi machine. So, the application developer doesn't need to be concerned with compiling their application to RISC-V. The application back-end should run in the developer's machine and call the Rollup HTTP API to process advance and inspect inputs.
NoNodo is a valuable development workflow help, but there are some caveats the developer must be aware of:
- The application will eventually need to be compiled to RISC-V or use a RISC-V runtime in case of interpreted languages;
- In this mode, the application will not be running inside the sandbox of the Cartesi machine and will not block operations that won't be allowed when running inside a Cartesi machine, like accessing remote resources;
- This mode only works for applications that use the Cartesi Rollups HTTP API and doesn't work with applications using the low-level API;
- Performance inside a Cartesi machine will be much lower than running on the host.
NoNodo uses the Anvil as the underlying Ethereum node. To install Anvil, read the instructions on the Foundry book.
Installing NoNodo using the go install
command is possible.
To use this command, install Go following the instructions on the Go website.
Then, run the command below to install NoNodo.
go install github.com/gligneul/nonodo@latest
Make sure you add the Go path to your system path. The snippet below exemplifies that.
export PATH="$HOME/go/bin:$PATH"
To start NoNodo with the default configuration, run the command below.
nonodo
With the default configuration, NoNodo starts an Anvil node with the Cartesi Rollups contracts deployed.
NoNodo uses the same deployment used by sunodo, so the contract addresses are the same.
NoNodo offers some flags to configure Anvil, starting with --anvil-*
.
To send an input to the Cartesi application, you may use cast, a command-line tool from the foundry
package. For instance, the invocation below sends an input with contents 0xdeadbeef
to the running
application.
INPUT=0xdeadbeef; \
INPUT_BOX_ADDRESS=0x59b22D57D4f067708AB0c00552767405926dc768; \
APPLICATION_ADDRESS=0x70ac08179605AF2D9e75782b8DEcDD3c22aA4D0C; \
cast send \
--mnemonic "test test test test test test test test test test test junk" \
--rpc-url "http://localhost:8545" \
$INPUT_BOX_ADDRESS \
"addInput(address,bytes)(bytes32)" \
$APPLICATION_ADDRESS $INPUT
NoNodo exposes the Cartesi Rollups GraphQL (/graphql
) and Inspect (/inspect
) APIs for the application front-end, and the Rollup (/rollup
) API for the application back-end.
NoNodo uses the HTTP address and port set by the --http-address
and --http-port
flags.
NoNodo can run the application back-end as a sub-process.
If this process exits, NoNodo will also stop its execution.
This option is helpful to keep the whole development context in a single terminal.
To use this option, pass the command to run the application after --
.
nonodo -- ./my-app
NoNodo has a built-in echo application that generates a voucher, a notice, and a report for each advance input.
The echo also generates a report for each inspect input.
This option is useful when testing the application front-end without a working back-end.
To start NoNodo with the built-in echo application, use the --built-in-echo
flag.
nonodo --built-in-app