TL;DR
AvalancheGo v1.15.0 schedules the Helicon upgrade for September 22. Mainnet activation is set for 15:00 UTC. Node operators need to upgrade before activation.Avalanche has put a date on its next mainnet upgrade.
AvalancheGo v1.15.0 schedules the Helicon network upgrade for September 22 at 15:00 UTC, with mainnet node operators being told to update before the activation time.
That gives validators only a short window to make sure their software is ready.
Helicon packages a new set of Avalanche Community Proposals into the network and also raises the plugin version used by Avalanche applications.
This Is A Mandatory Operator Upgrade
The release notes are unusually direct.
All mainnet nodes must upgrade before Helicon activates.
Plugins also need to move to the new compatible version.
That matters because protocol upgrades are different from ordinary application releases.
If consensus software changes and part of the validator set runs incompatible rules, nodes can disagree about what constitutes a valid block.
Networks therefore coordinate these upgrades carefully and give validators a fixed activation point.
Avalanche has done that here.
Helicon Continues Avalanche’s Regular Upgrade Cycle
Avalanche has increasingly used named upgrades to bundle protocol improvements into scheduled activation windows.
For developers, that makes the process easier to plan around.
Instead of individual features appearing unpredictably, software and protocol changes arrive behind a clearly defined network upgrade.
The September 22 date is therefore the main thing node operators need to know.
Users are unlikely to notice anything dramatic at the moment of activation, assuming validators update in time.
That is usually the sign of a successful network upgrade.
The engineering work happens underneath, while applications continue operating normally above it.
Still, anyone running Avalanche infrastructure has a concrete deadline now.
Helicon is not merely sitting in a proposal document.
It is scheduled into the AvalancheGo release and headed for mainnet.
Source: Ava Labs AvalancheGo release notes — https://github.com/ava-labs/avalanchego/releases/tag/v1.15.0
This article was written by the News Desk and edited by Samuel Rae.
This report is based on information released by Github. at Github