GPU-POOR

Racked so far: waiting for the server

Of an H100 · 1,979 TOPS INT8Spec

How many of you make one H100?

A 45-second sprint on your own GPU, timed and checked by our server. The result is the fraction of an H100 your device is.

  1. Hold to start. Our server sends a nonce and starts its clock.
  2. Your GPU multiplies integer matrices for 45 s. Every 5 s, the server recomputes 4 tiles.
  3. All 36 checks pass: you get N, a class and a public receipt.

This browser

Live
GPU
Asking the browser… 
Faction
— 
Run
45 s · 9 windows · 36 checks
Param
Keys
↵orSpacehold to startEscstop
or hold↵

Hold 1 s. Stop any time.

How it works

$GPUPOOR · not launched · no token, no price, no address · nothing is paid

Illustration: FINS, a chrome android whose hair is heatsink fins.
FIG. 0 — FINS · the GPU-POOR reference unit · a renderIllus

Classes · Season 1 · The Shortage

Your class is your N.

N is how many devices like yours make one H100. Thresholds are Param: set once in public after the beta, then frozen for the season. You can’t buy your class.

  1. GPU-POOR

    N > 1,000

  2. Working-class

    N 333–1,000

  3. Middle-class

    N 100–333

  4. GPU-RICH

    N ≤ 100

Our M5 · 1,727 Verified

FIG. 4 — Classes by N · log scaleParam
  • Illustration: FINS cradling one small cooling fan; only its lowest fins glow.

    GPU-POOR

    N > 1,000

  • Illustration: FINS carrying one graphics board against its chest.

    Working-class

    N 333–1,000

  • Illustration: FINS with a partial arc of three cooling fans behind its head.

    Middle-class

    N 100–333

  • Illustration: FINS, every fin lit, with a ring of eight cooling fans behind its head.

    GPU-RICH

    N ≤ 100

  • Illustration: FINS seated on a block of stacked graphics boards.

    Oligarch

    Top 0.1%

  • Illustration: FINS as a blurred silhouette behind hatched frosted glass, among dark server cabinets.

    Landlord

    Off-scale

Renders, not measurements.Illus

Off the axis

Param
Oligarch
Top 0.1% · seasonThe season’s top 0.1%, checked 256 times instead of 36. Opens at 1,000 verified runs.
Landlord
Off-scale · not countedCloud, VPN or server hardware. Never ranked, never counted, never paid.

Markers

Ring
Our Apple M5 test laptopLow Power Mode · 45 s on our clock
Dot
You, after a verified runNothing is marked before a run.

Verification

Your GPU computes. Our server checks.

The server issues the nonce, keeps the time and recomputes 36 random tiles. Figures measured on our Apple M5.

  1. A nonce

    Our server sends a fresh 256-bit nonce. It seeds your matrices, so nothing can be computed in advance.

  2. Chained batches

    Each batch seeds the next one, on your GPU. No skipping ahead, no splitting the run across machines.

  3. A hash per 64×64 tile

    Every output tile is hashed with BLAKE3 into a commitment. It is nonlinear, so there is no algebra shortcut.

  4. 4 tiles, redone on our clock

    Every 5 s we pick 4 tiles and recompute them ourselves. Only our clock counts time.

  • Checks per runParam

    36

    challenges in every 45 s run

  • Slip chanceDerived

    2.3%

    chance that a run faking 10% of its work gets through: (1 − 0.1)36

  • Test cheaterVerified

    4/36

    checks failed by our test cheater, who faked 9% of the work. It scored 0.

  • Final checkVerified

    54–96ms

    for the final check after the last window

We prove the compute, not the place.

A bigger card simply scores as a bigger card. Faking under 5% still slips past 36 checks 16% of the time, so any run that would enter the top tier gets 256.

How it works

The People’s Cluster

Nobody’s GPU-rich alone.

One rack is one People’s H100: 8.9 × 10¹⁶ verified ops, or 45 seconds of one H100 at dense peak. Every verified run fills racks by its share. An M5 fills 1/1,727 of one.

Open the cluster
Illustration: FINS sliding a server tray into a rack in a dark server aisle.
An illustration. The measured aisle is below.Illus
FIG. 5 — Aisle 1 · 1 rack = 1 People’s H100 · — H100 rackedLive

Racked

—

People’s H100s. — runs so far.

Live

—

During a Surge. Verified windows only.

Record

—

Best peak together. No Surge yet.

A sum of peaks is not a cluster.

No interconnect, no shared memory. We add up verified peaks and say so.

Illustration: a chrome knife-switch breaker, lever down.

The SurgeParam

Every Sunday 18:00 UTC

Lobby opens at 17:50 UTC.

Time to the next Surge
First target
0.1 H100
Target
Equals
≈ 173 M5 laptops
Derived
Start
T−10 sSynchronised start: hold to start with everyone at T0.
Holding
0 devices
Add to calendar.ics
  • The Orchard
  • Team Green
  • Team Red
  • Team Blue
  • The Pocket Army
  • Unaffiliated

Factions are cosmetic. Missing a Surge costs nothing.