Six steps, all local, nothing sent anywhere: register a unique aperiodic mark, decide which devices are allowed to read it, program and reprogram its meaning, verify against a protected chain of custody, defeat a copy attack, then take the mark into the physical world and scan it back in with your camera. Marks are cryptographically unreadable to unassigned devices.
And a Nocmark is not limited to a physical object. The same mark can be shown on a screen, projected into a scene, or serve as a file’s identifier inside a system — bound to a user, carried in an image chain. On a crate or inside your software, an authorized read fires your programmed action. See digital & file identity →
This page is a simulation of the core principles, not the production system. Everything below runs inside an ordinary browser tab, so the response times you observe are substantially slower than the real thing — a browser adds JavaScript execution, canvas rendering, and UI overhead that production never pays.
In production, Nocmark runs on the silicon you already field — the cameras, drones, and sensors in place today. This page is a simulation of the core principles in your browser, not the production system, so you can see how it holds without installing anything.
This demo shows the principles. The production tool is the Nocmark Studio — customized for you after a briefing and set up with our team on a Studio install. That's where you configure what this demo only hints at:
Registration, provisioning, and reprogramming are written to the chain of custody; every read resolves locally against it — and only on hardware you have assigned.
Identity → unique aperiodic mark, sealed into a protected block.
Only devices you provision can decode the mark. Everything else sees noise.
Attach an action, then reprogram over the air — the state chains forward.
Two scores: exact chain integrity + recognition confidence.
Clone the mark, advance the chain, watch the clone die.
Print it or show it on a phone — verify through your camera.
Enter an owner or item identity. A unique, non-repeating aperiodic mark is generated on your device and sealed into the chain below as a new block, linked to the block before it.
A Nocmark is cryptographically unreadable to unassigned devices. You decide which hardware holds the key. Toggle provisioning below (simulated), then attempt a read as this browser — first without the key, then with it.
Anti‑enumeration: a photograph of a marked asset yields an unassigned device nothing — no identity, no data, no inventory intelligence.
Every registered mark carries a programmable action that fires on a verified match by an assigned reader. Change it any time — the mark is re-tasked without re-registering, and each state chains to the hash of the one before it.
Production verification is two-layered by design: an exact SHA‑256 chain check — where a single altered bit fails — and an approximate recognition score that tolerates real-world capture noise. Both run locally, timed live below.
The first question every engineer asks: what stops a photocopy? Two things. To an unassigned device, a copy is cryptographic noise (Step 2). And against assigned readers, a copy carries a frozen state — the moment the genuine mark is reprogrammed, the chain head advances and the stale clone fails.
Honest note: a clone presented to an assigned reader before the next state change is the narrow residual case — managed in deployment with state‑rotation policy matched to the asset's risk. Rotate faster, and the window closes.
Download the mark, print it or open it on a second phone, then verify it through this device's camera — or upload a photo of it. Recognition is approximate by design: it reports how many pattern cells differ and whether that lands inside the threshold.
