Deep Dive
1. Granite Upgrade Pre-Release (08 June 2026)
Overview: This is a pre-release version (v1.14.0-rc0) that prepares Flare's test networks for the upcoming Granite upgrade. It is not yet for the mainnet and primarily affects developers and node operators testing on Coston and Coston2.
The update aligns Flare's codebase with AvalancheGo v1.14.0. A key change is raising the minimum C-chain gas price (base fee floor) to 500 GWei on testnets, which could make test transactions slightly more expensive but helps simulate mainnet economic conditions more accurately. The activation is scheduled for June 11 on Coston and June 16 on Coston2.
What this means: This is neutral for FLR as it's a testnet update. It shows active development focused on long-term network security and performance. For users, it means the core technology is being rigorously tested before any mainnet changes, which is a good practice for stability.
(Flare Foundation)
2. Avalanche v1.13.0 Mainnet Integration (19 March 2026)
Overview: This stable release (v1.13.0) was a mandatory upgrade for all Flare and Songbird network nodes. It integrated the latest Avalanche protocol improvements, which include performance optimizations and changes to how validator data is reported.
The update removed the "StakeAmount" field from validator queries, requiring applications to use the "weight" field instead. Nodes had to upgrade by specific deadlines, with the Flare mainnet cutoff set for April 14, 2026.
What this means: This is bullish for FLR because it demonstrates the project's commitment to maintaining modern, secure, and efficient infrastructure. A successful mainnet upgrade reduces technical risk and ensures the network remains compatible with leading blockchain advancements.
(Flare Foundation)
3. Optional v1.12.1 Stability Release (24 February 2026)
Overview: This version (v1.12.1) was an optional but recommended update, focused on minor bug fixes and general stability improvements. It was backwards compatible with the previous v1.12.0.
Such releases are typical in software development cycles, addressing issues identified after a major version launch without introducing new features or breaking changes.
What this means: This is neutral for FLR. It reflects a mature development process where the team continuously refines the network. For users, it translates to a more reliable and smooth experience with fewer unexpected interruptions.
(Flare Foundation)
Conclusion
Flare's development trajectory shows a consistent pattern of integrating upstream Avalanche improvements, enforcing disciplined upgrade schedules, and refining network stability. The focus is clearly on building a robust foundation for its data and DeFi ecosystem. With a testnet pre-release already circulating, how will the successful deployment of the Granite upgrade influence the timeline for future mainnet features?