Akash Network
Akash Client Engineering - Q3 Funding Proposal #1105
Closed
lechenghiskhan
started this conversation in
Governance Proposals
Replies: 1 comment
-
|
This proposal passed on chain on December 2, 2025 by a 96% majority. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Client Engineering - Q3 Funding Proposal
Summary
As the development of Akash Network accelerates through 2025 with the help of Community Pool resources, the Akash Core Team will continue publishing AEP funding requests in quarterly batches that encompass shipped features and enhancements during that period.
This discussion invites the Akash Community Pool to support the completion of six (6) Akash Enhancement Proposals (AEPs) — **AEPs 33, 34, 68, 69, 71, and 72 **These AEPS collectively form the third quarter’s comprehensive set of upgrades, bringing essential, enterprise-ready features and significant functional refinements to both the Provider and Deployment Consoles. These AEPs, along with future proposals completed and shipped during a particular quarter, will be combined into unified discussions for brevity.
These AEPs were developed, tested, and implemented by the Overclock Labs Product and Core Engineering teams to continue addressing long-standing limitations in flexibility, interoperability, and developer experience when deploying workloads to the Akash Network on the Deployment Console, as well as to enhance the flexibility and scalability of the Akash Provider Console.
Why This Matters
While individually meaningful, these six (6) AEPs collectively provide significant quality-of-life improvements for both new and existing users on the Akash Network. Many of these features have been asked for by existing users and new users alike. These AEPs will improve user experience for client integrations with Akash, managing providers, and beyond.
Total Costs
For Q3 Client Proposal, Overclock Labs will request $434,258.04 from the Community Pool covering labor and operating costs directly attributable to the client AEPs for Q3.
*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 14 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. *
Cost Breakdown by AEP
AEP Summary
AEP-33: Escrow Balance Alerts in Akash Console
Problem Addressed:
One of the main challenges Akash users face is the sudden termination of leases caused by depleted escrow balances. Without the enhanced visibility into when their funds are running low, users may be caught off guard, leading to service interruptions.
See “Total Costs” for the labor budget.
Github Milestone: https://github.com/akash-network/console/milestone/15
Key Features Introduced:
Associated Blog: Alerts and Notifications in Akash Console
AEP-34: Workload Log Forwarding via Akash Console
Problem Addressed:
Customers can only view limited logs in Console and the logs are often lost when the lease closes.
See “Total Costs” for the labor budget.
Key Features Introduced:
AEP-68: Console - Billing & Usage
Problem Addressed:
Credit card users on Akash Console lack visibility into billing and usage data, unlike crypto wallet users who can track activity via blockchain tools. This makes it hard to track spending, review receipts, and understand how compute resources are being used over time.
See “Total Costs” for the labor budget.
Key Features Introduced:
A new “Billing & Usage” section in Account Settings provides detailed billing insights.
Associated Blog: Billing & Usage Analytics in Akash Console & API
AEP-69: Provider Console API - v1
Problem Addressed:
GPU providers need structured access to financial and utilization metrics for internal dashboards, stakeholder reporting, and revenue forecasting. The current Provider Console only offers limited high-level stats.
See “Total Costs” for the labor budget.
Key Features Introduced:
Associated Blog: Provider Console - Earnings API
AEP-71: Deployment Closure Alert in Console
Problem Addressed:
Deployments can close unexpectedly for reasons beyond depleted escrow funds, leaving users unaware until disruption occurs. Without immediate alerts, users cannot respond quickly to restore services.
See “Total Costs” for the labor budget.
Key Features Introduced:
Github Milestone: https://github.com/akash-network/console/milestone/23
Associated Blog: Alerts and Notifications in Akash Console
AEP-72: Console - Improved User Onboarding
Problem Addressed:
Akash Console’s current onboarding process offers minimal trial credits, no sign-up requirements, and limited providers, resulting in lower conversion rates and wasted resources. New users lack guidance and urgency to transition into paying customers.
See “Total Costs” for the labor budget.
Key Features Introduced:
Github Milestone: https://github.com/akash-network/console/milestone/23
Conclusion
These AEPs are critical because they close major usability and trust gaps in the Akash ecosystem. Together, they prevent unexpected workload failures (through alerts and auto-reload), give users the visibility and tools they need to debug and manage spend (via log forwarding and billing dashboards), and improve the overall customer journey (onboarding, product announcements, credit flexibility). At the same time, they unlock professional-grade capabilities for providers (APIs, multi-depositor escrow) that enable scale and automation. In short, these initiatives reduce friction, build confidence in Akash as a production-ready platform, and drive both user adoption and provider growth.
Implementation & Rollout
These features are fully tested and are live for users right now.
Limited Market Impact & Transparent Reporting
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 to minimize market impact. 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.
Feedback Welcome
We're opening this discussion to:
Feel free to comment below with any thoughts, issues, support, or ideas.
Beta Was this translation helpful? Give feedback.
All reactions