📦
Article 6
Recyclable Design Requirements
All packaging must meet recyclability design criteria.
EU Regulation 2025/40
Meet EU Packaging Regulation 2025/40 with blockchain-verified compliance.
Effective August 2026 — Is your packaging ready?
What is PPWR?
Three articles redefine how packaging is designed, declared, and labelled across the European single market.
Article 6
All packaging must meet recyclability design criteria.
Article 8
Manufacturers must declare material content — immutably and verifiably.
Article 11
Physical labels replaced by machine-readable digital passports.
How It Works
Upload material composition, recyclability data, and certifications.
Your product gets a unique, regulation-compliant URL.
QR code printed on packaging. Anyone can verify compliance instantly.
Privacy-first Verification
We use Midnight blockchain ZK proofs to let regulators verify compliance without exposing your supplier details or trade secrets.
Every passport version is anchored on-chain. Records cannot be silently rewritten after publication.
Zero-knowledge proofs let regulators check compliance without seeing supplier names or formulations.
A continuous, time-stamped trail from factory data to consumer scan — exportable on request.
Anti-greenwashing
Three independent layers — each closing a specific path a brand could otherwise take to make a passport claim it can't back up.
Layer 1 · B3
Every cert PDF's SHA-256 fingerprint is anchored on-chain.
If a brand swaps the certificate file after publication, auditors detect the tamper immediately — not just metadata, but the full content fingerprint. Pre-publish guard rejects any cert whose stored file or hash is missing.
schema_version 4 · hex CHECK constraint at DB layer · 14-item test matrix
Layer 2 · B2
Failed anchoring attempts never enter the public audit trail.
Successful attestations and failed attempts live in separate tables. Brands cannot fake a clean record by hiding failures — every attempt is recorded for authorized auditors, while the public-facing chain shows only confirmed anchors.
Defense-in-depth status filter across 5 read paths · forensic admin endpoint
Layer 3 · B4
What you preview is byte-for-byte what gets anchored.
The passport UUID is reserved at preview time and re-used at commit. There is no preview-vs-commit drift: if a single field changed between Step 4 and Step 5, the commit returns 422 and the brand re-previews.
Reserved UUID · 5-condition 422 guard · 30 min TTL · 7-day forensic GC
Verify it yourself
Every audit token issues a ZIP containing the canonical passport bytes, a filename manifest, every cited certificate file, and a stdlib-only Python script. No dependency on our servers. No vendor lock-in. If we disappear tomorrow, the audit trail still verifies.
$ unzip ppwr-audit-bundle-*.zip $ cd ppwr-audit-bundle-* $ python3 verify.py Bytes read: 4392 Expected: 9f3c1abe...8d24 Actual: 9f3c1abe...8d24 OK: 3 cert file(s) match recorded hashes RESULT: PASS - canonical.json matches the on-chain anchor.
Pricing Model
Setup
One-time engagement to connect your ERP, validate test data, and pass first-article review.
Per-Unit
Volume-based metering aligned with SKU launch cycles. No idle subscription fees.
Annual
Continuous regulation tracking, schema upgrades, and long-term passport storage.
Pricing based on volume. Contact us for a quote.
Contact
Join the first wave of PPWR-compliant manufacturers.