Parametrize chain type via configuration file #1630
Labels
E: non-cosmos
External: related to non-Cosmos chains
I: CLI
Internal: related to the relayer's CLI
I: configuration
Internal: related to Hermes configuration
O: usability
Objective: cause to improve the user experience (UX) and ease using the product
Milestone
Crate
ibc-relayer
andibc-relayer-cli
Summary
We're adapting the
relayer
andibc
modules to support interoperability with non-SDK chains. In this context, we may want to allow operators to select the type of chain which they are configuring.For example,
would turn into
Problem Definition
I think there are two problems we're having at the moment.
https://github.com/informalsystems/ibc-rs/blob/02776c879b203510f9d1b38b9f643639221b163c/relayer-cli/src/cli_utils.rs#L69-L70
This will have to change, and it's not clear yet how to parametrize it dynamically. Specifying the chain type in the
config.toml
could be a solution.config.toml
:https://github.com/informalsystems/ibc-rs/blob/02776c879b203510f9d1b38b9f643639221b163c/config.toml#L228-L232
The proof specification that a network uses is a low-level concern, yet it is very important when creating / manipulating IBC clients and the corresponding proofs. It's unlikely that relayer operators know how to configure the proof specs, and unclear if this should be a configuration option, since the proof type is a property of the chain type.
Acceptance Criteria
proof_spec
option in the config.toml with a higher level option calledtype
(or similar name)Related to: #1318 and cosmos/ibc-rs#67
For Admin Use
The text was updated successfully, but these errors were encountered: