Deep Dive
1. Mandatory Daemon v8.0.0 (8 July 2025)
Overview: Critical update aligning Flux’s infrastructure for its v9 fork and PoUW v2.
The release removes block reward halvings, phases out 32-bit system support, and introduces AMD64/ARM64/Windows builds. It enhances chain analysis via optional block height tracking in getchaintips
and migrates CI/CD pipelines to GitHub Actions. Arcane Mode enables advanced testing for developers.
What this means: This is bullish for FLUX because it streamlines node operations for future upgrades, reduces fragmentation, and incentivizes participation with fixed rewards (14 FLUX/block). Node operators must update to avoid downtime.
(Source)
2. PoUW Transition (11 July 2025)
Overview: Flux replaces GPU mining with node-powered workloads for real-world applications.
PoUW v2 rewards FluxNodes running AI, dApps, or data-processing tasks instead of traditional mining. Block production quadruples, distributing rewards more frequently. A 0.5 FLUX/block allocation funds ecosystem development.
What this means: This is neutral-to-bullish for FLUX as it reduces energy waste and aligns incentives with utility, but node operators must adapt to workload-based rewards.
(Source)
3. Infrastructure Overhaul (13 August 2025)
Overview: Hard deadline for node operators to upgrade to v8.0.0 by 14 August 2025.
The fork enforces compatibility with PoUW v2, requiring nodes to run updated software to stay in consensus. Non-compliant nodes risk losing rewards and network access.
What this means: This is neutral for FLUX as it ensures network stability but pressures slower operators to act swiftly.
(Source)
Conclusion
Flux’s codebase shifts toward sustainable, utility-driven decentralization with PoUW v2 and stricter node requirements. How will the transition impact node operator participation and FLUX’s valuation as compute demand grows?