privinet.net valid

PriviNet

PriviNet Inc builds verification infrastructure. Lumra seals operational event

For agents: PriviNet Inc builds verification infrastructure; Lumra seals operational event records, with open verifier tools and pilot programs for design partners.

verification infrastructurelumratamper evidencesealed recordsincident verification

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T21:20:13.059Z. Cached copy · Source on privinet.net

# 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 de
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=privinet.net · GET /v1/domain/privinet.net · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for privinet.net:
1. POST https://agentwebmap.com/v1/sites/privinet.net/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://privinet.net/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/privinet.net/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/privinet.net).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.