xWarden: Physical Evidence Custody Chain
Every evidence item is XorIDA-split into QR shares. Every custody transfer generates an HMAC-chained audit entry with Ed25519 signatures. Append-only chain provides cryptographic proof of custody integrity.
The Problem
Physical evidence chain of custody relies on paper logs and institutional trust. Tampered logs can undermine forensic integrity. There is no cryptographic proof that evidence was not altered between custody transfers.
From the crime scene to the courtroom, physical evidence passes through multiple custodians: investigators, transport officers, lab technicians, evidence room clerks, and attorneys. Each transfer is recorded in a paper log or basic database that can be altered without detection.
A single compromised custodian can alter the log to cover evidence tampering. Defense attorneys routinely challenge chain of custody — and win — because paper logs provide no cryptographic guarantee that the evidence presented in court is identical to what was collected at the scene. The integrity of the entire justice system depends on trust in a paper trail.
The Old Way
The PRIVATE.ME Solution
Each evidence item is XorIDA-split into QR shares distributed to custodians. Every custody transfer generates an Ed25519-signed, HMAC-chained audit entry. The append-only chain is cryptographic proof of unbroken custody.
When evidence is collected, its digital fingerprint (hash + metadata) is XorIDA-split into QR shares distributed to independent custodians. The evidence item carries a QR tag linking it to its custody chain. Every transfer between custodians generates a log entry signed with the outgoing custodian's Ed25519 key and countersigned by the incoming custodian.
Each log entry includes the HMAC of the previous entry, creating an append-only chain. Altering any entry breaks the chain from that point forward. In court, the HMAC chain provides mathematical proof that the evidence custody record has not been tampered with — replacing "trust us" with "verify the math."
The New Way
How It Works
A four-stage pipeline: evidence registration with digital fingerprint, QR share distribution to custodians, Ed25519-signed transfer logging, and HMAC-chained custody verification.
Tamper-evident chain: HMAC-chained entries create an append-only log. Altering any entry in the chain is immediately detectable by verifying the HMAC sequence.
Evidence integrity: The evidence item's cryptographic hash (SHA-256) is recorded at registration. Any subsequent physical tampering is detectable by re-hashing and comparing.
Use Cases
Every evidence item QR-tagged at collection. Every check-in, check-out, and transfer HMAC-logged. Defense counsel can independently verify the chain. No more "lost" evidence.
Chain of CustodyLab receipt, testing, and return of evidence items cryptographically logged. Lab technician signs receipt and condition assessment. Results linked to unbroken chain.
Lab IntegrityAttorneys and judges verify the HMAC chain independently. Mathematical proof replaces witness testimony about custody handling. Stronger evidentiary foundation.
AdmissibilityPhysical evidence for insurance claims (damaged goods, accident artifacts) tracked with HMAC chain. Prevents evidence substitution fraud. Adjusters verify chain before settlement.
Fraud PreventionIntegration
import { registerEvidence, transferCustody } from '@private.me/physicalcustody'; // Register evidence with custodian list const chain = await registerEvidence( { id: 'EV-2026-0042', hash: evidenceHash, type: 'physical' }, ['officer-badge-1234', 'lab-tech-5678', 'clerk-9012'] ); // Transfer custody (both parties sign) const result = await transferCustody(chain, { from: 'officer-badge-1234', to: 'lab-tech-5678', condition: 'sealed, intact' }); // result.auditLog contains HMAC-chained entries
Security Properties
| Property | Mechanism | Guarantee |
|---|---|---|
| Evidence Integrity | SHA-256 hash at registration | Tamper detection via re-hash |
| Non-Repudiation | Ed25519 dual signatures | Both custodians sign each transfer |
| Audit Integrity | HMAC-chained log | Tamper-evident append-only chain |
| Secrecy | XorIDA QR shares | Information-theoretic (unconditional) |
| Verifiability | Independent chain verification | Any party can verify the full chain |
Verifiable Data Protection
Every operation in this ACI produces a verifiable audit trail via xProve. HMAC-chained integrity proofs let auditors confirm that data was split, stored, and reconstructed correctly — without accessing the data itself.
Read the xProve white paper →
Ready to deploy xWarden?
Talk to Ren, our AI sales engineer, or book a live demo with our team.
Deployment Options
SaaS Recommended
Fully managed infrastructure. Call our REST API, we handle scaling, updates, and operations.
- Zero infrastructure setup
- Automatic updates
- 99.9% uptime SLA
- Enterprise SLA available
SDK Integration
Embed directly in your application. Runs in your codebase with full programmatic control.
npm install @private.me/physicalcustody- TypeScript/JavaScript SDK
- Full source access
- Enterprise support available
On-Premise Upon Request
Enterprise CLI for compliance, air-gap, or data residency requirements.
- Complete data sovereignty
- Air-gap capable deployment
- Custom SLA + dedicated support
- Professional services included
Enterprise On-Premise Deployment
While xWarden is primarily delivered as SaaS or SDK, we build dedicated on-premise infrastructure for customers with:
- Regulatory mandates — HIPAA, SOX, FedRAMP, CMMC requiring self-hosted processing
- Air-gapped environments — SCIF, classified networks, offline operations
- Data residency requirements — EU GDPR, China data laws, government mandates
- Custom integration needs — Embed in proprietary platforms, specialized workflows
Includes: Enterprise CLI, Docker/Kubernetes orchestration, RBAC, audit logging, and dedicated support.
Ship Proofs, Not Source
xWarden generates cryptographic proofs of correct execution without exposing proprietary algorithms. Verify integrity using zero-knowledge proofs — no source code required.
- Tier 1 HMAC (~0.7KB)
- Tier 2 Commit-Reveal (~0.5KB)
- Tier 3 IT-MAC (~0.3KB)
- Tier 4 KKW ZK (~0.4KB)