Avalanche Sets Sept. 22 Mainnet Deadline for Helicon Node Upgrade

Avalanche's mainnet upgrade deadline for the Helicon network upgrade now has a date. AvalancheGo v1.15.0's release notes, published by Avalanche Developers on Sept. 8, set Mainnet activation for 11 AM ET (3 PM UTC) on September 22, 2026, and state plainly: "All Mainnet nodes must upgrade before 11 AM ET, September 22nd 2026."

Descout's earlier guide to what Helicon changes on the C-Chain and P-Chain, published at 13:00 UTC that same day, recorded Mainnet activation as "Not yet scheduled" - the status read Pending, with no date attached. Eight hours and forty-six minutes later, at 21:46 UTC, @AvaxDevelopers announced the v1.15.0 release. Avalanche's builder-hub docs have since updated: the activation-status table now lists Mainnet as "Scheduled," against the same September 22, 2026, 15:00 UTC date.

"Nodes not running a Helicon-capable version by then won't be able to follow the network," @AvaxDevelopers wrote in the announcement. Avalanche's docs describe the same outcome in different words: a node "still on an older release when Helicon activates will not follow the upgraded chain." That specific sentence does not appear in the release notes themselves - their language addresses a narrower, separate problem, covered below.

Mainnet nodes need AvalancheGo v1.15.0 - a different build from v1.15.0-fuji, the release that activated Helicon on the Fuji testnet on July 28. Per Avalanche's docs, that Fuji-only build "refuses to start against a Mainnet configuration, and does not support C-Chain state sync once Helicon is active." That limitation is scoped to the Fuji build and does not carry over unchanged to the Mainnet release: the v1.15.0 release notes' C-Chain State Sync section instead says state sync "is not supported immediately around the Helicon activation" and that a node "that is state syncing when Helicon activates may stall." After activation, the same notes list specific operating limits rather than a blanket ban: restarting a node mid-sync restarts the sync from the beginning, disabling state sync partway through can trigger an unrecoverable FATAL error, and a node running the Firewood state scheme cannot state sync at all - it must set state-sync-enabled to false or the node will shut down with a FATAL error.

Once Mainnet activates, Helicon turns on six Avalanche Community Proposals at once - Continuous Execution and a validator-voted C-Chain gas price, plus four Primary Network staking changes to uptime, minimum duration and reward rates - which Descout's earlier guide covers mechanic by mechanic. What changed with this release is the date: node operators now have a fixed window, Sept. 8 to Sept. 22, to comply before Mainnet enforces it.