Lumra signs an event where it happens, links it into a hash-chained ledger, and exports a bundle that a standalone tool can verify with no dependency on PriviNet. Below is exactly how that works.
Three stages. Each meaningful event flows left to right, gaining a signature at the source, a place in the chain, and a path to verification that needs nothing from us.
Taps an NFC checkpoint or scans a code, then signs the event.
Witnesses a sensor reading and signs it with a per-tenant key.
Cameras, dashcams, IoT platforms, and sensors arrive by webhook.
Normalize incoming events and forward any upstream signatures honestly.
Meaningful events, each linked to the hash of the entry before it.
High-volume routine readings, Merkle-anchored into the ledger.
The ledger exports as a portable, signed bundle.
Checks every signature and the full chain. No PriviNet runtime.
An auditor, insurer, regulator, or counterparty can run it themselves.
A worker phone signs an event with an Ed25519 key gated behind the device biometric, so the signature attests that a specific person, on a specific enrolled device, acted at a specific time.
An enrolled gateway signs a witnessed sensor event with a per-tenant key. Proof is created at the edge, not reconstructed later from logs.
Events from MIOTY gateways, generic sensors, cameras, and dashcams arrive through webhook adapters. Lumra normalizes them and writes them into the ledger.
When an upstream device provides its own signature, Lumra forwards it without claiming to have verified it, marked vendorSignatureUnverified. The system never overstates what it can prove.
Putting every raw reading into the chain would bloat it and slow verification. Lumra separates the record that must be permanent from the stream that does not.
Carries only meaningful events: check-ins, custody handoffs, sensor anomalies, threshold crossings, and batch anchors.
Carries routine readings that do not each need to be permanent proof, kept available for a short window.
The point of a proof layer is that you do not have to trust the company that wrote it. Lumra's verifier is a standalone tool that anyone can run against the exported bundle.
The verifier is a standalone Node.js tool. It does not call our servers, our database, or our API. It needs only the signed export and the public keys.
An auditor, insurer, regulator, or counterparty checks the record themselves. Trust comes from the math, not from PriviNet's word.
If PriviNet were gone tomorrow, an exported bundle would still verify. The proof outlives the vendor.
Illustration of verifier output. Change one byte in the export and verification fails, naming the broken entry.
Lumra uses well-understood primitives. The value is in where they are applied, at the source, end to end, not in inventing new cryptography.
This is a working build, not a concept. The core signing, ledger, anchoring, and verification paths run now.
Shipped: source signing, hash-chained ledger, Merkle-anchored telemetry, MIOTY and HTTP webhook ingest, and the standalone verifier. On the roadmap: deeper hardware-level attestation and broader source integrations. We will not describe a capability as available until it is.
A phone tap, a signed event, an independent verification. Tell us your environment and we will scope a pilot.
Request a pilot