Canonical Chain Upgrades

Verify release versions

Releases on Github

If you would like to verify injectived or peggo version numbers via Docker, follow the instructions in the verify-injective-release code snippet.

This is useful if you are on an operating system other than Linux, and would like to independently verify the binaries in each release.

For example, for v1.16.1, it should produce the following output:

injectived version
Version v1.16.1 (8be67e82d)
Compiled at 20250802-1910 using Go go1.23.9 (amd64)
peggo version
Version v1.16.1 (8be67e82d)
Compiled at 20250802-1913 using Go go1.23.9 (amd64)

Releases on Docker

These are more straightforward, as each binary needs a single command.

For injectived, use the following command:

docker run -it --rm injectivelabs/injective-core:v1.16.1 injectived version

This should produce output similar to:

Version v1.16.1 (8be67e8)
Compiled at 20250802-1909 using Go go1.23.9 (arm64)

For peggo, use the following command:

docker run -it --rm injectivelabs/injective-core:v1.16.1 peggo version

This should produce output similar to:

Version v1.16.1 (8be67e8)
Compiled at 20250802-1911 using Go go1.23.9 (arm64)

Note that you should replace v1.16.1 in the commands above with your intended Injective release version number.

Checking for matches

Note that the output from the above commmands contain the following in addition to the version numbers (e.g. v1.16.1):

• The binary release hashes (e.g. 8be67e82d)
• The compiled time stamp (e.g. 20250802-1910)
• The compiler (e.g. Go go1.23.9 (amd64))

You can verify that these match the values stated in the Injective chain releases page on Github.

Deprecated flags

Deprecated statsd flags (v1.19.0+)

The following injectived start flags are no longer supported as of v1.19.0 and must be removed from your start command or systemd unit file before upgrading:

statsdAgent, statsdEnabled, statsd-prefix, statsd-address, statsd-stuck-func, statsd-tracing-enabled, statsd-profiling-enabled, trace-recorder-threshold

If any of these flags are present, injectived will fail to start after the upgrade. An external validator on testnet encountered this issue informally — remove these flags before running injectived start on the new version.