Idle compute, sellable by the token.
Phones, laptops, cars, drones — billions of NPUs sit idle 90% of the time. The HQ Compute Mesh is the global spot market: clients post inference jobs, workers claim leases, HQ schedules and prices, and every passing-attestation result settles per-token via the Loadit Settlement Grid. Compute is the new oil — and the user owns it.
The paradigm break
Compute is concentrating in 5 hyperscalers who capture ~95% of the margin. That isn't because hardware is scarce — every recent phone ships an NPU capable of ~50 INT8 TFLOPS, and there are billions of them. The blocker has always been scheduling, settlement, and trust.
HQ does scheduling (job ↔ worker matching with reputation weighting). Loadit + the Settlement Grid do settlement (per-token, atomic, with a verifiable receipt). Hylaq does trust (every device is a @handle/device-XX with attested capability and accumulating reputation). That triangle is what unlocks the marketplace.
What we replace
Six devices. One marketplace.
How a job moves
The 40-year arc
- Years 1–3Power-user laptopsIndie devs running local LLMs lend NPU/GPU at night. Small developer audiences buy from the Mesh because it's cheaper than OpenAI for non-frontier models. ~10K workers, $1B/yr inference.
- Years 4–7Phones at scaleiOS/Android SDKs ship; opt-in 'earn on charger' becomes a setting. ~100M phones online overnight. The Mesh becomes the cheapest place to serve open-weight models on Earth.
- Years 8–12Vehicles + edgeTesla / Rivian / GM open EDGE_NPU APIs. Telco MEC nodes auto-register. Inference spot price decouples from hyperscaler cost curves. ~$100B/yr Mesh volume.
- Years 13–20Default for anything not frontierEverything except trillion-parameter frontier models runs on the Mesh by default. Hyperscalers pivot to specialty training. The Mesh is the Visa of compute.
- Years 20–40Citizen-owned computeThe biggest distributed cluster on Earth is owned by hundreds of millions of individuals. The dividend is meaningful. Compute is the new asset class everyone holds.
Shipped today
- src/lib/compute-mesh/ — types, capability scorer, pricing engine, reputation, in-memory registry with heartbeat-TTL OFFLINE detection, job queue with spot-priced-on-post, lease lifecycle (ISSUED/ACTIVE/COMPLETED/SETTLED/EXPIRED/FAILED/SLASHED), bidirectional scheduler, attestation + audit (STAKED + DUAL), settlement that calls into Settlement Grid, BigInt-safe wire serialize
- 8 API routes — POST /workers/register, POST /workers/heartbeat, POST /jobs/post, POST /jobs/claim, POST /jobs/complete, GET /jobs/[id], GET /prices, GET /health
- Pricing curve — piecewise-linear utilization (floor → 4x → ceiling) clearing per device class. Floor undercuts hyperscaler unit economics; ceiling undercuts hyperscaler list price.
- Capability scorer — per-class score caps (PHONE_NPU 250, LAPTOP_NPU 450, LAPTOP_GPU 700, DESKTOP_GPU 1000) with sustained-power discount + bandwidth gate
- Reputation arithmetic — bounded [0, 10000], +SUCCESS / -FAILURE / -SLASH, banned <1000, DUAL-eligible >=3000
- Worker SDK — httpTransport(baseUrl) + meshWorkerSdk + runWorkerLoop with heartbeat + long-poll claim + complete; runs in browsers, RN, Node, Bun
- End-to-end jest test — register → post → match → claim → complete → attest (forced ACCEPT) → settle via Settlement Grid → verifiable receipt + worker IDLE + reputation up
- Phase-2 swap points called out — TEE attestation on capable hardware, federated audit, persist to Postgres, multi-region scheduling with proximity, HQ-driven dynamic price calibration
Compute is the new oil. The user owns the well.
Hyperscalers concentrate the margin because they own the rails. The Mesh + Settlement Grid is a different rail — one where the hardware is already owned, the settlement is already protocol-native, and the dividend flows back to the people who own the silicon.