A consumer PWA that verifies any Purity Receipt in 50ms. No app store. No login. No tracking.
Point your phone camera at any QR or NFC tag on Hive-certified packaging. PurityScan fetches the signed Purity Receipt from the issuer URL embedded in the tag, calls the edge verifier at thehiveryiq.com/verifier, and renders a trust card in under 50ms. Soil signature, GMO status, mRNA-vaccine status, pesticide residue, EU-banned-additive check, and 7 FSMA 204 KDEs — all cryptographically verified, all visible at the shelf.
Tagline: Scan it. Trust it. Signed by soil.
Free for consumers. Brands pay per-scan. Hive treats this like a CDN: minimal cost, maximal reach.
This page is a product specification. PurityScan is planned for Q3 2026. The actual PWA ships separately from this spec document.
CSS-only mock. No emoji. Obsidian mobile frame.
The trust card is what the consumer sees after scanning. Every row is a cryptographically signed attestation — not a marketing claim. If the cert is expired, the header shows a clear "Expired" badge instead of "Verified." If the brand is not a Hive customer, PurityScan still verifies any /v1/purity/ cert from any issuer.
If a cert has passed its valid_until timestamp, the header chip switches from green "Verified" to red "Expired". The attestation rows remain visible so the consumer can see what was true at issuance time. No ambiguity.
PurityScan is a Progressive Web App shell. No native SDK. No app-store review. Install is optional — the URL itself is the product. The architecture is designed so that verification logic runs at the edge, not on a central server.
Planned — Q3 2026
Loaded from thehiveryiq.com/purityscan/. Service worker caches the shell on first visit. Subsequent loads are instant — sub-100ms from cache, no network required for the UI skeleton. Manifest enables "Add to Home Screen" on iOS and Android.
service worker + web manifestCamera access via getUserMedia(). QR decoding via jsQR — a pure JavaScript library that runs entirely in the browser. No pixels leave the device. NFC tap via Web NFC API where supported (Q4 2026). The URL is decoded client-side before any network call is made.
getUserMedia + jsQR — client-side onlyThe QR URL contains an issuer DID and a cert_id. PurityScan resolves the DID document, extracts the cert endpoint, and fetches the signed Purity Receipt JSON directly from the issuer's server. Hive does not proxy this request. The consumer's browser contacts the issuer directly, preserving issuer sovereignty.
DID resolution + direct HTTPS fetchThe signed cert is forwarded to thehiveryiq.com/verifier — a Cloudflare Workers deployment. The verifier checks the ML-DSA-65 and Ed25519 signatures, confirms the chain hash linkage, and returns a structured verification result. Cloudflare p99 latency is under 50ms from any major metro.
Cloudflare Workers · 50ms p99Consumer phone | | getUserMedia() + jsQR (client-side, no network) | v QR decoded → URL: https://thehiveryiq.com/purityscan/?cert=<id>&issuer=<did> | | DID resolution (browser → issuer DID document) v Issuer server → returns signed Purity Receipt JSON (2–8 KB) | | POST /verify (browser → Cloudflare Workers) v thehiveryiq.com/verifier (Cloudflare edge, 50ms p99) | - ML-DSA-65 signature check | - Ed25519 hybrid check | - chain hash linkage | - expiry check v verification result → trust card rendered in browser no server-side session, no log of the consumer, no PII transmitted
PurityScan is designed from the ground up to collect zero consumer data. The following list is explicit, not aspirational. CCPA and GDPR posture is identical: nothing is collected, so there is nothing to disclose, sell, or delete.
No personal information is collected. There is no data to disclose, sell, or make subject to a deletion request. PurityScan does not trigger CCPA obligations because it processes no personal data.
No personal data within the meaning of GDPR Article 4(1) is processed. No lawful basis for processing is required because no processing occurs. Hive is not a data controller for consumer scans.
Cloudflare sees request metadata (IP, user-agent, timestamp) for the duration of WAF processing. Hive does not receive, log, or store these fields. This is the same posture as any static website hosted on Cloudflare.
The URL embedded in the tag is designed to be minimal. The cert_id is a 22-character base58 string. The issuer DID is truncated to a compact form. Total URL length: under 90 characters, which fits in a QR code version 4 (33×33 modules) at error correction level M.
cert_id is a 22-character base58-encoded SHA3-256 prefix of the receipt payload hash. It is deterministic — the same receipt always produces the same ID. The verifier uses it to look up the full cert at the issuer endpoint.
issuer is a DID (Decentralized Identifier) in the form did:hive:<namespace>:<slug>. PurityScan resolves the DID document from thehiveryiq.com/did/<did> to find the cert endpoint. Any issuer can host their own DID document outside Hive infrastructure.
The same URL is encoded as an NDEF URI record on the NFC tag. NFC tap on Android uses the Web NFC API. iOS 14+ supports background NFC tag reading for HTTPS URLs natively. No app required on either platform. NFC support planned Q4 2026.
Four steps from Purity Receipt to printed QR. No proprietary hardware required beyond a FarmGuard deployment or a direct API key. The brand owns its signing keys.
# Issue a Purity Receipt for a specific SKU curl -X POST https://thehiveryiq.com/v1/purity/cert/issue \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "sku": "SUNRISE-APPLE-HONEYCRISP-2026", "farm_did": "did:hive:farm:sunrise-orchards", "attestations": { "gmo_free": true, "mrna_free": true, "pesticide_free": true, "eu_additive_free": true, "fsma_204_complete": true, "soil_signature_axes": [17, 18, 20] }, "valid_days": 90 }' # Response (200 OK) { "cert_id": "7xKqNmB4RpLdA3fYe8Wv2z", "issuer": "did:hive:farm:sunrise-orchards", "issued_at": "2026-06-15T08:00:00Z", "valid_until":"2026-09-13T08:00:00Z", "qr_url": "https://thehiveryiq.com/purityscan/?cert=7xKqNmB4RpLdA3fYe8Wv2z&issuer=did:hive:farm:sunrise-orchards", "sig": "ML-DSA-65:0x8f3a...2b1c" }
PurityScan is free for consumers. Brands pay per scan. Hive's cost model treats verification like a CDN: minimal marginal cost, billed to the brand, not the shopper. The $99/month minimum ensures service viability while keeping the per-scan rate competitive with any provenance alternative.
| Option | Cost per scan | Monthly minimum | Scans included at minimum | Provenance data |
|---|---|---|---|---|
| PurityScan — Tier 1 Hive | $0.0001 | $99 / month | Up to 1M scans/mo | Full Purity Receipt, 6 attestation axes, FSMA 204 chain |
| PurityScan — Tier 2 (over 1M) Hive | $0.001 | $99 / month base | Billed on usage above 1M | Same full receipt |
| Blockchain food-trace platforms Alt | $0.05 – $0.20 | Varies; typically $500+ | 2,500 – 10,000 | Supply-chain hashes; limited attestation content |
| Traditional barcode / GS1 Alt | $0.00 | GS1 membership: $250 – $10K/yr | — | No provenance, no attestation, no signing |
A brand shipping 500,000 units per month, with 10% QR scan rate, generates 50,000 scans/month. At $0.0001/scan: $5.00 in scan fees + $94 minimum overage = $99/month total. Cost per unit scanned: $0.002. Cost per unit shipped: $0.0002. Compare: a blockchain alternative at $0.05/scan would cost $2,500/month for the same volume.
PurityScan is designed to coexist with, not replace, existing food-labeling infrastructure. The QR URL format is compatible with GS1 Digital Link. The attestation schema is designed to map to Open Food Facts fields. FSMA 204 KDE coverage is complete.
The PurityScan URL can be structured as a GS1 Digital Link resolver URL, allowing a single QR to resolve to both a GS1 product page and a Purity Receipt. The cert and issuer params are passed as custom query-string extensions, which GS1 DL 1.1 permits.
Purity Receipt fields including GMO status, additive list, and country of origin are designed to map directly to Open Food Facts product fields. Brands that submit their Purity Receipts to OFF can enrich the public database with cryptographically signed provenance data.
The Purity Receipt chain covers all seven FSMA 204 Key Data Elements (traceability lot code, quantity, unit of measure, product description, location description, date, and reference document) at each Critical Tracking Event (growing, receiving, transforming, shipping). FarmGuard generates these automatically; PurityScan surfaces them to the consumer.
EU 1169/2011 requires country-of-origin labeling for meat, fish, honey, olive oil, fruit and vegetables. PurityScan's soil signature (Axis 17) provides a farm-level geographic attestation that is consistent with EU 1169/2011 origin requirements. EU-banned-additive check covers the 12 additives permitted in the US but banned under EU food safety law.
Every item below is planned, not shipped. Dates are targets, not commitments. PurityScan does not exist as a shipping product today. This page is a product specification.
The live camera scan demo will be available when the PWA shell ships. Until then, the trust card mock above reflects the target consumer experience.
Hold steady over any Hive-certified QR tag
This is a product specification page, not the running PWA. The actual PWA ships separately.
Book a 30-minute integration call. We walk through cert issuance, QR encoding, and the brand dashboard. Most brands are live in under a week.