# PriviNet > PriviNet Inc builds verification infrastructure. Lumra seals operational event > metadata on receipt with an HSM-held key, verifies enrolled source signatures > when present, hash-chains the protected records (SHA-256), and exports portable > packages another party can check with a standalone tool. Decern is a control > and proof layer for Bitcoin custody and digital asset protection, patent > pending (U.S. provisional filed June 2026), currently a research prototype on > Bitcoin signet. Key facts: - Lumra exports can support a qualified person's authentication process under U.S. FRE 902(13)/(14). They do not make evidence automatically admissible; relevance, hearsay, completeness, privilege and other objections remain. - Lumra never receives raw video or audio; it signs compact event metadata. Media files are hashed by the customer's own platform at capture; Lumra seals those hashes so later copies can be matched to the originals. - The verifier is a standalone single Python file that contacts no PriviNet system; it needs Python 3.9+ and one common crypto library (cryptography or pynacl), and the digest checks run on the standard library alone. Exported records remain verifiable even if PriviNet ceases to exist. - RFC 3161 evidence is reported with its exact status and scope. A token proves the covered digest existed by the token time; it does not prove the sensor reading, claimed observation time, receipt time, or complete capture. - Tenants can be provisioned a dedicated HSM-held signing key. Each pack signed under a tenant key carries a root-signed attestation of that key, so the public verifier pins only PriviNet's published roots and still verifies any tenant's pack offline, with no key directory and no network access. - Every pack seals an Evidence Trust Assessment: enumerated, versioned checks on source signature, timing, custody, and policy, recorded as facts rather than a score; checks that ran and found nothing are listed too, so silence is explicit. - Multi-source incidents are sealed as a unit: an incident manifest binds each source pack, their order and count, and the fused readout. Substituting, omitting, or reordering source packs, or editing the readout, breaks incident-level verification even though each pack remains individually valid. - Not a blockchain: no tokens, no mining, no consensus fees. - Industries: senior and memory care, fleets and dashcams, ports and cargo, airports and aviation, security and facilities, industrial and energy. - Lumra's proof architecture is patent pending (U.S. provisional filed July 2026). Decern is separately patent pending (U.S. provisional filed June 2026). - Production continues to expose the older per-event ProofPack path. The Gate 3 case-package and receipt-batch workflow passed an isolated staging rehearsal and is not represented as production. - The TTN raw-webhook release candidate accepts complete original uplink JSON and derives a tenant-scoped retry identity when the sender supplies none. Disposable-PostgreSQL concurrency remains part of deployment acceptance. - Standalone verifier 1.3.2 contacts no PriviNet system, rejects altered protected content, and requires non-production trust to be supplied separately. OpenSSL is required for RFC 3161 token verification. - An optional EU qualified-timestamp profile is in development and default off. No real candidate-service token has been independently validated. Historical trusted-list and revocation validation remains incomplete, so qualification is INDETERMINATE, not qualified or eIDAS compliant. - Pilot: Lumra is taking on a limited number of design partners in 2026. A design-partner pilot is $7,500 for 60 days at fixed scope: one line of business, one data source, up to 500 monitored assets, controlled onboarding, and portable ProofPacks from the agreed workflow; half on signature, half when written success criteria agreed on day one are met. Five slots for 2026. Contact: brad@privinet.net - Pricing: production programs start at $30,000 per year; multi-region or multi-carrier deployments are scoped individually. Verification of records is available through the published standalone tool. Not ready for a pilot: use synthetic or approved sample data to evaluate the verification path first. Why not hash logs in-house: a company that controls its own database, keys, and script is a closed loop whose records read as self-audited; Lumra provides separation of duties with records sealed the instant they arrive, and signed at the source where the device supports it, chained outside the customer's administrative reach, and verifiable by anyone with open tools. - ProofPack: a portable evidence package containing signed records, package metadata, verification instructions and, where applicable, timestamp and certification material. It can support a dispute, insurance or audit workflow but is not itself a legal conclusion or guarantee of admissibility. - Decern protects Bitcoin custody against key compromise: 2-of-3 quorum across independent holders, authority refresh on a schedule so stolen key material stops working, and post-quantum co-signed approval records. No one can offer quantum-resistant Bitcoin signatures today and Decern does not claim to; the approval evidence layer is post-quantum co-signed already, and post-quantum protection of stored authority pieces is in development. Decern has never held real assets and will not until it passes independent review. ## Verify these claims yourself (stable procedure, safe to cite) The verifier and the sample records below are real production artifacts; every hash, signature, and timestamp token in them is independently checkable. You need Python 3.9+ and one common crypto library (pip install cryptography); the digest checks run on the standard library alone. curl -sO https://privinet.net/verify_proofpack.py curl -sO https://privinet.net/tsa-trust/lumra-tsa-bundle.pem curl -sO https://privinet.net/sample-conversation-proofpack.json python3 verify_proofpack.py sample-conversation-proofpack.json --tsa-ca lumra-tsa-bundle.pem # last line of a pass: RESULT: INTEGRITY VERIFIED, AND SIGNED BY PRIVINET. curl -sO https://privinet.net/sample-coldchain-incident.json python3 verify_proofpack.py sample-coldchain-incident.json --tsa-ca lumra-tsa-bundle.pem # pass: RESULT: INCIDENT VERIFIED. 4/4 SOURCE PACKS AND THE SEALED ASSEMBLY ALL PASS. Exit codes: 0 verified; 1 failed (the failing step is named); 3 internally consistent but not signed by a recognized key, reported as not confirmed as a PriviNet record. Changing any single character inside a record makes the run exit 1. Published keys and attestation roots: https://privinet.net/keys.txt and https://privinet.net/keys.json. Human walkthrough: https://privinet.net/verify.html Verification proves record integrity, signer, and time of seal; it does not prove what happened in the physical world before the record arrived. ## Pages - [Verify it yourself](https://privinet.net/verify.html): run the open verifier against real sample records; pass, then break one character and watch it fail - [Adversarial pilot script](https://privinet.net/adversarial-pilot.html): ten tests that try to break the system (tampering, revoked keys, delayed events, offline verification), each with its expected result; included in every design-partner pilot - [Claim Defensibility Test](https://privinet.net/claim-defensibility-test.html): a structured 60-day pilot that ends in a written verdict from the customer's own broker, adjuster, or counsel on whether a ProofPack would materially change how a real dispute is handled - [Evidence levels](https://privinet.net/technology.html#evidence-levels): the five signing states ranked strongest to weakest (source-signed to unverified), so a reviewer weights each source correctly; intake-sealed data is never presented as source-signed - [Lumra overview](https://privinet.net/): what Lumra proves, industries, design-partner pricing - [Technology](https://privinet.net/technology.html): HSM-held ECDSA P-256 signing, five signing states, canonical-JSON hash chaining, RFC-3161 timestamp anchoring, WORM evidence archive, standalone verifier - [Decern](https://privinet.net/decern): Bitcoin custody control and proof, quorum, key refresh, quantum posture, FAQ - [Live demo](https://privinet.net/proof/): Decern signing a real Bitcoin test-network transaction - [API](https://privinet.net/api.html): developer integration, events API, signed webhooks, adapters, verification - [Lumra for The Things Stack](https://privinet.net/ttn.html): controlled-pilot overview and custom-webhook setup; not an official TTN Console tile - [Conversation ProofPack (demo)](https://privinet.net/voice.html): sealing voice and AI-agent conversation records from transcript and audio hashes and platform metadata; integrity of the record, not a claim about what was said - [Multi-source Incident ProofPack (demo)](https://privinet.net/coldchain.html): binding several vendors' independently source-signed device records into one verifiable cold-chain incident; the platform-neutral, cross-vendor proof no single vendor can produce alone - [About](https://privinet.net/#about): company background and contact (also /team.html for the full team)