Docs pages
Delivery week
Every deadline of a delivery runs on fixed offsets from the week's start, W: a Monday at 00:00 UTC. The app's ticket page shows each one for your ticket.
Deadlines
| When | UTC, for a week starting Monday | What happens |
|---|---|---|
| W − 80 h | Thursday 16:00 | last auction of the series |
| W − 72 h | Friday 00:00 | notice: delivery requests close; claims stop moving |
| W − 60 h | Friday 12:00 | buyer's SSH key committed, or the ticket ends in buyer default |
| W − 48 h | Saturday 00:00 | seller assigns a node |
| W − 24 h to W + 4 h | Sunday 00:00 to Monday 04:00 | inspector's acceptance test |
| acceptance + 2 h | buyer confirms access, or silence confirms it | |
| W to W + 168 h | Monday to Monday | delivery |
| W + 168 h to W + 192 h | Monday 00:00 to Tuesday 00:00 | challenge window; faults can still be filed |
| from W + 192 h | Tuesday 00:00 | certificate, then settlement |
A healthy hour
The seller is paid for each healthy node-hour. An hour is healthy when:
- all 8 GPUs are visible;
- their UUIDs match the node's accredited record;
- no gating XID error occurred (XIDs 48, 64, 74, 79, 95, 119 and 120: double-bit ECC, row-remap failure, NVLink, a GPU fallen off the bus, uncontained ECC and GSP errors);
- the node was reachable for at least 55 of the 60 minutes.
Evidence
Two agents sign a record every minute of the week:
- the buyer's Delivery Agent, on the node: a heartbeat with the GPUs' UUID hash, the XID count and a recent Solana slot;
- the seller's Provider Agent, on the management plane: BMC power and link state and DCGM health.
Each hour the committee aggregates both into one Merkle root per series and a bitmap of healthy tickets, and commits it on chain with two of its three signatures. An hour counts as healthy from the buyer's heartbeats; when the buyer's agent is silent and no fault is open, clean seller telemetry counts. Missing records never cut anyone's payment on their own: they open review. See the agents to run them.
Faults
If the node fails during the week, the buyer files a fault on the ticket:
- File. Choose the kind (unreachable, GPU health, performance, missing heartbeats), the hours affected, and attach the evidence's hash. A bond of 5% of the ticket's notional is posted with it. Faults can be filed until 24 hours after the week ends.
- Cure. The seller has 4 hours to move the ticket to another accredited node in the region. A replacement accepted by an inspector stops the damages clock.
- Contest and probe. The seller can contest instead. An inspector probes the node through the Delivery Agent's health endpoint. A failed probe, or a node that is unreachable while its BMC shows it down, is the seller's fault; a passing probe, or a buyer who blocks the probe, rejects the fault and the bond goes to the seller.
- Arbitration. A dispute still open after 72 hours goes to arbitration under the participant agreement; two of the three committee members record the award on chain.
The bond comes back to the buyer when the fault is upheld or cured.
After the week
When the challenge window closes and no dispute is open, the committee posts each ticket's delivery certificate: its certified hours out of 168. The ticket then settles on its own; see Settlement.