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

The contract and its grades

Akash Compute Forwards is a design for a cleared forward market in GPU compute. A forward fixes a price today for delivery later. The buyer is long and gains when the price at delivery is above the contract price, and the seller is short and gains when it is below.

The ten fundamentals

The design rests on ten fundamentals.

  1. The hour is perishable. A GPU-hour, one hour of one GPU, that is not served in its hour is gone. Nothing can be delivered late.
  2. Delivery is continuous. Compute flows hour by hour, and settlement follows the same clock.
  3. Delivery is physical, and a failure closes out in cash. If a buyer’s provider fails in delivery, the program buys replacement compute for the buyer and charges the provider what it costs, or the buyer may take cash at the reference price, the anchor of the mark, instead. What is paid at once has limits, which Default protection and guarantors sets out.
  4. Margin comes before anything else. An account’s own margin answers for its losses ahead of any other layer, as Default protection and guarantors explains.
  5. There are two kinds of account. An anonymous account posts the full notional value of its position, the contract price times its GPU-hours, on either side, because its collateral is its only recourse. A certified account has a legal identity behind it and posts a requirement set by measured risk. During the pilot, a period set when the market starts that governance ends and cannot restart, only certified accounts place orders.
  6. Amounts are in US dollars. The market settles today in USDC, Circle’s dollar coin. AKT is never margin. ACT, Akash’s dollar-pegged compute token, may count toward part of a certified account’s margin, at a haircut set by formula, once it exists on Solana with the transfer terms the design requires. Until then, all margin is in US dollars, settled in USDC.
  7. Orders are open. Each contract’s book shows the total size at each price with no keys and clears at one price at a scheduled close.
  8. The program never names a trader. Positions are recorded under keys, the on-chain accounts that sign orders, never under a legal identity.
  9. The market runs on Solana.
  10. Node-months are interchangeable, and the program is the counterparty. Any attested node of the contract’s grade and region, one whose attestation the validators have verified (see Grades), delivers it. The program stands between every buyer and seller for the money, and anyone may be long or short, because attestation is required to deliver, not to sell.

The units

Unit What it is Its job
GPU-hour One hour of one GPU The unit of price, in US dollars per GPU-hour
Node-hour One node of one grade in one region for one hour The unit of account: each is served or missed, and settled, on its own
Node-month One node of one grade in one region for every hour of one calendar month The contract

An hour of an eight-GPU node costs eight times the quoted price. A node-month’s value is the price per GPU-hour times the GPUs per node times the hours in the month.

A strip is a run of consecutive node-months. It is not a separate instrument: it is entered as a block order, and at assignment it is a request to stay on the same nodes.

One contract

1 node · 8 × B300 · 1 calendar month · any attested provider · priced in USD per GPU-hour

One node · 8 × B300Every hour of one calendar monthOne node · 8 × B300Every hour of one calendar month

A node-month is every hour of one calendar month on one node. Its value is the price per GPU-hour × 8 GPUs × the hours in that month (744 in December).

A contract and a position

A contract is a grade, a region and a delivery month. An account’s position in it is a net number of nodes, positive for a long, which will receive compute, and negative for a short, which will deliver it.

A position changes only by trades at a close, by a close-out, by the assignment step that resolves an imbalance, and by the settlement of hours in delivery.

Any account may be long or short in any quantity its margin supports. A short delivers up to the attested free capacity its registry entry holds at assignment. The rest of it, and any short with no registry entry, is a financial short: it is netted against longs that asked for cash, and what remains of it at assignment is in default. A market maker can therefore sell without hardware and buy back before the month. Assignment is in Delivery.

Grades

A grade is defined entirely by thresholds a machine can check. Every grade requires confidential computing, a hardware mode in which a node encrypts a workload’s memory and signs a report of what it runs. Validators verify each node’s attestation report, the signed report of what it runs, and its signed performance results when it registers, and a node that passes is attested. The regions are NA, EU and APAC, coarse because they are the only geographic information on chain.

B300A, the opening contract

Field B300A
GPUs per node Eight B300 GPUs (HGX)
Host Intel TDX or AMD SEV-SNP, with measured boot, running a confidential virtual machine at grading
Confidential computing Confidential-computing mode across all eight GPUs, with NVLink encryption between them
Attestation The host’s report and a report for each GPU and each NVSwitch, each chained to its vendor’s root of trust, with the trusted computing base at or above the committed baseline. The evidence names the Fabric Manager’s measured version and the NVSwitch routing it set.
Floors Intra-node bandwidth, compute, host memory, storage and network, each read by formula
Test image Pinned by digest for the grade, and run inside the node’s attested confidential virtual machine

The owner decided that B300A’s floors are set by formula, never by hand. Each floor is a low quantile of the performance results measured in confidential-computing mode on the earliest attested nodes, with the vendor’s reference specification as the prior. The quantile is a placeholder still to be set. Floors come from performance tests measured on attested nodes and are re-read each quarter.

The formula’s form is a builder’s call, a default that can change. Every attested node’s results join the sample, so a new reading can lower a floor as well as raise it. No node is graded B300A until enough nodes are measured that no single weak node sets the quantile. A node keeps the floors it was graded at, so a rise never strips capacity sold forward, and no floor falls below the one originally ratified. A node measured at a registration that failed the floors still joins the sample, and it may register again and is graded at a new floor if a later reading lowers the floor to a level it meets. Governance ratifies a grade by adding it to the specification’s grade table, and it sets no threshold by hand.

The pilot starts with B300A alone, and Rules, fees and limits says what happens if B300A misses its supply gate.

H100A

H100A, the specification’s other grade, is eight H100 80 GB SXM GPUs on the same kind of confidential host, with GPU confidential-computing mode and protected NVLink. Its thresholds are set by hand, a builder’s call that can change, and whether they should be read by B300A’s formula instead is open. As the site’s grade card states them, they are:

  • NVLink all-reduce of 400 GB/s or more.
  • Sustained compute of at least 65% of the grade’s reference peak.
  • Host of 96 vCPU, 1 TB of RAM and 8 TB of NVMe, with 6 TB of tenant NVMe at 1.25 GB/s.
  • Network of 10 Gbit/s.

The provider registry

A provider registers its public endpoint, then each node with its attestation report, and its registry entry records attested nodes by grade and region. An order carries no registry reference, so the program does not attribute a provider’s asks to its entry. Only its assignments are attributed. The entry matters only at assignment, where a short counts as attested up to its free attested capacity. A registry entry may be anonymous or certified. During the pilot, an anonymous entry may register its nodes, but its key cannot place an order until the pilot ends.

By a builder’s call, a provider whose node fails mid-month may put in another node of the same grade from its own fleet, and the downtime counts as missed hours. The buyer’s state on the failed node is the buyer’s loss. Cash settlement does not cover it, so buyers who need their state checkpoint it to storage off the node.

Leaving a position

A position is closed by trading the other side at any close up to the last one before its month, at the market price, with no transfer and no one’s consent. A contract in delivery cannot be transferred, because a new buyer would inherit nodes holding the old buyer’s state. A buyer in delivery that stops using the compute keeps paying for served hours.

What is still open

  • Whether H100A’s thresholds should be read by B300A’s formula is open.
  • Whether a rise in a floor should ever reach a node graded before it is open.
  • The quantile behind B300A’s floors is a placeholder still to be set.

Three ways in

Do you run, need or price GPU compute?