RP

RepairProof

Verifiable device repair history

LOCAL DEMO MODE · cryptographic proof
Trust layer for repair records

Know what happened to a device.
Prove the record wasn't changed.

RepairProof turns service events into tamper-evident records. A buyer, insurer, technician, or reseller can verify the history without trusting a screenshot or spreadsheet.

Demo state
3
repair proofs stored locally
✓ HASH VERIFIEDCHAIN-READYNo customer PII on-chain

The demo hashes canonical repair data locally. A production deployment can anchor the hash to an EVM contract without putting private repair details on-chain.

Create repair proof

Capture only the service facts needed to verify the event later.

Verify a proof

Paste a RepairProof ID. The verifier reconstructs the canonical record and checks its fingerprint.

Verified history

Every record exposes its verification fingerprint and event details.

How RepairProof works

01 · CAPTURERecord the repair eventDevice + service facts are normalized into a canonical payload.
02 · FINGERPRINTHash the payloadSHA-256 creates a unique proof fingerprint for the exact record.
03 · ANCHOROptionally anchor on-chainOnly the fingerprint needs to reach a public EVM registry.
04 · VERIFYDetect changesAny altered field produces a different fingerprint and fails verification.

Hackathon MVP · Demo records are stored in browser localStorage. This is not a device authenticity certification or a substitute for an authorized service provider's records.