Avalanche activated Helicon on mainnet with six proposals at once
Serguey Asael Shinder2 min readThe Helicon network upgrade activated on Avalanche Mainnet at 11 AM ET (3 PM UTC) on Tuesday 22 September 2026, scheduled by the avalanchego v1.15.0 release. Every mainnet node had to upgrade before that moment, and the plugin version moved to 46, requiring all plugins to update to stay compatible.
Helicon activates six Avalanche Community Proposals together:
| ACP | What it does | |---|---| | 194 | C-Chain async execution | | 236 | Auto-renewed staking | | 267 | Validator uptime requirements increase | | 273 | Reduce minimum validator staking duration | | 283 | Dynamic minimum C-Chain gas price | | 285 | Reduce minimum consumption rate |
Separately, Subnet-EVM can now set the initial ACP-226 minimum block delay at genesis through InitialMinDelayMS in the chain config. The release notes also flag that C-Chain state sync is not supported immediately around the upgrade.
The part worth noticing
Four of the six are about validator economics, and they pull in opposite directions on purpose. Reducing the minimum staking duration (273) and auto-renewing stake (236) both lower the friction of being a validator — shorter commitment, no manual re-staking. Raising the uptime requirement (267) and reducing the minimum consumption rate (285) push the other way: easier to join, harder to coast once you are in, and less reward for doing the minimum.
Read together that is a deliberate shift from recruiting validators to selecting them. A network that has enough participants stops optimising for entry and starts optimising for quality, and this upgrade is what that transition looks like in parameters.
ACP-194, C-Chain async execution, is the one with consequences beyond staking. Decoupling execution from consensus is the change that raises the ceiling on throughput, and it is also the change most likely to surprise tooling that assumed a block's results were final the moment the block was. Anyone running indexers or bridges against the C-Chain has reason to re-read that proposal rather than the release notes.
⚠️ We are reporting an activation, not a performance result. No throughput or latency figures are published here, and the state-sync caveat suggests the operational picture around the upgrade is still settling.