Skip to main content
Version: 1.0

Deploying dApps

Cartesi Rollups dApps are intended to be deployed to public blockchains, so that they can be accessed by users. This can be done by taking advantage of a cloud-based infrastructure provided by Cartesi.

As happens with any blockchain application, the act of "deploying a dApp" involves publishing its smart contract so that it is publicly available and usable by clients or front-end applications. In the context of a Cartesi dApp, the smart contract is represented by an arbitrary back-end program that runs on Linux inside a Cartesi Node. This means that deploying Cartesi dApps basically corresponds to first deploying a smart contract that represents your dApp on-chain and then instantiating Cartesi Nodes that run the intended back-end logic of the application.

In order to facilitate the instantiation of such nodes, Cartesi provides an infrastructure for easily getting them running in the cloud. Developers are thus invited to take advantage of this convenience service in order to jump-start bringing their applications to public blockchains.

Supported networks

As stated above, the first step in the deployment of a new Cartesi dApp to a blockchain requires creating a smart contract on that network that makes use of the Cartesi Rollups smart contracts. For convenience, Cartesi has already deployed the Rollups smart contracts to a number of networks, in order to make it easier for developers to create dApps on them.

The table below shows the list of all networks that are currently supported in the latest Cartesi Rollups release:

Network NameChain ID
Ethereum Mainnet1
Optimism Sepolia11155420
Arbitrum Sepolia421614

Deploying on Mainnet or Public Testnet with a Cartesi Node running locally

  1. Build the dApp's back-end machine. To do this, run the following command from the directory of your dApp:
docker buildx bake machine --load --set *.args.NETWORK=<network>

Replace <network> with the name for your preferred network, written in the following way:

  • mainnet
  • sepolia
  • optimism
  • optimism_sepolia
  • arbitrum
  • arbitrum_sepolia

If you have PostgreSQL and Redis already installed on your system, you may encounter port conflicts when the Docker containers attempt to start services on ports that are already in use. To resolve these conflicts, edit the ports for Redis and PostgreSQL in the docker-compose.yml file located in the root directory of your dApp.

  1. Deploy the back-end to a corresponding Rollups smart contract by running:
export MNEMONIC='<user sequence of twelve words>'
export RPC_URL=<https://your.rpc.gateway>

The '<user sequence of twelve words>' sets your wallet's mnemonic, a sequence of twelve words used to generate private keys.

The <https://your.rpc.gateway> sets the URL for your preferred RPC gateway, a connection point for interacting with the Ethereum network. Replace it with a specific URL, such as<USER_KEY>.

  1. Submit a transaction to the Cartesi dApp Factory contract on the target network by executing the following command
DAPP_NAME=<example> docker compose --env-file ../env.<network> -f ../deploy-testnet.yml up

Replace <network> with the name for your preferred network.


The preferred network must be one that has the Rollups contracts deployed.

  1. Get the address of the dApp by running:
cat ../deployments/<network>/<example>.json

Replace <network> with the name of your preferred network and <example> with the name of your dApp. For example, cat ../deployments/sepolia/fortune.json.

The output will look similar to this:

"address": "Oxf3C97b309BfBf6bDD3436cC86dEdA6D149e2BD9D",
"blockHash": "0x8a895c94d23bf6aba465addc065f7bc205b637e4497ab79895541359620f05c8",
"blockNumber": 9361663,
"transactionHash": "0x154b7d30a6ffe728206cc56280cfb8c35b27cf6fdaca108fd400d38c4f6537cf"
  1. Stop the containers using ctrl+c then remove the containers and the volumes:
DAPP_NAME=<example> docker compose --env-file ../env.<network> -f ../deploy-testnet.yml down -v

Replace <network> with the name for your preferred network.

  1. Set a secure websocket endpoint for the RPC gateway (WSS URL) that the local Cartesi Node will use. The command depends on your preferred network. For example, for Sepolia and Alchemy, this will look as follows:
export WSS_URL=wss://<USER_KEY>
  1. Now we can start the local Cartesi Node:
DAPP_NAME=<example> docker compose --env-file ../env.<network> -f ../docker-compose-testnet.yml -f ./docker-compose.override.yml up

Replace <network> with the name for your preferred network.

  1. We can check the application status on Etherscan, for example, by searching by our address, such as Oxf3C97b309BfBf6bDD3436cC86dEdA6D149e2BD9D.

  2. Now let's send inputs to the dApp using the frontend-console application.

From the rollups-examples base directory, navigate to the frontend-console one:

cd frontend-console

Build the frontend console application:

yarn build

And send an input as follows:

yarn start input send --payload “test” --rpc <rpc-address> —address <dapp address>
  • Replace <rpc-address> with your preferred RPC address. You can obtain an address here.
  • Replace <dapp address> with the address obtained in step 4.

© 2023 Cartesi Foundation Ltd. All rights reserved.

The Cartesi Project is commissioned by the Cartesi Foundation.

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.