Denis Fadeev

Consensus version has been set to 1. https://github.com/ignite/cli/blob/7c836df5ec90e9a7abd15a114cd6ec2b10969a27/ignite/templates/module/create/stargate/x/%7B%7BmoduleName%7D%7D/module.go.plush#L153

wdyt about following the `transfer` module pattern and having a separate `IBCModule` type: https://github.com/cosmos/ibc-go/blob/v5.0.0-beta1/modules/apps/transfer/ibc_module.go#L21-L30 and `AppModuleBasic` type: https://github.com/cosmos/ibc-go/blob/v5.0.0-beta1/modules/apps/transfer/module.go#L33 This is how it could potentially look like: https://github.com/fadeev/templateIBCv4/tree/master/x/foobar

wdyt about adding interchain accounts to the default template?

I agree that the process of upgrading chains is needlessly difficult when we have dependencies on Ignite and SPN in the chain's source code. That being said, dumping 600 lines...

@lubtd also, the query cmd namespace. ```go func queryCommand() *cobra.Command { cmd := &cobra.Command{ Use: "query", Aliases: []string{"q"}, Short: "Querying subcommands", DisableFlagParsing: true, SuggestionsMinimumDistance: 2, RunE: client.ValidateCmd, } cmd.AddCommand( authcmd.GetAccountCmd(),...

After we have an open discussion about this, maybe we can first remove `cosmoscmd`, then try to add a package to Cosmos SDK repo that could abstract the hairy bits...

What a binary essentially has is a top-level list of commands. Most of these commands are exactly the same between chains, however, leaving an option for a developer to overwrite...

Can't reproduce. macOS Monterey Version 12.3.1 Chip: Apple M1 Pro

This is a great idea! Would it make sense to keep the documentation about modules in the code or right next to the code to make sure that the docs...

I propose we move this section in the "Installing Ignite CLI" section (next to the write permissions one). Otherwise, looks good, I think.