Deep Dive
1. Mainnet 18 Upgrade (11 June 2026)
Overview: This upgrade improves the network's data feeds and makes operations more reliable for compute providers. It ensures existing user deployments continue running without interruption.
The activation introduced three key changes. Oracle v2 replaces block-height references with wall-clock timestamps, making price queries and staleness detection more accurate and reliable. The Resource Reclamation feature (AEP-82) gives providers a negotiated grace period before terminating a lease, preventing immediate closure and allowing for smoother transitions. Finally, a fix ensures the EventOrderClosed properly fires when a deployment closes, correcting a previous bug in market order events.
What this means: This is bullish for AKT because it makes the underlying infrastructure more robust and reliable. Users benefit from more accurate pricing data, while providers can operate with greater stability, which should encourage more supply on the network.
(Source)
2. Burn-Mint Equilibrium Launch (23 March 2026)
Overview: This hard fork, dubbed "Project Twilight," fundamentally changed AKT's tokenomics by directly linking network usage to token scarcity.
The upgrade implemented the Burn-Mint Equilibrium (BME) model. When users purchase cloud compute, a portion of the AKT used for payment is permanently burned. Simultaneously, stable, internal "Akash Compute Tokens" are minted for settlement. This creates a direct deflationary mechanism tied to utility. The upgrade also added WebAssembly (WASM) support, enabling developers to build programmable dApps on Akash's decentralized cloud.
What this means: This is bullish for AKT because it transitions the token's value from pure speculation to being driven by actual network demand. Increased usage now directly reduces supply, potentially supporting the token's price over the long term.
(Source)
3. Mainnet 14 Upgrade (28 October 2025)
Overview: This was a foundational upgrade that modernized the network's core software, setting the stage for faster future innovation.
The upgrade successfully migrated Akash to Cosmos SDK v0.53. This shift cleared out legacy code barriers that were limiting development speed. For validators and node operators, it was a mandatory upgrade to stay in sync with the network.
What this means: This is neutral to bullish for AKT as it was a necessary technical step. It didn't add user-facing features but improved the long-term health and development velocity of the entire project, allowing the team to build newer upgrades like Mainnet 18 more efficiently.
(Source)
Conclusion
Akash Network's development trajectory shows a clear focus on strengthening core infrastructure—from foundational SDK upgrades to sophisticated tokenomics and enhanced provider reliability. These iterative improvements aim to build a more scalable and utility-driven decentralized cloud. What will be the next technical milestone to further catalyze network adoption?