Skip to main content
This note summarizes injectived start flag changes between v1.19.0 and v1.20.0. All node runners should review their startup scripts, Helm charts, systemd units, or Kubernetes manifests before upgrading.
  1. Remove flags that no longer exist.
  2. Rename metrics and ChainStream flags if you use them.
  3. Pin any changed defaults if your node depends on the old behavior.

Long-Term Configuration Recommendation

Prefer setting persistent node configuration in the appropriate config file:
  • Use app.toml for application-level settings such as API, gRPC, JSON-RPC, pruning, metrics, ChainStream, EVM, and Injective websocket configuration.
  • Use config.toml for CometBFT settings such as P2P, RPC, consensus, and mempool configuration.
Startup flags should be treated as temporary overrides for testing, emergency operations, or short-lived rollout changes. They should not be used as the permanent replacement for values that belong in app.toml or config.toml. Keeping long-lived settings in config files makes validator behavior easier to audit, reduces upgrade risk when flags are renamed or removed, and keeps startup commands stable across releases. The template app.toml and config.toml files for the v1.20.0 tag can be found at the bottom of this file.

Renamed or Replaced Flags

Update any startup configuration that still uses the old flag names.

Added Flags (Informational. No change needed as these values will be picked from the config files as usual)

These flags did not exist as injectived start flags in v1.19.0.

Removed Flags

Remove these from startup scripts before running v1.20.0.

Same Name, Changed Default or Type

If your deployment relied on the old default, set the old value explicitly. For --api.*, note that generated Injective app.toml defaults were already set to enabled in v1.19.0; the notable change is the effective CLI flag default used by injectived start.

Template Config Files

app.toml

config.toml

Last modified on July 9, 2026