Injective has officially released the v1.20.3‑safeharbor.1 mainnet upgrade, marking the latest milestone in the protocol’s ongoing development. The update, tagged with the code commit `b994d6b`, brings new features and security patches that are critical for validators to adopt.
The "safe harbor" designation indicates that the upgrade is designed to be non‑disruptive for the network, allowing validators to transition without risking downtime or data loss. This is particularly important for nodes that operate continuously and handle high‑volume trading activity.
Both the core daemon (`injectived`) and the peg‑to‑chain bridge (`peggo`) have been rebuilt to version `v1.20.3‑safeharbor.1`. They are compiled with Go 1.26.4 on an amd64 architecture, ensuring compatibility with the latest Linux distributions. The binary release includes a shared library (`libwasmvm.x86_64.so`) that supports WebAssembly execution for smart contracts.
Docker images are available under the `injectivelabs/injective-core` repository. The `v1.20.3‑safeharbor.1` tag supports both `amd64` and `arm64` architectures, making it straightforward for validators running on ARM‑based servers to pull the correct image:
``` docker pull injectivelabs/injective-core:v1.20.3-safeharbor.1 ```
After pulling the image, validators can run the included binaries directly from the container or extract them for local deployment.
To verify that the correct binaries are in use, validators can execute:
``` injectived version peggo version ```
The output should display `v1.20.3‑safeharbor.1 (b994d6b)` for both tools, confirming the upgrade.
A detailed, step‑by‑step upgrade guide is available in the official documentation at https://docs.injective.network/infra/validator-mainnet/canonical-chain-upgrade-v1.20.3-safeharbor.1. Validators are encouraged to review the guide before initiating the upgrade to ensure a smooth transition.
By adopting this release, validators will benefit from the latest performance improvements and security fixes, helping to maintain the robustness and reliability of the Injective mainnet.