Testnet Upgrade to v1.1.2

Documentation to upgrade from testnet v1.1.1 to v1.1.2

Upgrade Instructions using Cosmovisor

Cosmovisor must be set up, as instructed on the previous page, before proceeding with the following steps.

1. Check that the GRPC port set up in $HOMEDIR/config/client.toml matches the one in $HOMEDIR/config/config.toml.

${HOMEDIR}/config/client.toml

<!-- truncated -->
# <host>:<port> to Tendermint RPC interface for this chain
node = "tcp://localhost:26657"
<!-- truncated -->

${HOMEDIR}/config/config.toml

<!-- truncated-->
[rpc]
# TCP or UNIX socket address for the RPC server to listen on
laddr = "tcp://127.0.0.1:26657"
<!-- truncated-->

1. Verify that XRPUSDT exists in both the oracle price-feeder configuration files.

${HOMEDIR}/config/oracle_env_chainlink.yaml

urls:
  mainnet: !!str https://eth-mainnet.g.alchemy.com/v2/${YOUR_API_KEY}
  sepolia: !!str https://eth-sepolia.g.alchemy.com/v2/${YOUR_API_KEY}
  arbitrum: !!str https://arb-mainnet.g.alchemy.com/v2/${YOUR_API_KEY}
tokens:
  ETHUSDT: 0x5f4eC3Df9cbd43714FE2740f5E3616155c5b8419_mainnet
  WSTETHUSDT: 0xaaabb530434B0EeAAc9A42E25dbC6A22D7bE218E_sepolia
  USDCUSDT: 0x8fFfFfd4AfB6115b954Bd326cbe7B4BA576818f6_mainnet
  STETHUSDT: 0xCfE54B5cD566aB89272946F602D76Ea879CAb4a8_mainnet
  SOLUSDT: 0x4ffC43a60e009B551865A93d232E33Fce9f01507_mainnet
  # recently added
  XRPUSDT: 0xB4AD57B52aB9141de9926a3e0C8dc6264c2ef205_arbitrum

${HOMEDIR}/config/oracle_feeder.yaml

tokens:
  - token: ETHUSDT
    sources: chainlink
  - token: WSTETHUSDT
    sources: chainlink
  - token: USDCUSDT
    sources: chainlink
  - token: NSTETH
    sources: beaconchain
  - token: SOLUSDT
    sources: chainlink
  # recently added
  - token: XRPUSDT
    sources: chainlink

sender:
  path: $HOMEDIR/config # actual path not `homedir`
imua:
  chainid: imuachaintestnet_233-8
  appName: imua
  grpc: 127.0.0.1:9090
  ws: !!str ws://127.0.0.1:26657/websocket
  rpc: !!str http://127.0.0.1:26657

1. Download the new version of imuad to the current directory (which may be any location such as /tmp) and schedule the upgrade.

VERSION="1.1.2"
UPGRADE_NAME=$VERSION
UPGRADE_HEIGHT=13516420
wget -O imuad_${VERSION}.tar.gz "https://github.com/imua-xyz/imuachain/releases/download/v${VERSION}/imuachain_${VERSION}_$(uname -s)_$(uname -m | sed 's/x86_64/amd64/' | sed 's/aarch64/arm64/').tar.gz"
tar -xvzf imuad_${VERSION}.tar.gz
# Delete prior upgrade
rm -r ${HOMEDIR}/data/upgrade-info.json
# Cosmovisor step
cosmovisor --cosmovisor-config ${HOMEDIR}/cosmovisor/config.toml \
    add-upgrade ${UPGRADE_NAME} \
    bin/imuad \
    --upgrade-height ${UPGRADE_HEIGHT}

The chosen upgrade height is estimated to be breached around 6:30 am UTC on 22 May 2025. A more accurate countdown is available on our explorer.

Verify that the upgrade is created in the folder.

$HOMEDIR/data/upgrade-info.json

{
  "name": "1.1.2",
  "time": "0001-01-01T00:00:00Z",
  "height": 13516420
}

Node Stuck after Upgrade

1. Check which binary is running.

$(readlink -f /proc/$(pidof imuad)/exe) version

1. If is the old binary (1.1.1) check that the port configuration is accurate as described above.

   1. If it is corrected, restart the service and it will resync automatically.

AppHash after Upgrade

1. Run a rollback

systemctl stop cosmovisor-imuad
imuad rollback --home ${HOMEDIR}

1. Proceed with step 3 of the upgrade process.

Manual Upgrade

1. Run a rollback

systemctl stop cosmovisor-imuad
imuad rollback --home ${HOMEDIR}

1. Replace the binary with the newly downloaded one (1.1.2)

2. Start the node.