Don't take the claims on faith — run them. In five steps, prove the core of Photichain to yourself, right in this browser:
And an image-block isn’t limited to photographs. The registered image can be data, code, or a file; a transaction or exchange, where a verified match fires an action you design; a medical scan; satellite imagery; or even your existing barcode or QR code, reprogrammed — the code keeps doing its everyday job for every ordinary scanner, while Photichain adds a verified identity underneath
The core loop — four steps, one protected chain. Registration and reprogramming are both written to the chain of custody; verification and recognition both resolve locally against it. Below the loop: reader gating, field recognition, and challenge tests.
Choose or capture an image. It is fingerprinted on your device and sealed into the chain below as a new image-block, linked to the block before it.
On a phone, this lets you take a photo or pick from your library.Every registered image carries a programmable action that fires on a verified match. Change it any time — the image-block is re-tasked without re-registering, and the change is recorded in the chain of custody.
Present an image. It is checked against the protected chain locally, with no server call. A registered, unaltered image passes and its programmed action executes; anything altered or unknown fails. The few milliseconds shown is browser overhead on a general-purpose CPU — a ceiling, not the target. In firmware on a DPU it is engineered to run far faster.
This takes an image you registered, changes a single pixel, and runs the same verification. The altered copy no longer matches its protected image-block — tamper-evidence in action.
A protected image-block is cryptographically unreadable to unassigned devices — you decide which hardware holds the key. Toggle provisioning below (simulated for this demo), then attempt a read as this browser: first without the key, then with it. The anti‑enumeration consequence matters as much as the security one — to everything you have not assigned, your protected assets yield nothing: no identity, no data, no inventory intelligence.
Display one of your registered images on another screen — or print it — then point your camera at it. Photichain recognizes the genuine, registered image and resolves it. A photo of a photo isn’t the sealed original, so it doesn’t carry the same proof. What you assign is what verifies.
On a phone, tap to take a photo or pick from your library.Verification here is two-layered by design: an exact layer (Step 3) where changing a single bit fails, and an approximate recognition layer (Step 6) that tolerates real capture noise while rejecting different content. These challenges show where each layer draws its line — run them and watch the system explain its own boundaries.
Each block below is sealed against the one before it. Registrations and reprogramming events are both recorded, so re-tasking an image-block never breaks the custody trail.
What you just used is the floor, not the ceiling. Every capability on this page scales up in the production architecture:
This page runs in a sandboxed browser. The production architecture is resident on the hardware you already own — CPUs, DPUs, and SmartNICs in the field, or servers and workstations inside your own network — and can equally be designed into hardware you are still developing, so it ships native rather than retrofitted. Either way, it verifies at the point of capture.
Recognition here is deliberately simple. The patented architecture specifies AI-based computer vision — built to recognize registered images through the lighting, angles, and distances of real field conditions.
You reprogrammed one image-block over the air. The same patented capability is designed to re-task verification logic, identities, and triggered actions across an entire deployed fleet — with no recovery, no replacement.
This browser demo is the floor — the simplest public expression of Photichain. Response Images has also built and exercised an enterprise-scale prototype on enterprise cloud infrastructure, running one-way (point-of-capture) and two-way (round-trip) verification pipelines — the program behind the consensus-free architecture presented across this site. Full instrumented benchmarking is the current milestone.
To arrange a technical briefing on the prototype program — or to explore developing the capability for your systems and sector — get in touch.
Request a technical briefingWhat you just did to an image-block, Photichain does to any digital object — one engine, edge and digital. Instead of a captured image, seal a transaction, a document, a record, or a data feed the moment it’s created, and verify it locally as it moves between systems, data centers, or regions.
Confirm a transaction, claim, or handoff is genuine and unaltered as it happens — both sides checked locally, with a record kept when you want one.
Seal a contract, scan, manifest, or evidence file and know at every step it’s the same one — change a character and it shows.
When data travels between sites or across the world, confirm it arrived exactly as it left — checked at both ends, no trip to a middleman.
Most sectors use both: capture at the edge and verify digital objects in motion. See the digital page for the full picture.