Proof of Plate

revolutionizing food industry supply chain. Proof of Plate is a product passport system for food supply chains. Today, consumers see claims like “organic,” “lactose-free,” “no added sugar,” or “safety tested,” but they usually have no way to verify whether those claims are real, current, or backed by actual evidence. Proof of Plate turns each product batch into a scannable, tamper-evident passport.

A consumer scans a QR code on a product, such as our ultra-filtered milk or organic apple juice demo batches, and instantly sees the product’s verified claims, certification evidence, supply-chain timeline, trust score, recall state, and on-chain proof links. The app connects real product data to Sui, Hedera, and Walrus so each claim can be traced back to an immutable event, token, object, or evidence hash instead of just a database row.

The goal is to make food provenance understandable at the point of purchase. Regulators, brands, certifiers, retailers, and consumers can all inspect the same source of truth: what was claimed, who attested it, when it was recorded, what evidence supports it, and whether anything changed later. We also built an AI verifier that can answer plain-English questions like “Is this product lactose free?” or “What evidence supports this organic claim?” by grounding responses in the product passport data.

Proof of Plate is designed for the real world: scan first, understand fast, verify deeply.

Proof of Plate is a Next.js monorepo with a consumer-facing product passport UI, admin/demo flows, and on-chain verification integrations across Sui, Hedera, and Walrus.

On Sui, we use Move to represent the product passport’s verification layer. Each product batch has on-chain state for claims, score updates, evidence commitments, and recall status. We also use Sui soulbound tokens for certifications and third-party verifications. These SBTs are non-transferable, so a certification cannot be casually sold, moved, or reassigned after it is issued. That makes them a strong fit for food attestations like organic certification, lab testing, safety checks, and supplier verification.

On Hedera, we use multiple native services. HCS acts as an ordered audit log for claim intake and lifecycle events, creating an append-only timeline of what was submitted, verified, or changed. HTS is used to tokenize the product itself: each product passport can be represented as a Hedera token carrying the product’s identity, batch metadata, and verification context. This gives the product a durable tokenized representation while Sui and Walrus handle additional proof and evidence layers.

Walrus stores decentralized evidence artifacts such as claim manifests, supporting documentation, and verification files. The UI displays hashes and storage references so users can verify that the evidence behind a claim has not been silently changed.

The frontend is built around the QR scan experience. A consumer scans a product and sees its trust score, verified claims, certifications, supply-chain timeline, Sui explorer links, Hedera HCS/HTS records, Walrus evidence, and an inspector mode for deeper verification. We also integrated a Claude-powered AI verifier so users can ask natural-language questions like “Is this product lactose free?” or “What evidence supports the organic claim?” and receive grounded answers based on the actual passport data.