Avalanche activated the Helicon network upgrade on its mainnet on September 22, 2026, at 11 AM ET, a release that the Avalanche Foundation's development stack delivered through AvalancheGo v1.15.0 and that project data claims makes block verification up to 100 times faster.

Helicon is a coordinated protocol change, not an incremental patch. It bundles six Avalanche Community Proposals (ACPs) into a single activation, covering transaction processing, gas pricing mechanics and validator reward rules. Every mainnet node operator had to adopt the latest protocol version before activation, and the upgrade discontinued certain legacy RPC methods on the C-Chain.

Consensus split from execution

The centerpiece is Continuous Execution, formally designated ACP-194. The change decouples consensus from execution on the C-Chain, the Ethereum Virtual Machine-compatible instance at the core of Avalanche's smart contract activity. Previously the chain handled block agreement and transaction execution in lockstep; under the new model, transactions are processed asynchronously after consensus.

The operational consequence is throughput. Post-launch data shows per-block capacity has roughly doubled, giving the C-Chain 2x more headroom per block. Early reports also indicate the chain ran below its gas target for the first time in months — a sign that congestion pressure on the network has eased, at least in the immediate aftermath of activation.

Gas pricing moves to validators

Helicon also reworks fee mechanics under ACP-283. The minimum gas price on the C-Chain is no longer a fixed parameter. It now follows a dynamic model governed by validators, handing node operators direct influence over the network's cost floor.

The shift is substantial. Post-upgrade observations point to a roughly 100-fold change in the effective gas fee floor, illustrating how much pricing power the new mechanism transfers to the validator set. For application developers, the change introduces a different variable into cost planning: fee floors are now an emergent property of validator behavior rather than a protocol constant.

Staking economics rewritten

The upgrade also rewrites the rules for network participants. The minimum staking duration for validators drops from 336 hours, or 14 days, to 48 hours, or 2 days. Validators additionally gain auto-renewing staking, allowing a staking period to roll over automatically rather than requiring a manual restart at each expiry.

The lower entry barrier comes paired with a stricter performance requirement. For new staking periods, validators must maintain at least 90% uptime to qualify for rewards. The combined effect should make capital less locked up for operators while raising the operational bar for those running unreliable hardware.

Two months of testnet runway

Helicon did not reach mainnet cold. The upgrade first activated on Fuji, Avalanche's testnet, on July 28, 2026, with no significant issues reported, giving developers and node operators nearly two months to test the new execution model and staking rules before mainnet deployment.

The release also illustrates how Avalanche ships protocol changes: improvements move through the ACP process as individual proposals, then get grouped into named network upgrades that every node must adopt together.

Operational consequences

For developers building on the C-Chain, Continuous Execution is the component with the widest implications. Doubled per-block headroom and asynchronous processing should reduce congestion-driven slowdowns during demand spikes, a structural change to how the chain behaves under load rather than a marginal tuning.

For validators, the shorter minimum commitment lowers the barrier for new entrants. The 90% uptime requirement simultaneously raises the cost of running substandard infrastructure — an operator whose hardware misses the threshold forfeits rewards for that staking period.

The most concrete near-term risk sits with infrastructure. Node operators who missed the mandatory upgrade, and applications still calling the deprecated RPC methods, are the parties most likely to experience friction in the weeks following activation.

The near-term watch items are empirical: whether the doubled per-block capacity and reduced gas consumption hold under sustained demand, and how validators exercise their new authority over the fee floor as network usage recovers.