W3C Community Group · Launched Feb 2026

Verifiable trust
in global supply chains

We build the infrastructure for cryptographically verifiable trade — mapping EPCIS events to Verifiable Credentials, binding DIDs to supply chain actors, and embedding HS Codes, INCOTERMS®, and UCP 600 as normative vocabularies so every shipment becomes a self-proving trade document.

vsc-event-credential.jsonld
{
  "@context": [
    "https://www.w3.org/ns/credentials/v2",
    "https://w3c-cg.github.io/vsc/contexts/v1"
  ],
  "type": ["VerifiableCredential", "VscObjectEvent"],
  "issuer": "did:web:mfr.example.com",
  "credentialSubject": {
    "eventType": "ObjectEvent",
    "bizStep": "shipping",
    "hsCode": "3004.90",
    "incoterms": "CIF:2020:Mombasa",
    "tradeFinance": "LC:irrevoc:USD250K"
  }
}
8Participants
15Mailing list messages
3Open GitHub issues
5Industry verticals
2GitHub forks
Data from W3C archives · Updated on page load
About VSC
What the Verifiable Supply Chain framework does

VSC is a five-layer architecture that transforms physical supply chain events into self-contained, cryptographically provable trade documents. It maps EPCIS events to Verifiable Credentials, binds DIDs to supply chain actors, and embeds three normative vocabularies — HS Codes, INCOTERMS®, and UCP 600 — so a single credential answers what the product is, who bears commercial risk, and how payment is governed.

📋
EPCIS → VC Mapping
Lossless transformation of all five EPCIS event types into Verifiable Credentials with Data Integrity proofs. Every event becomes tamper-evident.
🔐
DID Identity Binding
Every credential signed by the asserting actor's DID. Verifiers resolve DIDs independently — no central authority required.
📦
Normative Vocabularies
HS Codes for commodity classification, INCOTERMS® for commercial terms, UCP 600 for trade finance. All standardized, all machine-readable.
🧩
Event Matrix
Five-dimensional cross-domain verification schema. Forward-compatible with +Dn extensibility. ML-ready feature extraction.
Specifications
Read the specs

Each specification is a standalone ReSpec document.

📘
VSC Requirements & Use Cases
The foundational specification — twenty functional requirements, eleven use cases, the Event Matrix, Regulatory Rule Compiler, and all three normative vocabularies.
Open specification
⚗️
Pharma Supply Chain Profile
VC/UORA credential schema for pharmaceutical traceability. Maps DSCSA, FDA identifiers, and GS1 EPCIS to W3C Verifiable Credentials.
Open specification
⛏️
Critical Minerals Traceability
Provenance and due-diligence credentials for lithium, cobalt, and rare earth elements. Aligned with EU Battery Regulation and OECD guidance.
Open specification
🏛️
Trust Framework Template
Customizable governance, accreditation, and compliance rules for supply chain networks issuing verifiable credentials.
Open specification
Industry profiles
VC/UORA profiles by vertical

Reusable, public credential schemas tailored to specific industry regulatory contexts.

⚗️
Pharmaceuticals & Healthcare
Lot-level chain-of-custody attestation and serialization credentials aligned with US drug traceability law.
In progress
DSCSAFDA 21 CFRGS1 EPCIS
⛏️
Critical Minerals
Provenance and due-diligence credentials for lithium, cobalt, rare earths, and other strategic minerals.
Draft
CBAMEUDRISO 14001
🚗
Automotive & Aerospace
Component traceability, recall management, and EV battery passport credentials for multi-tier supply chains.
Planned
EU Battery Reg.AS9100
🌾
Food & Beverage
Farm-to-fork provenance, allergen disclosure, and deforestation-free sourcing attestations.
Planned
EUDRGS1 EPCISFSMA 204
💎
Luxury Goods
Anti-counterfeiting authenticity credentials and ownership attestation linked to the EU Digital Product Passport.
Planned
EU DPPCSRD
💻
Electronics
Component origin, conflict minerals disclosure, and repair/recycle credentials for the circular economy.
Planned
EU ESPRDodd-Frank §1502
Deliverables
What the group produces

Four concrete output types — all public, all under W3C Document License.

📘
Industry Blueprints
A library of public, reusable VC/UORA profiles for major supply chain verticals.
Formal JSON-LD credential schemas
Regulatory mapping documents
Issuer and verifier role definitions
Data minimization guidance
🔧
Interoperability Toolkit
Specifications and software tools for translating supply chain event data into verifiable attestations.
EPCIS-to-VC mapping specifications
Translation libraries (Python, TypeScript)
Conformance test suites
Sample implementations
🏛️
Trust Framework Template
Customizable governance, accreditation, and compliance rules for credential issuers.
Trust anchor accreditation criteria
Governance models for consortia
Dispute resolution frameworks
Liability & legal entity mapping
📊
Business Implementation Guide
Non-technical playbook with quantified ROI case studies and pilot program templates.
Anti-counterfeiting ROI models
ESG & Scope 3 reporting guides
Recall management reference arch.
Vendor evaluation criteria
Standards alignment
Grounded in real regulations

VSC maps directly to regulatory requirements across pharmaceuticals, food safety, critical minerals, and trade finance.

Regulatory frameworks
US DSCSAPharma
EU CBAMMinerals · Industrial
EUDRFood · Timber
EU Digital Product PassportLuxury · Electronics
EU Battery RegulationAutomotive · EV
CSRDCross-vertical
FSMA 204Food & Bev.
Data & technical standards
W3C VC Data Model 2.0Core standard
W3C DID CoreIdentity layer
UORAPhysical assets
GS1 EPCIS 2.0Event data
WCO HS NomenclatureCommodity codes
ICC INCOTERMS® 2020Commercial terms
UCP 600Trade finance
Community
Founders & participants

Proposed on 3 February 2026 by Amir Hameed Mir and launched on 21 February 2026 with 5 founding supporters. Chaired by Amir Hameed Mir (Sirraya Labs), with W3C Staff Contact Ian Jacobs.

8 participants as of May 2026 · View full list on W3C →

Mailing list
Recent discussion

All communication is public and archived at lists.w3.org. 15 messages across March–May 2026.

Open to anyone.
No W3C membership required.

We are a community initiative — anyone with a free W3C account can join, contribute to specifications, and participate in discussions. All work is public and licensed under W3C Document License.

Shape the VSC Requirements and Use Cases specification
Contribute VC/UORA profiles for your industry vertical
Represent your industry's regulatory and implementation constraints
All discussion archived publicly at lists.w3.org
Join on W3C →View GitHubEmail the list