Deep Dive
1. Mainnet Upgrade to Avalanche 1.12.0 (11 November 2025)
Overview: This mandatory update upgraded Flare's core software to align with Avalanche version 1.12.0. It introduced Ethereum's Cancun/Dencun features to the network, which directly improves the experience for developers and users.
The upgrade included new operations codes (opcodes) like MCOPY for faster memory handling and TSTORE/TLOAD for cheaper temporary data storage. It also enabled dynamic staking fees on the P-chain, adjusting costs based on network usage. All node operators were required to upgrade by specific deadlines, with the main Flare network cutoff set for 2 December 2025.
What this means: This is bullish for FLR because it makes the network more efficient for decentralized applications. Users benefit from potentially lower transaction fees and developers can build more complex, scalable apps, which could drive greater usage and demand for FLR.
(Source)
2. Optional Update to Avalanche 1.11.13 (23 October 2025)
Overview: This release updated the codebase to Avalanche 1.11.13. It was labeled as optional but encouraged, meaning node operators could upgrade for improved performance and security without the urgency of a hard fork deadline.
The update focused on under-the-hood refinements and bug fixes from the upstream Avalanche project. It maintained full backwards compatibility with the previous v1.11.0, ensuring a smooth upgrade path.
What this means: This is neutral for FLR as it represents ongoing maintenance. It shows the development team is actively refining network stability and security, which is essential for long-term reliability but doesn't directly introduce new user features.
(Source)
3. Mandatory Upgrade to Avalanche 1.11.0 (26 June 2025)
Overview: This was a critical network upgrade that moved the core software to Avalanche 1.11.0. Node operators on the Songbird and Flare mainnets had to install this version by July and August 2025, respectively, to remain in consensus.
The update brought the latest core improvements from the Avalanche platform to Flare's infrastructure. Failure to upgrade by the deadline would have caused nodes to fall off the network.
What this means: This was bullish for FLR at the time because it demonstrated disciplined network governance and a commitment to keeping core infrastructure modern and secure, which is a foundational requirement for ecosystem growth.
(Source)
Conclusion
Flare's recent codebase history shows a consistent pattern of integrating upstream Avalanche improvements, focusing on core infrastructure stability, Ethereum compatibility, and preparing the network for more sophisticated DeFi activity. How will these technical foundations translate into increased developer adoption and on-chain activity in 2026?