cli icon indicating copy to clipboard operation
cli copied to clipboard

Ignite is a CLI tool and hub designed for constructing Proof of Stake Blockchains rooted in Cosmos-SDK

Results 355 cli issues
Sort by recently updated
recently updated
newest added

Ignite scaffold changes the code if the command is done or not. The command will apply some changes if it throws an error or the user cancels the scaffold. Consider...

type:feature
component:scaffold

We might by default list all requests and add a flag to filter by one of these: pending, approved, rejected. This feature requires adding filtering support in SPN. tracked by:...

network

so we wouldn't need an `--address-prefix` flag. related to https://github.com/ignite-hq/cli/pull/2541#discussion_r885227198.

investigation

We need to find proper packages to have support for them an also rename `pkg/jsonfile` to something generic. One of the use case for it is in the chain service:...

enhancement

If spn network is launched with validators with hidden peer. The network relies on validators who have public peers. If they go offline, network is stopped. It would be nice...

network
research

as we discussed before, we can add a cache for the genesis from URL: https://github.com/ignite-hq/cli/pull/2228#discussion_r887847299

request
network

**Describe the bug** I attempted to scaffold a new message and encountered the error `invalid checksum` **To reproduce** 1. Install latest Ignite CLI (at the moment v0.21.2) 2. Attempt to...

investigation
scaffold

Depends on https://github.com/tendermint/spn/issues/790 **Is your feature request related to a problem? Please describe.** Mainnets can have special allocations: shares of the campaign allocated for a specific purposes other than redeemed...

component:network
needs-triage

**Is your feature request related to a problem? Please describe.** For mainnet chain, a token distribution might be already defined in the initial genesis for the chain with special allocations....

type:request
component:network
needs-triage

If you use `tcp://0.0.0.0:26657` instead `http://0.0.0.0:26657` stucks the relayer CLI UI ```shell ignite relayer configure -a -r --ordered \ --source-account "alice" \ --source-rpc "tcp://0.0.0.0:26657/" \ --source-faucet "tcp://0.0.0.0:4500/" \ --source-port "monitoringc"...

type:bug
report
needs-triage