At present, genesis files in Roller are generated through manual execution of scripts and loading environmental variables, which can lead to errors. A proposed enhancement for roller config init is to automate this genesis files creation process, resulting in a more efficient and reliable setup.

Generate the configuration to run a rollapp as detailed in the ADR

The roller register command needs to be enhanced to support registration of a rollapp and a sequencer to the Dymension hub.

Currently the cmd to install roller is:
curl -L https://github.com/dymensionxyz/roller/releases/download/v0.0.0/install.sh | bash

I believe this install cmd will be marketed in various places, hence a branded domain is necessary:

I propose the following domain:
roller.dymension.xyz/install

which will be marketed:

curl -L https://roller.dymension.xyz/install | bash

https://www.notion.so/dymension/Command-Line-Interface-674c01a2fe954c1bb8e1560d55c35210?pvs=4#456c15b9a8294ef3ad4ddeb3d5d60ef9

Add an optional "hub" command with "devnet" and "35-c" options

Getting an error on initial roller config init command when the .roller directory does not exist.

Create a cli root command to show general information about the CLI tool

Currently, Roller stores config files in ~/.roller by default. This task involves introducing a --home flag to allow users to specify a custom directory for Roller configuration files. This will enhance user flexibility and support various use cases.

Generate the keys necessary to run a rollapp as detailed in the ADR

it contains a fix required for dymint to be able to track timedout txs

As it stands, relayer configuration in Roller is performed manually via scripts and loading environmental variables. This process can be cumbersome and lead to errors. We propose enhancing roller config init to automatically generate these configuration files, making the setup process more efficient and reliable.

To ensure the reliability and correct functioning of the 'roller config init' command, it's crucial to implement comprehensive integration tests. These tests will validate the command's performance in different scenarios and with various inputs, thus ensuring its robustness and reliability in a variety of use cases.

New terminal, rollapp is registered on the hub and previously configured.

cmd: roller sequencer start:

The roller register command should be robust in handling reruns. This includes checking if the current Dym address was used for rollapp registration in case of a rerun with an already registered rollapp id. If the rollapp is already registered, the user should be notified and the sequencer should be registered if it hasn't been done already. If the rollapp id is in use by another rollapp, the command should alert the user and prompt for a new rollapp id. This issue will focus on implementing idempotency to ensure consistent outcomes upon re-execution of the roller register command.

On roller relayer start and a 5 minute wait after funding the addresses I received the following exit status 1 response:

ts=2023-06-19T17:12:52.977081Z lvl=error msg="Error sending messages" src_chain_id=internal-devnet dst_chain_id=shaolin_9000_1 src_client_id=01-dymint-23 dst_client_id=07-tendermint-0 error="error sending messages: rpc error: code = Unknown desc = rpc error: code = Unknown desc = failed to execute message; message index: 0: connection handshake open ack failed: connection state is not INIT (got STATE_OPEN): invalid connection state [cosmos/ibc-go/[email protected]/modules/core/03-connection/keeper/handshake.go:183] With gas wanted: '18446744073709551615' and gas used: '123345' : unknown request"
ts=2023-06-19T17:12:54.628088Z lvl=info msg="Successful transaction" provider_type=cosmos chain_id=internal-devnet gas_used=157452 fees= fee_payer=dym12cm8f6gg7wy6ydg8s9hnkzq29nwjcja76ztktv height=1050904 msg_types=/ibc.core.client.v1.MsgUpdateClient,/ibc.core.connection.v1.MsgConnectionOpenConfirm tx_hash=CE3CFD7BF6B08B8570D9CD16F54A36AB5D46B6C93CD7D3FAB2100843245EE85C
ts=2023-06-19T17:12:55.140341Z lvl=info msg="Connection handshake termination candidate" chain_id=internal-devnet client_id=01-dymint-23 termination_client_id=01-dymint-23 observed_client_id=01-dymint-23 termination_counterparty_client_id=07-tendermint-0 observed_counterparty_client_id=07-tendermint-0
ts=2023-06-19T17:12:55.140406Z lvl=info msg="Found termination condition for connection handshake" chain_id=internal-devnet client_id=01-dymint-23
💈 exit status 1

The following attempt at this worked successfully.