Verify the route.
Not just the identifier.

RouteProof is a software-based cryptographic system for verifying authorized pharmaceutical distribution routes.

A valid identifier can still appear at the wrong recipient. RouteProof exposes that contradiction. It checks the observed recipient against the authenticated route, rejects conflicting route continuations, and verifies that pack identities remain correctly assigned when shipments are split or merged.

The result: independently verifiable route evidence — to pinpoint contradictions, investigate suspected diversion, and reproduce verification results. Built to complement existing verification systems and make the authorized route verifiable as a continuous chain — from manufacturer to intended recipient.

Initial focus: European pharmaceutical supply chains.

Illustrative scenario. Not a recording of the evaluation demo.
Video description and text

Video description

RouteProof is a software-based cryptographic system for verifying authorized pharmaceutical distribution routes.

This 74-second film is an illustration, not a recording of the evaluation demo. An illustrated pharmaceutical carton introduces the difference between an identifier and an authorized route. Scenes follow a shipment from a manufacturer through a distributor toward a hospital, and show cartons being split into separate groups. A hospital and a pharmacy represent the expected receiver A and the observed receiver B. A side-by-side comparison and a red cross highlight the route/context mismatch. The film then presents RouteProof's route-verification and evidence capabilities, before closing with the RouteProof logo and the message: Verify the route. Not just the identifier.

Visible main text

  1. RouteProof™
  2. A valid code is not the whole story.
  3. Where is this product supposed to be?
  4. Follow the authorized route.
  5. Even when a shipment is split.
  6. Expected at A. Observed at B.
  7. Make the contradiction visible.
  8. Understand the mismatch. Verify the claim.
  9. Beyond the identifier. Verify the authorized route. Detect unexpected recipients. Reject conflicting route claims. Validate shipment splits and merges.
  10. Evidence for action. Flag missing or outdated evidence. Reproduce verification independently. Support diversion investigations. Complement existing verification systems.
  11. RouteProof™ / Verify the route. Not just the identifier.

A valid identifier is not a verified route.

An identifier can be valid while the recipient is wrong. A shipment can be split or merged. Two records can look credible while describing incompatible onward transfers. And a valid historical record may not establish the current state.

RouteProof checks how the recorded transfers connect, who is authorized to make them, and which pack identities belong to each shipment group. The result is a check of the evidenced route as a connected chain — not merely an isolated identifier or event.

No verified claim without the required evidence.

If evidence required for a particular claim is missing, RouteProof does not return a positive verification result for that claim.

Verify continuity. Expose contradictions.

Verify route continuity and authorization

Check that the recorded transfers connect into a coherent route and satisfy the applicable authorization requirements under the selected trust rules.

Expose recipient mismatches

Compare the observed recipient with the authenticated route. Identify a mismatch even when the original route history remains valid.

Reject conflicting continuations

Reject incompatible onward transfers that compete to continue the same current route state. They cannot both be accepted as its current continuation within the supported system scope.

Verify shipment splits and merges

Check which pack identities belong to each group when shipments are divided or recombined. Detect invalid duplication, insertion or omission in that digital membership.

Distinguish history from current evidence

Separate what a past record establishes from the evidence needed for a current route claim. Identify missing, outdated or mismatched evidence required to support that claim.

Reproduce verification independently

Recheck a defined route claim outside the presentation interface and originating database, using the required evidence and explicitly selected trust.

Expected at A.
Observed at B.

A shipment follows an authorized route from a manufacturer through a distributor to receiver A. The same pack identity is then presented in the context of receiver B.

The route to A can remain valid. It does not establish that B is the intended recipient.

RouteProof identifies the mismatch between the observed recipient and the authenticated route, providing a concrete starting point for investigation.

Manufacturer → Distributor → Expected receiver A. Observed receiver B is highlighted separately as a route/context mismatch.
Illustrative scenario. The authorized route ends at receiver A and remains unchanged. Receiver B represents a separate observation that does not match that route. The dashed red connection marks the mismatch; it does not establish the shipment’s actual physical path to B.

Route evidence you can act on — and independently check.

For manufacturers and supply-chain participants

Verify authorized handovers, check pack assignments after splits and merges, and identify conflicting route records through a consistent set of verification rules.

For market surveillance, customs and investigators

Use authenticated route evidence to investigate unexpected recipients, suspected diversion, theft or other supply-chain irregularities. A mismatch identifies a contradiction; establishing its cause still requires investigation. It is not by itself proof of a particular offence or a counterfeit medicine.

For regulatory and infrastructure evaluators

Test a working reference implementation, reproduce defined verification results, and assess the data, trust and integration requirements for a real deployment.

For strategic technology partners and acquirers

Evaluate a coherent cryptographic system backed by an executable demonstration and reproducible technical evidence. Examine its capabilities, limitations and integration potential through an agreed private evaluation.

Working technology. Testable results.

A working reference implementation performs real cryptographic checks in controlled pharmaceutical supply-chain scenarios using synthetic data. The scenarios cover valid routes, recipient mismatches, conflicting continuations, split-and-merge errors, and missing or outdated evidence.

Request a private evaluation to inspect the results and agree the scope of a technical review. Access to technical materials is arranged separately according to that scope.

What the verification establishes

RouteProof verifies digital route claims against the required evidence and selected trust. It complements existing traceability and verification environments; it does not replace regulatory repositories or required safety mechanisms.

A valid digital route does not by itself prove a medicine’s chemical contents, the truth of every real-world statement entered by a participant, or that every physical movement was recorded. The completeness of the real-world record depends on the participating actors and the data they capture.

The reference demonstration is not evidence of a live pharmaceutical deployment, regulatory approval or independent third-party certification.

Presented by Picyboo Cybernetics Inc.

RouteProof brings cryptographic route verification into an executable system. For demonstration access and further technical information, contact Picyboo Cybernetics Inc.

Request a private evaluation.

Tell us which organization you represent and which route-verification questions you want to examine. Contact Picyboo to discuss an appropriate evaluation scope and access arrangements.

Contact Picyboo

Access is arranged individually. Demo credentials and technical downloads are not published on this page.

RouteProof™ — Presented by Picyboo Cybernetics Inc.

Verify the route. Not just the identifier.