Skip to content ComputeWorksPRELAUNCH
Documentation
Docs/The economics

Growing the GPU fleet

From a funded purchase plan to online hardware, including support during the waiting period.

Prelaunch documentationDescribes the intended protocol. Live contracts, funding, and services remain launch milestones.
On this pageEach purchase has its own planFunding is the start of a processSupport while hardware is being preparedSupport before the first rental payment

01Each purchase has its own plan

A hardware purchase is registered as a cohort: a defined unit or group of GPUs with a hardware specification, purchase budget, expected net revenue, and support terms. Estimates are planning inputs, not guaranteed earnings. Future cohorts can use different hardware and economics.

External suppliers and hosting operators handle procurement, installation, power, connectivity, maintenance, and rental operations. Protocol operators review payment, order acceptance, online status, and revenue evidence. An onchain payment record alone does not prove that hardware was installed or that it earned income.

02Funding is the start of a process

  1. Plan: review the hardware quote, expected net earnings, payment route, and finite support budgets.

  2. Reserve: confirm acquisition funds and the required Reserve backing, then reserve the purchase and fund its support commitments.

  3. Pay and accept: complete the approved payment process and confirm that the order was paid and accepted.

  4. Bring online: verify that the hardware is operating and record its online status.

  5. Reconcile: match rental reports to operating costs and actual settled revenue before routing physical cash.

03Support while hardware is being prepared

An approved cohort may have a Reserve-funded ramp subsidy covering the gap after paid order acceptance and before the hardware comes online. The implementation caps this period at 56 days and stops it earlier when the hardware goes online or the cohort closes.

The commitment is funded in advance. An unpaid provisional order does not vest support, and token launch alone does not start it. Released ramp support is a subsidy: it is not recorded as a loan to be repaid from later rental earnings.

04Support before the first rental payment

Once hardware is online, a separate finite advance window can bridge the delay before rental cash is received. A 30-day window is possible, but the actual duration and maximum are explicit deployment and cohort settings. The protocol cannot guarantee a supplier's payment date.

Advances require reviewed accrual evidence or an explicitly approved, capped estimate policy. Both the build-period and online commitments reserve full credit face at the 70% hard maximum of the cohort's expected net revenue, rather than only the discounted cashout amount.

When matching rental cash arrives, the same earning period's holder share first repays its online advance to Reserve. Any remaining holder share creates additional backing. A shortfall is recorded as a loss; the same earnings cannot create a second full allocation.

Updated September 22, 2026Read the risk disclosures ↗