Akash Network: Decentralized Cloud Infrastructure Marketplace

Author credited on PDF	Overclock Labs
Published	May 13, 2018; version 0.0.3
Project	Akash Network
Document license	No explicit reuse license stated in the PDF. The separate AEP-2 specification states Apache 2.0.
Original paper	Official repository PDF

Akash Network: Decentralized Cloud Infrastructure Marketplace is a 2018 proposal for an open market connecting people who need compute with providers that can lease it. The original PDF credits Overclock Labs. This summary separates that early design from later GPU support and the payment system documented in 2026.

The Original Design

The paper proposes a shared marketplace across independent providers, with containerized applications running on their infrastructure. Its core separation is between the ledger that records procurement and payment, and the servers that execute workloads. Blockchain consensus does not perform the application’s computation.

Its original token name is AKASH. That historical terminology should not be confused with today’s AKT and ACT roles. Early staking and reputation ideas describe a proposal; they do not establish every requirement of the current provider system.

Orders, Bids and Deployment

The related AEP-2 specification defines deployment requests, resource requirements, provider offers and leases. In this early design, an eligible lowest-price offer is matched after the bidding period. Current documentation describes users reviewing bids and selecting their preferred provider. Price is one criterion alongside hardware, location and reliability.

AEP-2 also separates the deployment manifest from its on-chain hash. It describes distributing manifest details to participants over authenticated connections, while the ledger provides the reference against which they can check the version. This distinction matters because publishing a procurement record is different from publishing an application’s complete configuration.

SDL and Present-Day Operations

Stack Definition Language (SDL) is a YAML-based format for services, resources and placement requirements. A container image alone is not a complete deployment specification: resource profiles, placement pricing and deployment mappings are also required. Consult the current syntax and examples for the network version you use.

The provider and lease guide explains the current selection process and operational responsibilities. Tenants monitor funding and close deployments when finished; providers run the containers and maintain service. Matching a lease on-chain does not guarantee that a particular provider will meet every application’s performance needs.

Later Network Milestones

The official Mainnet 1 announcement is dated September 25, 2020 and describes staking and governance. Deployment-marketplace functionality belonged to a later phase. Calling 2021 the first mainnet launch obscures that distinction.

The August 31, 2023 Mainnet 6 announcement introduced GPU support and stable payments. GPU workloads are a later expansion of the market, not proof that the 2018 paper described today’s hardware inventory. Available GPU models and prices vary by provider and time.

Payments: What Changed in 2026

Akash’s Q1 2026 report confirms that Burn Mint Equilibrium (BME) went live on March 23, 2026. AEP-76 describes the economic design around AKT and non-transferable ACT compute credits. For actual settlement behavior, the implementation documentation is the more specific reference.

The current application-layer documentation describes ACT-funded escrow, per-block lease accounting and provider withdrawals in ACT. BME handles conversion between ACT and AKT. When the circuit breaker halts minting, escrow can use an AKT fallback. This is more precise than saying every lease simply pays AKT or any IBC token.

The same documentation says the legacy take module does not apply a take-rate to lease settlements. A fixed “6% of every lease” claim is therefore inappropriate for the current system. Proof of Stake and AKT staking secure the chain; they are distinct from the compute credits used to fund workloads.

Reading the Paper Critically

The original paper explains a market architecture, rather than proving current savings, uptime or market share. Compare live quotes for equivalent hardware, storage, bandwidth and location, and account for migration and operational costs. Historical utilization estimates and forecasts should not be presented as measurements of today’s cloud market.

Social Media Sentiment

Not applicable to this historical-paper summary. Project reports document changes; they do not establish public sentiment or an investment case for AKT.

Last updated: 2026-10

Related Terms

Proof of Stake — chain security.
Staking — committing tokens to secure a network.
Validator — a participant in consensus.