Skip to main content


Now that we've registered the RollApp on the Dymension Hub we can proceed to begin running the RollApp.


If you would like to run your RollApp in a production settings, please skip this section and head over to the run in production section.


The following command abstracts some of the components required for running an IBC-enabled RollApp. For advanced users or for those interested in learning about the different components of an active RollApp please proceed to the advanced guide .

To start the RollApp run the following command:


roller run is for development process and once the terminal output is closed the RollApp will stop running. For a production-grade RollApp please refer to the production guide.

roller run

Enabling IBC in all channels can take up to an hour in which the developer is expected to see starting.... After which an active status will appear with the respective source IBC channels. IBC channels are created to facilitate applications such as token transfers from the RollApp to other ecosystems.

During the Run process a RollApp with an IBC connection to the Dymension Hub is started. A status table will appear with information about the RollApp and IBC relayer. Developers should see an output with useful information such as this:

  • Height: latest RollApp block height
  • Hub: latest RollApp block height that was published to the Dymension Hub
  • Port 8545: EVM RPC provides a RPC gateway for publishing EVM smart contracts (if applicable)
  • Port 26657: Node RPC provides a RPC gateway for requests to the node
  • Port 1317: Rest end-point provides a REST gateway for requests to the node
  • Log file path: is the PATH to the RollApp logs

Let's continue and interact with the running IBC-enabled RollApp.