IBC tutorial fails when running ignite relayer connect

[jeronimoalbi]

Description

Related to #2673

The relayer fails when following the IBC tutorial.

The ignite relayer connect command returns the error message:

input data is not a valid secp256k1 private key

The error message is the result of calling the @confio/relayer through nodetime.

To reproduce

Steps to reproduce the behavior:

1. Checkout Ignite CLI feat/sdk-ibc-upgrade branch.
2. Follow the IBC tutorial until the point where the relayer is configured.
3. Make sure that the planet/go.mod file uses your local Ignite CLI repository (cli path must match your local path):
   replace github.com/ignite/cli => ../ignite/cli
4. Run ignite relayer connect.

What version are you using?

Ignite CLI version:	development
Ignite CLI build date:	2022-08-08T09:16:41
Ignite CLI source hash:	3ba35937444341317129bde5956460b75d972b59
Your OS:		darwin
Your arch:		arm64
Your go version:	go version go1.18.1 darwin/arm64
Your uname -a:		Darwin Protostar.home 21.4.0 Darwin Kernel Version 21.4.0: Fri Mar 18 00:46:32 PDT 2022; root:xnu-8020.101.4~15/RELEASE_ARM64_T6000 arm64 arm Darwin
Your cwd:		/Users/jeronimoalbi/Projects/ignite/cli
Is on Gitpod:		false

[lumtis]

You are mentioning

Related to #2673

But your ignite version shows your are on develop branch which doesn't include 0.46. Did you run ignite version from feat/sdk-ibc-upgrade?

[jeronimoalbi]

But your ignite version shows your are on develop branch which doesn't include 0.46. Did you run ignite version from feat/sdk-ibc-upgrade?

Thanks for the heads up @lubtd!

I just checked and I am using a binary that I compiled for the 3ba3593 which at the moment is the last commit in the feat/sdk-ibc-upgrade branch.

It is true that "Ignite CLI version" shows "development" which might be misleading. Maybe is not a bad idea to change the build to include the branch next to the version:

Ignite CLI version: development (feat/sdk-ibc-upgrade)

[jeronimoalbi]

Fixed by #2729