Designed, not live. Nothing trades until two audits are clean, the pilot blockers found in our own risk review are fixed and checked again, counsel has answered, the B300A grade is ratified and default protection is in place and attested. The pilot will be open to certified businesses only.

Chapters

Documentation

The design of Akash Compute Forwards in detail, chapter by chapter, with every value marked as decided, a default, an initial value, a placeholder or open.

What these pages are

Akash Compute Forwards is a design for a cleared forward market in GPU compute. It is not open, and nothing on this site trades.

These pages set the design out in detail, for a provider’s engineers, a buyer’s infrastructure lead or a market maker’s desk. They are written from the market’s specification and from white paper Version 0.3, and each chapter says which sections it follows.

How to read them

Every value here carries its status. A decided value is one the owner set. A default that can change is a choice made in the design. An initial value is the value a parameter or a decided figure starts at: governance can change it behind the timelock, and where the specification measures the parameter, measured data replaces it. A placeholder is a value still to be set, which these pages name in words without a number. Open means the specification has not settled the question. The glossary defines each status word and every term these pages use.

Worked examples are illustrative, and each one says so. Prices are in US dollars per GPU-hour, quantities are in nodes and node-months, and money is in US dollars.

Where to start

Chapters

  1. The contract and its grades

    What one contract is, the units it is priced and settled in, the grades a node must meet to deliver it, and how a position opens and ends.

  2. The call auction, with worked order books

    How orders rest in an open book, how the daily call auction finds one clearing price per contract and shares the fill, what is published and what it costs, with three worked books.

  3. Margin, the daily mark and settlement

    How the program values every position each day at a mark built from the market's own trades, moves the change between accounts in US dollars, and holds each day's gain for one close-out window, with a worked week.

  4. Delivery, and how each hour is checked

    How a buyer is paired with attested nodes before the month, how validators check every hour, what a missed hour costs the provider, and what happens on a long outage.

  5. Default protection and guarantors

    What counts as a default, the fixed order in which a defaulter's loss is met, what its counterparties receive, and how a claim beyond the published price is pursued.

  6. Parties and roles

    Who takes part in the market, and what each party pays, is paid, stands behind and delivers.

  7. AKT and ACT

    The three places in this market where AKT comes into play, none of them switched on yet, and how ACT may count toward part of a certified account's margin.

  8. Opening an account

    The two kinds of account, why the pilot admits certified businesses only, what certification obliges an account to pay, and the steps from a certification agent's check to an order in the book.

  9. Rules, fees and limits

    What must happen before anything trades, the order shapes, the fees at their initial values, the limits on size and on gains, and how a rule is changed.

  10. Glossary

    The terms these pages use, each defined in a sentence or two, with the status words that mark what is decided and what is still open.

Before anything trades

What must happen before anything trades, and who decides, is in Rules, fees and limits.

The whole design in one document

White paper Version 0.3 sets out the same design in one document, with the reasons for its main rules.

Akash Compute Forwards

A cleared forward market in GPU compute

Version 0.3 · 11 November 2026

32 pages · PDF

Summary

A GPU-hour is perishable: an hour that is not served in its hour is gone. A provider that buys GPU servers and a buyer that plans months of work both need to fix the price of hours that do not yet exist. The paper proposes a forward market in which a contract is one node of one GPU grade, in one region, for one calendar month. A program on Solana stands between every buyer and seller. Each day it clears an open auction, values every position at a price built from the market's own trades, and moves the day's price change between accounts in US dollars. Before each month it pairs buyers with providers' attested nodes, and validators check every lease each hour. Every protection has a limit published in advance.

Download the white paper (PDF, 32 pages)

Three ways in

Do you run, need or price GPU compute?