Evidence Capture & Real-Time Tracking
Purpose: show how data becomes admissible evidence before it hits the PoV Gate.
What: commissioning, device identity, signed time windows, and calibration records.
Why: proof starts at the edge; unsigned or uncommissioned devices are not admissible.
What: signed payloads, TLS/mTLS, replay protection (nonces + window IDs), operator file digests.
Why: prevent tampering before evidence is hashed.
What: sorted/minified JSON, fixed units (Wh), fixed types → evidenceHash = SHA-256(blob).
Why: the same reality must hash to the same bytes; PoV equality checks rely on this.
What: duplicate detection, window overlap checks, per-device rate limits, sanity bounds.
Why: stop garbage and floods before attestations count.
What: local aggregation, retry queues, clock drift handling.
Why: reduce latency and data loss without weakening the evidence chain.
What: hashes on-chain; artifacts in S3/IPFS/partner vaults with signed URLs; access logs.
Why: keep PII off-chain while preserving auditability.
Last updated