Skip to content

Question: rly tx link with custom client trusting periods for each client #1357

@ashishchandr70

Description

@ashishchandr70

Hi,

When creating the client/connection/channel in one go, I use rly tx link .... Now, this command does support the --client-tp flag so I use it like so:

rly tx link sagaxl --client-tp 403200s --override --src-port transfer --dst-port transfer --order unordered --version ics20-1

This does create the client and the connection and channel but the trusting_period for both clients is set to the same value, which is not often the case as different chains can require different trusting_period values based on their chain's unbonding_period

This is one of the client's config after the above command completes successfully:

# rly q client axelar 07-tendermint-768 --log-format json|jq .
{
  "client_state": {
    "@type": "/ibc.lightclients.tendermint.v1.ClientState",
    "chain_id": "ssc-testnet-1",
    "trust_level": {
      "numerator": "1",
      "denominator": "3"
    },
    "trusting_period": "403200s",
    "unbonding_period": "1814400s",
    "max_clock_drift": "600s",
    "frozen_height": {
      "revision_number": "0",
      "revision_height": "0"
    }
...<snipped>...

Most chains require that you set the trusting_period to 2/3 of the unbonding_period.

Am I using the command incorrectly or should there be an option to set this for chain_1 and chain_2 separately in the rly tx link command?

I know I can do this separately by rly tx client for each chain separately but if we have rly tx link, it should not be too much work to introduce a flag for both chains separately.

Thank you

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions