Proof, not prestige

Verify us. Don't trust us.

Checking the node…
How it works

A number becomes signed

A node measures itself. It runs the benchmark, collects the result, and signs the measurement with its own private device key. The signature proves three things:

  1. The node ran the test. We did not invent the number. The device itself produced it.
  2. The result is unchanged. The signature commits to every byte of the measurement. Change one digit and the signature fails.
  3. You can verify it yourself. The node’s public key is published; anyone can re-hash the measurement, check the signature, and confirm the number was really signed.

That is the whole mechanism. No one is trusted because no trust is needed. You do not trust us to sign honestly — you verify the signature yourself. This is why we can say “these numbers are real” and mean it.

The honest part

What we have not measured

Every competitor's proof page claims completeness. Ours carries a changelog. Each entry below shows the date it was first added to the unmeasured list. When resolved, the resolution date will appear. This list shrinks.

gpu.throughput

GPU detection reports an inventory — model, VRAM, utilisation — and no throughput benchmark. A signed throughput benchmark is configured but not implemented.

Added Jul 9, 2026
energy.joules_per_hash

Energy is measured only on Intel processors with RAPL, on Linux. Every other platform reports nothing rather than a substitute.

Added Jul 9, 2026
cpu.throughput_multicore

CPU throughput is deliberately single-threaded, so that two machines can be compared. No whole-machine figure is measured.

Added Jul 9, 2026

Be precise about what is proven here. That a metric is unmeasured is asserted by the node itself: the snapshot marks it configured_not_yet_benchmarked, signed. The date beside it is not signed — it is the day we wrote the limitation down, and you are trusting us for that one. When an item resolves it leaves this list and appears in the verification matrix above.