Layer 1 · Instant Receipt Verification

Verify Any Sensor, Smart Meter, or Fleet Receipt in 60 Seconds.

Drop a ProofPack file below or click Run Sample Verification to see how an insurer, utility, or auditor confirms that a reading and timestamp have never been altered.

Under the Hood Specs

Interactive Provability & Tamper-Detection Verifier

Test an Authentic Delivery Receipt vs. a Doctored Spreadsheet Log

No hardware changes and no rip-and-replace. Click Run Sample Verification above (or pick any real-world dispute scenario below) to see how Lumra proves an authentic custody timeline and immediately catches a single altered temperature or braking reading.

How This Works (3 Easy Steps: Understand in 10 Seconds)
Ready: 30-Sec Guided Tour Available
Step 1: Choose a real-world disputed claim scenario below (or click "▶ Run Sample Verification").
Step 2: Watch Lumra test the sensor or telematics receipt, first verifying an authentic sealed record and then catching an after-the-fact spreadsheet or log edit.
Step 3: Read the Plain-English Claims Verdict Card showing who held custody, whether a single byte was altered, and how fast the dispute settles (with the full cryptographic proof underneath for engineering and legal review).
Zero Hardware Changes: Webhook / API Ingest Pricing: $0.10/sensor/mo · $1.00/asset/mo · $4.00/camera/mo Offline Verifier v1.4.0: verify_proofpack.py (Zero PriviNet Server Calls) Legal & Standards Alignment: US FRE 902(13)/(14) & EU eIDAS Art. 41 Workflows
Dispute Resolution Time
3 Minutes vs. 6 Weeks
Custody Sources Verified
4 / 4 Passed
Post-Event Log Edits Caught
0 Edits (Intact)
Standalone Verifier Exit Code
EXIT 0 (PASS)

Select a Disputed Claim Scenario Below

Inspect Real Production Sample Artifacts

Download the actual JSON ProofPacks and our reviewed standalone Python verifier (verify_proofpack.py v1.4.0) to run the exact same verification on your own machine with zero PriviNet server calls:

Plain-English Verdict: What Just Happened?

Interactive Claims Verdict · 4 Real-World Dispute Scenarios
Scenario 1: Verified Authentic
Dispute / Claim Scenario: A $150,000 pharma cold-chain shipment arrived with a disputed temperature question across 4 custody handoffs (warehouse, reefer truck, port yard, and customs).
What Lumra Proved: Lumra verified that all 4 independent sensor and handoff records were cryptographically sealed at the exact minute each reading occurred, confirming custody and temperature compliance with zero post-incident edits.
Bottom-Line Claims Outcome: 100% Authentic Receipt: Settles Claim in 3 Minutes

Cryptographic & Legal Discovery Proof (For CTO / Claims Counsel)

PROOFPACK ARTIFACT: sample-coldchain-incident.json (4-Vendor Sealed Assembly)
VERIFIER STATUS: RESULT: INCIDENT VERIFIED. 4/4 SOURCE PACKS AND THE SEALED ASSEMBLY ALL PASS.
SIGNATURE SCHEME: HSM ECDSA P-256 ( intake-sealed ) + Ed25519 device source signatures
CANONICAL SHA-256 ROOT: 9f4c8e2a1b7d6053c8e9f0a2b4d6e8f1a3c5e7b9d0f2a4c6e8b0d2f4a6c8e012
TIMESTAMP AUTHORITY: Dual RFC 3161 Qualified TSA Tokens Verified (Primary + Sealed Secondary)
EVIDENTIARY ALIGNMENT: Structured for US FRE 902(13)/(14) certification & EU eIDAS Art. 41 workflows
Every ProofPack is verifiable standalone using python3 verify_proofpack.py <pack.json> --tsa-ca lumra-tsa-bundle.pem without contacting any PriviNet server.

Live ProofPack Receipt & Tamper Diff Inspector

Exit Code 0

Inspect the exact machine-verifiable ProofPack receipt and verifier output generated for the selected scenario:


          

        

      

    

  







  

    
Layer 2 · Verifier Specification & Cryptographic Proof Format

    
For Engineers & Security Auditors: Under the Hood

    
The interactive verifier above runs the exact same cryptographic checks as our open standalone Python script (verify_proofpack.py v1.4.0). You do not need a PriviNet account, API key, or network connection to audit a ProofPack.


    

      

        
01 · SHA-256 Append-Only Hash Chains & Signatures

        
Standalone Zero-Network CLI Audit (verify_proofpack.py v1.4.0)

        
Run python3 verify_proofpack.py <pack.json> --tsa-ca lumra-tsa-bundle.pem on any air-gapped workstation. The script recomputes every canonical UTF-8 event SHA-256 digest, verifies the append-only hash chain, checks the HSM ECDSA P-256 and device Ed25519 signatures (with post-quantum NIST FIPS 204 ML-DSA-65 support across the PriviNet control plane), and exits 0 on pass or exits 1 with the exact failing step and record index on any byte modification.

      

      

        
02 · RFC 3161 Independent Timestamps

        
Dual Timestamp Authority Token Validation

        
The verifier invokes OpenSSL to validate primary and sealed secondary RFC 3161 Time Stamping Authority (TSA) tokens against your supplied root CA bundle (lumra-tsa-bundle.pem). It confirms that the TSA messageImprint matches the ProofPack root digest, proving the exact sensor, smart meter, or telematics reading existed prior to the timestamp authority's signed clock time.

      

      

        
03 · ETSI TS 103 357, LoRaWAN & MyGeotab Schemas

        
Multi-Custodian & Downstream Webhook Correlation

        
Supports single-stream ProofPacks from MyGeotab (GetFeed SDK), The Things Stack, LORIOT, and Mioty Service/Application Centers (ETSI TS 103 357 webhook ingest), as well as multi-party Incident ProofPacks (lumra.incident_proofpack.v1) that bind warehouse, carrier, and utility meter logs under one outer sealed manifest.

      

      

        
04 · US FRE 902(13)/(14) & Evidentiary Scope

        
What Cryptographic Verification Proves

        
Each ProofPack includes a pre-filled declaration template structured to support self-authentication of electronic records under US Federal Rules of Evidence 902(13) and 902(14) and EU eIDAS Art. 41 workflows. Cryptographic verification proves payload integrity, enrolled signer identity, and timestamp order; it does not prove physical sensor calibration prior to ingestion or guarantee court admissibility.