Skip to main content

Upgrade the ICS 20 transfer channel

Start the relayer​

We start the relayer:

hermes --config config.toml start

Initiate the upgrade​

The initiation of the upgrade process is authority-gated, and thus the upgrade will begin when a governance proposal passes. There a couple of ways in which the initiation can be triggered.

With upgrade-channels CLI​

We have a CLI command that streamlines the submission of the governance proposal to initiate the upgrade. By default the CLI will upgrade all channels on transfer port with the provided channel version string. Both the port and the channels to be upgraded can be customized with CLI flags. To keep it simple, and since we only have one ICS20 channel, for this example the CLI command would look like the following:

simd tx ibc channel upgrade-channels "{\"fee_version\":\"ics29-1\",\"app_version\":\"ics20-1\"}" --deposit 10stake

After the governance proposal is submitted, the user can vote for it and wait that it passes, but these steps are shown in more detail in the next section.

With submit-proposal CLI​

And alternative way of submitting the proposal is using x/gov module's CLI command. The contents of the governance proposal are:

{
  "title": "Channel upgrade init",
  "summary": "Channel upgrade init",
  "messages": [
    {
      "@type": "/ibc.core.channel.v1.MsgChannelUpgradeInit",
      "signer": "cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn",
      "port_id": "transfer",
      "channel_id": "channel-0",
      "fields": {
        "ordering": "ORDER_UNORDERED",
        "connection_hops": ["connection-0"],
        "version": "{\"fee_version\":\"ics29-1\",\"app_version\":\"ics20-1\"}"
      }
    }
  ],
  "metadata": "AQ==",
  "deposit": "100005stake"
}

where cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn is the address of the governance module on chain1. You can retrieve the account of the governance module running the following command:

simd query auth module-account gov --node http://localhost:27000

The upgrade will modify the channel version to include the fee version. We submit the proposal:

simd tx gov submit-proposal ./proposal_upgrade_channel.json \
--from $VALIDATOR_CHAIN1 \
--chain-id chain1 \
--keyring-backend test \
--home ../../gm/chain1 \
--node http://localhost:27000

Now we vote for the proposal:

simd tx gov vote 1 yes \
--from $VALIDATOR_CHAIN1 \
--chain-id chain1 \
--keyring-backend test \
--home ../../gm/chain1 \
--node http://localhost:27000

And we wait for the voting period to end (approximately 3 minutes). Once it ends we can check that the proposal has passed (i.e. the status has changed from PROPOSAL_STATUS_VOTING_PERIOD to PROPOSAL_STATUS_PASSED):

simd q gov proposals --node http://localhost:27000
pagination:
  total: "1"
proposals:
- deposit_end_time: "2024-01-27T21:29:52.430508Z"
  final_tally_result:
    abstain_count: "0"
    no_count: "0"
    no_with_veto_count: "0"
    yes_count: "1000000"
  id: "1"
  messages:
  - type: /ibc.core.channel.v1.MsgChannelUpgradeInit
    value:
      channel_id: channel-0
      fields: {}
      port_id: transfer
      signer: cosmos10d07y265gmmuvt4z0w9aw880jnsr700j6zn9kn
  metadata: AQ==
  proposer: cosmos1vdy5fp0jy2l2ees870a7mls357v7uad6ufzcyz
  status: 3
  submit_time: "2024-01-25T21:29:52.430508Z"
  summary: Channel upgrade init
  title: Channel upgrade init
  total_deposit:
  - amount: "100005"
    denom: stake
  voting_end_time: "2024-01-25T21:32:52.430508Z"
  voting_start_time: "2024-01-25T21:29:52.430508Z"

Now we wait for the relayer to complete the upgrade handshake.

Check upgrade completed​

Once the handshake has completed we verify that the channel has successfully upgraded:

simd q ibc channel channels --node http://localhost:27000
channels:
- channel_id: channel-0
  connection_hops:
  - connection-0
  counterparty:
    channel_id: channel-0
    port_id: transfer
  ordering: ORDER_UNORDERED
  port_id: transfer
  state: STATE_OPEN
  upgrade_sequence: "1"
  version: '{"fee_version":"ics29-1","app_version":"ics20-1"}'
height:
  revision_height: "135"
  revision_number: "0"
pagination:
  next_key: null
  total: "0"

The channel version on chain1 is what we expect.

simd q ibc-fee channels --node http://localhost:27000
fee_enabled_channels:
- channel_id: channel-0
  port_id: transfer
pagination:
  next_key: null
  total: "0"

As we expect there is one incentivized channel.

simd q ibc channel channels --node http://localhost:27010
channels:
- channel_id: channel-0
  connection_hops:
  - connection-0
  counterparty:
    channel_id: channel-0
    port_id: transfer
  ordering: ORDER_UNORDERED
  port_id: transfer
  state: STATE_OPEN
  upgrade_sequence: "1"
  version: '{"fee_version":"ics29-1","app_version":"ics20-1"}'
height:
  revision_height: "138"
  revision_number: "0"
pagination:
  next_key: null
  total: "0"

The channel version on chain2 is also what we expect.

simd q ibc-fee channels --node http://localhost:27010
fee_enabled_channels:
- channel_id: channel-0
  port_id: transfer
pagination:
  next_key: null
  total: "0"

As we expect there is one incentivized channel as well on chain2.

From now ICS 20 packets sent on this channel can be incentivized.