50GRAMx Proof

How Proof works.

Every step, and which machine does it. Your site is held on grams you own; the network’s edges carry it to visitors.

1Work runs2It signs3It travels4Anyone checks
  1. 1
    Work runsA gram measures, answers or publishes something.
  2. 2
    It signsThe gram signs the result with its own key.
  3. 3
    It travelsThe result goes wherever it is needed, with its signature.
  4. 4
    Anyone checksThe signature is checked against the gram’s public id.

Seen on a real gram

A real result, and the same result with one number changed
$ epnd bench verify result.json && epnd bench verify tampered.json
VALID: cpu.throughput = 153.8 hashes/s  (signed by did:epn:0024080112208414…bd024bfdd68672)

signature invalid — result was tampered with or signed by another node
Real output. Run on the founder’s Mac gram, 16 Nov 2026. In tampered.json only the value was changed, to 999.
A signed measurement
$ epnd bench cpu
{
  "result": {
    "metric": "cpu.throughput",
    "value": 153.80340074778266,
    "unit": "hashes/s",
    "node_did": "did:epn:0024080112208414…bd024bfdd68672",
    "extra": { "cpu_model": "Intel(R) Core(TM) i5-5350U CPU @ 1.80GHz", "cores_physical": 2 }
  },
  "signature": "A+lGCMXcikiDAoscA+e3wN8xyuPsl8Mn+ndf982Po8jf0FLa…"
}
cpu: 154 hashes/s over 507ms
Real output. Run on the founder’s Mac gram, 16 Nov 2026. The gram’s id and signature shortened.