Akash #343 10/21/2026, 1:12:05 AM

Core Engineering – Q3 2026 Funding Proposal

Akash proposal #343: # Core Engineering – Q3 2026 Funding Proposal ## Summary This proposal seeks community approval to fund the Overclock Labs core team for...

Yes

98%

No

0%

Abstain

2%

Veto

0%

Original Proposal Text

# Core Engineering – Q3 2026 Funding Proposal ## Summary This proposal seeks community approval to fund the Overclock Labs core team for the protocol and provider-level engineering delivered during Q3 2026. Building on the Q2 work funded in [Proposal 333](https://www.mintscan.io/akash/proposals/333), this work spans the Pyth price feed migration and resilience work behind BME, a unified Akash CLI, ARM64 provider support, the mainnet release of confidential compute and InfiniBand interconnect, and a single provider configuration file. The AEPs and initiatives covered by this proposal are: - [**AEP-88 – Pyth Router-Based Price Feed Contracts:**](https://akash.network/roadmap/aep-88/) migrating Akash's AKT price feed to Pyth's router-based system before the guardian-based feed is retired. - [**AEP-89 – Unified Akash Command-Line Interface:**](https://akash.network/roadmap/aep-89/) making akt the single command-line tool for Akash users. - **ARM64 Support:** CPU architecture as a provider-reported attribute that tenants can request. - [**Confidential Compute via Kata Containers (AEP-83) – Mainnet Release:**](https://akash.network/roadmap/aep-83/) taking TEE support from development to a live mainnet release. - **InfiniBand / RoCE Interconnect – Mainnet Release:** taking multi-node GPU interconnect support from development to a live mainnet release. - **Price Feed Resilience:** continuing the Pyth hardening work so the price feed layers behind BME are sustainable, including evaluating and designing a secondary AKT/USD price source. - **Provider Configuration (non-AEP):** a single configuration file for provider operators. ## Motivation Akash's supply has been limited by assumptions built into the protocol. Every machine was assumed to be amd64, so providers with ARM hardware had no way to advertise it, and an amd64 container placed on an ARM node would fail after the tenant had already started paying for the lease. ARM64 support removes that limit and makes room for ARM servers and Apple Silicon. Confidential compute and InfiniBand interconnect support, whose core development was funded in Q2, were released to mainnet this quarter, giving tenants hardware-isolated workloads and multi-node GPU clusters for distributed training and fine-tuning. The Pyth migration (AEP-88) is protective work. The on-chain oracle and Burn Mint Equilibrium both depend on an accurate AKT price, and the guardian-based Pyth feed Akash relies on is being retired upstream. The migration ran the old and new sources side by side before cutover so the price feed never went dark. The price feed resilience work is a direct continuation of that hardening, aimed at making the price feed layers behind BME sustainable rather than dependent on a single provider. The CLI (AEP-89) and provider configuration work address the day-to-day experience of the people building on and supplying the network. Commands spread across separate binaries could look and behave differently depending on the tool, and provider settings split between CLI flags and environment variables made misconfiguration easy. Consolidating both reduces support load, simplifies documentation and automation, and makes onboarding new providers easier. ## Total Request For the Q3 2026 Core Engineering Proposal, Overclock Labs is requesting $205,916 from the Community Pool for work directly attributable to the core AEPs for this period, alongside a 54.3% AKT volatility buffer. | | **Request from CP** | |:--|--:| | Engineering hours | 726.71 | | Engineering rate per hour | $176.90 | | Engineering total cost | $128,553 | | Support hours | 33.55 | | Support rate per hour | $146.01 | | Support total cost | $4,898 | | **Labor Subtotal** | **$133,452** | | AKT Volatility Buffer (54.3%)\* | $72,464 | | **Total Request** | **$205,916** | ***\*AKT Volatility Buffer –*** *A 54.3% buffer is applied to this request to ensure adequate coverage during liquidation based on the past 180 days of AKT price fluctuations (applied as of 10/1/26). Any unused buffer during liquidation will be returned.* ## Budget Breakdown | | **Hours** | **Cost** | |:--|--:|--:| | Pyth Router-Based Price Feed Contracts (AEP-88) | 209.12 | $41,417.74 | | *As a percentage of total labor budget* | *27.51%* | *31.04%* | | Unified Akash Command-Line Interface (AEP-89) | 162.71 | $28,298.33 | | *As a percentage of total labor budget* | *21.40%* | *21.20%* | | ARM64 Support | 80.34 | $16,178.81 | | *As a percentage of total labor budget* | *10.57%* | *12.12%* | | Confidential Compute (AEP-83) – Mainnet Release | 130.56 | $16,280.82 | | *As a percentage of total labor budget* | *17.17%* | *12.20%* | | InfiniBand / RoCE Interconnect – Mainnet Release | 38.58 | $7,475.25 | | *As a percentage of total labor budget* | *5.07%* | *5.60%* | | Price Feed Resilience | 86.11 | $17,649.74 | | *As a percentage of total labor budget* | *11.33%* | *13.23%* | | Provider Configuration (non-AEP) | 52.84 | $6,151.07 | | *As a percentage of total labor budget* | *6.95%* | *4.61%* | | **Total** | **760.26** | **$133,451.76** | ## Conclusion Q3's core work widens what the network can offer and keeps its foundations sound. ARM64 support brings a new class of hardware onto Akash, and the mainnet releases of confidential compute and GPU interconnect make the network viable for sensitive and distributed training workloads. The Pyth migration kept the price feed behind the oracle and BME running through an upstream change, and the resilience work reduces its dependence on a single source. The CLI and provider configuration work make Akash easier to build on and easier to supply. ## 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. Overclock Labs will coordinate with the Decentralized Cloud Foundation (DCF) on the timing and execution of liquidations, so that conversions of these funds are aligned with other market activity across the ecosystem and are not working against one another. More details: {"title":"Core Engineering – Q3 2026 Funding Proposal","summary":"# Core Engineering – Q3 2026 Funding Proposal\n\n## Summary\n\nThis proposal seeks community approval to fund the Overclock Labs core team for the protocol and provider-level engineering delivered during Q3 2026. Building on the Q2 work funded in [Proposal 333](https://www.mintscan.io/akash/proposals/333), this work spans the Pyth price feed migration and resilience work behind BME, a unified Akash CLI, ARM64 provider support, the mainnet release of confidential compute and InfiniBand interconnect, and a single provider configuration file.\n\nThe AEPs and initiatives covered by this proposal are:\n\n- [**AEP-88 – Pyth Router-Based Price Feed Contracts:**](https://akash.network/roadmap/aep-88/) migrating Akash's AKT price feed to Pyth's router-based system before the guardian-based feed is retired.\n- [**AEP-89 – Unified Akash Command-Line Interface:**](https://akash.network/roadmap/aep-89/) making akt the single command-line tool for Akash users.\n- **ARM64 Support:** CPU architecture as a provider-reported attribute that tenants can request.\n- [**Confidential Compute via Kata Containers (AEP-83) – Mainnet Release:**](https://akash.network/roadmap/aep-83/) taking TEE support from development to a live mainnet release.\n- **InfiniBand / RoCE Interconnect – Mainnet Release:** taking multi-node GPU interconnect support from development to a live mainnet release.\n- **Price Feed Resilience:** continuing the Pyth hardening work so the price feed layers behind BME are sustainable, including evaluating and designing a secondary AKT/USD price source.\n- **Provider Configuration (non-AEP):** a single configuration file for provider operators.\n\n## Motivation\n\nAkash's supply has been limited by assumptions built into the protocol. Every machine was assumed to be amd64, so providers with ARM hardware had no way to advertise it, and an amd64 container placed on an ARM node would fail after the tenant had already started paying for the lease. ARM64 support removes that limit and makes room for ARM servers and Apple Silicon. Confidential compute and InfiniBand interconnect support, whose core development was funded in Q2, were released to mainnet this quarter, giving tenants hardware-isolated workloads and multi-node GPU clusters for distributed training and fine-tuning.\n\nThe Pyth migration (AEP-88) is protective work. The on-chain oracle and Burn Mint Equilibrium both depend on an accurate AKT price, and the guardian-based Pyth feed Akash relies on is being retired upstream. The migration ran the old and new sources side by side before cutover so the price feed never went dark. The price feed resilience work is a direct continuation of that hardening, aimed at making the price feed layers behind BME sustainable rather than dependent on a single provider.\n\nThe CLI (AEP-89) and provider configuration work address the day-to-day experience of the people building on and supplying the network. Commands spread across separate binaries could look and behave differently depending on the tool, and provider settings split between CLI flags and environment variables made misconfiguration easy. Consolidating both reduces support load, simplifies documentation and automation, and makes onboarding new providers easier.\n\n## Total Request\n\nFor the Q3 2026 Core Engineering Proposal, Overclock Labs is requesting $205,916 from the Community Pool for work directly attributable to the core AEPs for this period, alongside a 54.3% AKT volatility buffer.\n\n| | **Request from CP** |\n|:--|--:|\n| Engineering hours | 726.71 |\n| Engineering rate per hour | $176.90 |\n| Engineering total cost | $128,553 |\n| Support hours | 33.55 |\n| Support rate per hour | $146.01 |\n| Support total cost | $4,898 |\n| **Labor Subtotal** | **$133,452** |\n| AKT Volatility Buffer (54.3%)\\* | $72,464 |\n| **Total Request** | **$205,916** |\n\n***\\*AKT Volatility Buffer –*** *A 54.3% buffer is applied to this request to ensure adequate coverage during liquidation based on the past 180 days of AKT price fluctuations (applied as of 10/1/26). Any unused buffer during liquidation will be returned.*\n\n## Budget Breakdown\n\n| | **Hours** | **Cost** |\n|:--|--:|--:|\n| Pyth Router-Based Price Feed Contracts (AEP-88) | 209.12 | $41,417.74 |\n| *As a percentage of total labor budget* | *27.51%* | *31.04%* |\n| Unified Akash Command-Line Interface (AEP-89) | 162.71 | $28,298.33 |\n| *As a percentage of total labor budget* | *21.40%* | *21.20%* |\n| ARM64 Support | 80.34 | $16,178.81 |\n| *As a percentage of total labor budget* | *10.57%* | *12.12%* |\n| Confidential Compute (AEP-83) – Mainnet Release | 130.56 | $16,280.82 |\n| *As a percentage of total labor budget* | *17.17%* | *12.20%* |\n| InfiniBand / RoCE Interconnect – Mainnet Release | 38.58 | $7,475.25 |\n| *As a percentage of total labor budget* | *5.07%* | *5.60%* |\n| Price Feed Resilience | 86.11 | $17,649.74 |\n| *As a percentage of total labor budget* | *11.33%* | *13.23%* |\n| Provider Configuration (non-AEP) | 52.84 | $6,151.07 |\n| *As a percentage of total labor budget* | *6.95%* | *4.61%* |\n| **Total** | **760.26** | **$133,451.76** |\n\n## Conclusion\n\nQ3's core work widens what the network can offer and keeps its foundations sound. ARM64 support brings a new class of hardware onto Akash, and the mainnet releases of confidential compute and GPU interconnect make the network viable for sensitive and distributed training workloads. The Pyth migration kept the price feed behind the oracle and BME running through an upstream change, and the resilience work reduces its dependence on a single source. The CLI and provider configuration work make Akash easier to build on and easier to supply.\n\n## Limited Market Impact & Transparent Reporting\n\nOverclock Labs will custody the requested funds in a new, distinct wallet so that funds from any other source are not commingled.\n\nAll 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.\n\nOverclock Labs will coordinate with the Decentralized Cloud Foundation (DCF) on the timing and execution of liquidations, so that conversions of these funds are aligned with other market activity across the ecosystem and are not working against one another.","additional_link":"https://github.com/orgs/akash-network/discussions/1541"}

Community

Up 0 Down 0 Comments 0

1XP X 0base.vc

Cosmos governance portal by 1XP Validator and 0base.vc

... chains Wallet ready