Akash Core Engineering - Q3 [SDK53] - Funding Proposal #1106
Replies: 3 comments
|
Hi @lechenghiskhan, Sorry for the late review, however I just wanted to ask how the funds provided to Overclock in Proposal 268 (153,331.76 AKT or $377,196.13 estimated at the time of the proposal)? I imagine that given the Mainnet upgrade took way longer than the original plan (including an increased scope), and Proposal 268 did not cover the full cost as Overclock was planning to cover part of the effort themselves, that additional funds were required, however I'm surprised to see that it was not mentioned during the calculations of the cost. Was that effort (planned to finish in September 2024) completed without success and then this proposal only covers the work done "in the last 3 months" as you say? I checked the Proposal 268 Report linked here but I do not have access to read it. On the assumption that my above hypothesis is correct, I'm voting yes on the proposal. Thanks to all who made the network upgrade a success! |
|
This vote passed on chain on December 2, 2025 by a 97% majority. |
|
Hi @lechenghiskhan, |
Uh oh!
There was an error while loading. Please reload this page.
Summary
This proposal seeks community approval to reimburse the Overclock Labs core team for efforts related to the Akash Network from Cosmos SDK v45 to Cosmos SDK v53, representing a major modernization of the chain’s architecture. Over the last 3 months, the core team has been focused on a massive code rebase and optimization for Akash Mainnet 14. This effort took a great deal of code improvements and testing, along with a great deal of coordination leading up to, during, and following the network upgrade to Akash Mainnet 14.
The following AEPs (Akash Enhancement Proposals) were delivered on as a result of the Mainnet 14 upgrade:
For further insights into the Mainnet 14 upgrade, see the blog post here. For further details of technical upgrades throughout the update timeline see the GH roadmap here.
Prior to the mainnet 14 upgrade, the core team issued JWT Support for the Akash Provider API. The JWT Support was discussed in AEP-64.
JWT authentication offered several advantages to the legacy counterpart:
The JWT Support upgrade was successfully completed prior to the launch of Mainnet 14.
Motivation
The Cosmos SDK v45 release marked a stable foundation for Akash, but its lifecycle is approaching end-of-support. Cosmos SDK v53 delivers substantial advancements across performance, state management, modularity, storage, and security—allowing the Akash Network to have a codebase that is easier to maintain, and a host of features that can be unlocked with greater speed.
Key drivers include:
Background
The Mainnet 14 release delivered:
This network upgrade has made it possible to develop and build the network significantly faster.
Throughout the network upgrade event the Core Team was responsible for a wealth of intensive responsibilities including:
Total Costs
For Q3 Core Support Proposal, Overclock Labs will request $742,158.42 from the Community Pool covering labor and operating costs directly attributable to the efforts around the Mainnet 14 upgrade.
*Additional Operating Support Costs
Represent recurring or semi-recurring expenditures that support the administration, coordination, and continuity of Akash Network operations across fiscal periods. They include infrastructure costs and client-facing functions.
**AKT volatility buffer
*This buffer accounts for the historical daily volatility of AKT measured over a period of 28 days. By providing a more substantial buffer against potential downswings in AKT, we mitigate the need to request any budget shortfalls through subsequent proposals. In the event of excess funds above the US dollar amount for labor, taxes, and overage, all remaining AKT will be promptly returned to the community. *
Limited Market Impact & Transparent Reporting
The Overclock Labs will custody the requested funds in a new, distinct wallet so that funds from any other source are not commingled.
All funds will be liquidated and managed in a manner that ensures minimal impact on the market. These funds will be handled with the same care and attention as all previous Community Funding Proposals, with liquidations done in a fashion that will not adversely affect the market. In practice, the effort of this liquidation will add depth to the AKT market for buyers looking to enter.
Conclusion
Migrating Akash from Cosmos SDK v45 to v53 is a crucial step in enhancing the network’s performance, maintainability, and ecosystem compatibility. With the architectural overhaul to Mainnet 14 complete, Akash is well-positioned to benefit from the improvements introduced in SDK v53.
This discussion invites community feedback and serves as the foundation for a formal governance proposal.
All reactions