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.
v1.19.0 flagv1.20.0 flagNotes
--metrics-enable-metrics=false--metrics.metrics-enabled=falseSame default.
--metrics-enable-tracing=false--metrics.tracing-enabled=falseSame default.
--metrics-endpoint=localhost:4317--metrics.endpoint=localhost:4317Same default.
--metrics-insecure=false--metrics.insecure-endpoint=falseSame default.
--metrics-export-interval=10s--metrics.export-interval=10sNow parsed as a duration and used by metrics export.
--metrics-stuck-func=0m--metrics.stuck-func-timeout=0sSame effective disabled default.
--trace-flight-recorder-threshold=0--metrics.flight-recorder-threshold=0sSame effective disabled default.
--log-color=true--log-no-color=falseBehavior is inverted.
--chainstream-server=""--chainstream.server=""Same default.
--chainstream-buffer-cap=100--chainstream.buffer-cap=100Same default.
--chainstream-publisher-buffer-cap=100--chainstream.publisher-buffer-cap=100Same default.
--chainstream-enforce-keepalive=false--chainstream.enforce-keepalive=falseSame default.
--chainstream-min-client-ping-interval=30--chainstream.min-client-ping-interval=30Same default.
--chainstream-max-connection-idle=180--chainstream.max-connection-idle=180Same default.
--chainstream-server-ping-interval=60--chainstream.server-ping-interval=60Same default.
--chainstream-server-ping-response-timeout=40--chainstream.server-ping-response-timeout=40Same default.

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.
v1.20.0 flagDefaultNotes
--app-db-backend""Empty value falls back to the CometBFT DB backend.
--index-events[]Controls event indexing for CometBFT. Empty means all events are indexed.
--chain-idinjective-1New on start
--injective-websocket.address""Empty value disables the Injective websocket server.
--injective-websocket.max-open-connections0Unlimited.
--injective-websocket.read-timeout10sHTTP read timeout.
--injective-websocket.write-timeout10sHTTP write timeout.
--injective-websocket.max-body-bytes1000000Maximum allowed request body size.
--injective-websocket.max-header-bytes1048576Maximum allowed header size.
--injective-websocket.max-request-batch-size10Maximum JSON-RPC requests per batch.

Removed Flags

Remove these from startup scripts before running v1.20.0.
Removed flagPrevious defaultReplacement
--with-comettrueNone. In-process CometBFT startup is now the supported path.
--with-tendermintAlias for --with-cometNone.
--addresstcp://0.0.0.0:26658None for normal validator startup.
--transportsocketNone for normal validator startup.
--pruning-keep-every0None. Use --pruning, --pruning-keep-recent, and --pruning-interval.
--multistore-commit-syncfalseNone. This flag was registered in v1.19.0 but not consumed by Injective startup code.

Same Name, Changed Default or Type

If your deployment relied on the old default, set the old value explicitly.
Flagv1.19.0v1.20.0Suggested validator action
--minimum-gas-prices""160000000injPin explicitly if you require a different minimum gas price.
--pruningdefaultnothingPin --pruning=default if you do not want archive-style behavior.
--pruning-keep-recentuint64(0)string "0"Usually no action; type changed for config parsing.
--pruning-intervaluint64(0)string "0"Usually no action; type changed for config parsing.
--iavl-cache-sizeint(500000)uint64(781250)Pin old value if memory/cache sizing depends on it.
--api.enablefalse flag defaulttrue flag defaultPin --api.enable=false if the REST API must remain disabled.
--api.swaggerfalse flag defaulttrue flag defaultPin --api.swagger=false if Swagger must remain disabled.
--api.addresstcp://localhost:1317tcp://0.0.0.0:10337Pin old address if exposing the API is not intended.
--api.enabled-unsafe-corsfalse flag defaulttrue flag defaultPin false if CORS must remain disabled.
--json-rpc.apiunset / nil[eth, net, web3, inj]Pin explicitly if you require a different namespace set.
--json-rpc-debug.api[debug][eth, debug, inj]Pin explicitly if debug RPC is enabled and should stay debug-only.
--json-rpc.max-open-connectionsuint(0)int(0)Usually no action; value remains unlimited.
--json-rpc.return-data-limituint(512000)int64(512000)Usually no action; value is unchanged.
--json-rpc-debug.max-open-connectionsuint(0)int(0)Usually no action; value remains unlimited.
--json-rpc-debug.return-data-limituint(10485760)int64(10485760)Usually no action; value is unchanged.
--log-levelinfo""Pin explicitly if you require a specific log level.
--log-formatplain""Pin explicitly if you require plain or json.
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 June 5, 2026