ZK-PoC — consent, meter, revoke

A signed Compute Consent Manifest is verified independently, then a resource governor executes shards inside its declared ceiling. The meter shows what is actually being taken, not what was promised.

1 · Compute Consent Manifest

share ceiling duration path

no manifest issued yet

2 · Tamper tests

Each button alters the manifest after signing, then re-verifies. A declaration is only meaningful if changing it is detectable, so these must all fail — and the governor must refuse to start.

3 · Live meter

idle

device share — red mark is the declared ceiling

—achieved share

—target (after backoff)

—elapsed / cap

—shards done

—throughput

—energy est. / cap

—long frames

—battery

4 · The signed manifest

issue a manifest to see it

Serve over HTTP — module workers and ES imports do not load from file://. From the repo root: npx serve . or python -m http.server, then open /demo/.

Energy is an estimate. Browsers expose no power draw, so it is wattsAtFull × achievedShare × time, calibrated from host-side measurement. Battery delta is shown where available as a weak cross-check.