Protocol Walkthrough

The chain,
step by step.

Step 1 / 6

Identity created.

500 serials are registered under batch BCH-49A2. Each serial is cryptographically signed — mathematically bound to this manufacturer, this batch, this moment.

BATCH_REGISTERED

BCH-49A2 → 500 serials assigned

Signature: 7f3a… Hash: a4f2…

Step 2 / 6

Custody transferred.

The batch ships to a regional distributor. The custody claim is accepted by the eligibility gate — both parties are verified, the state is ELIGIBLE.

CLAIM_ACCEPTED

SRL-7F3A → dist-01 (Mumbai CFA)

State: ELIGIBLE Latency: 12ms

Step 3 / 6

Anomaly detected.

A scan event arrives from an unexpected region — Signal 3 fires. The serial was already scanned 400km away 6 minutes ago. This is physically impossible.

SIGNAL_3: DUPLICATE_SCAN

SRL-7F3A flagged → State: RESTRICTED

Distance: 412km Gap: 6min Confidence: HIGH

Step 4 / 6

In transit. Verified.

The legitimate shipment continues. Logistics custody is recorded with GPS coordinates. The hash chain grows. Every transfer is sealed and immutable.

CUSTODY_RECORDED

logistics-07 → pharmacy-12 (Pune)

GPS: 18.5204°N, 73.8567°E Chain: intact

Step 5 / 6

Authenticity confirmed.

The pharmacy scans the serial at point of receipt. Five detection signals run in parallel. All clear. Verification returns ELIGIBLE in 47ms.

VERIFY_RESULT: ELIGIBLE

SRL-7F3A — 4 signals clear

Latency: 47ms Merkle proof: valid Trust: GREEN

Step 6 / 6

Every product. Proven.

The consumer scans the QR code. A certificate is issued — cryptographically provable, independently verifiable, tamper-evident. The supply chain doesn't lie.

CERTIFICATE_ISSUED

SRL-7F3A → consumer verified

Hash: 9c3f… Proof chain confirmed

See it live.

The walkthrough above shows the protocol in theory. A 30-minute demo shows it running on your supply chain.