You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since Cosmos SDK v0.47 the genesis commands have all been grouped under a genesis top level sub-command. See issue and PR in Cosmos SDK repository.
It would be nice if gm could differentiate whether the chain binary has the genesis commands in the top level directly or under the genesis sub-command.
The text was updated successfully, but these errors were encountered:
Great point, thanks for opening the issue, Carlos. Most probably we'll do some kind of "fallback" implementation (as we did with the tendermint sub-command before). Unfortunately, we ran into network binaries that removed the --long parameter from the version command, hence it's not always trivial to query the SDK version used in the binary. (Injective, I'm looking at you...)
If you could strongly encourage downstream developers to keep the flags the core teams provide, please apply the pressure. ;)
Since Cosmos SDK v0.47 the genesis commands have all been grouped under a
genesis
top level sub-command. See issue and PR in Cosmos SDK repository.It would be nice if
gm
could differentiate whether the chain binary has the genesis commands in the top level directly or under thegenesis
sub-command.The text was updated successfully, but these errors were encountered: