Results
Identity and privacy
No accounts and no fingerprints. A random key in your browser, and a print made only from measurements.
- Barcode
- Six metric bytes: read, write, copy, random, latency (inverted), sustain. Log-quantized; a wide bar is a 1, a narrow bar a 0, guards between.
- Phase traces
- Read, write, copy and sustain, 32 buckets each: every sample's deviation from its phase median, scaled per row.
- Die map
- A pattern seeded by the print id, for recognisability.
- Id
- Six digits: FNV-1a over the metric bytes, retention and traces.
Operator identity
No accounts. The first run creates a random 128-bit key stored in this browser. The server stores only the first 16 hex characters of SHA-256 of that key, shown publicly as OP-XXXXXX. The key never leaves the browser except inside a submission, and the Rewards page can copy it or restore it to move a ledger to another browser.
Wallets
Linking a wallet is optional. On the Rewards page you sign a short message naming your operator and the time; signing sends no transaction and costs nothing. The server checks the signature and stores the operator hash, the address and the signature. Unlink at any time from the same page.
MEMPRINT
A MEMPRINT is derived only from the measurements. It identifies a result, not a machine: two runs on the same computer produce different prints, and nothing in it comes from hardware identifiers.
What is stored
| Stored with a run | Never stored |
|---|---|
| Measurements, per-phase statistics and traces | IP addresses (rate limits count in memory only) |
| WebGL renderer string, WebGPU vendor and architecture | Accounts, emails, names |
| Coarse browser and OS, e.g. Chrome 140, Windows | The full user agent |
| Operator hash, status, flags, timestamps | Hardware serials or fingerprints |
| A wallet address, only if you link one | Private keys or signing authority |
Rejected runs are stored for audit and never shown.