Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
LABS
Glossary

W3C VC Data Model

The W3C Verifiable Credentials Data Model is a World Wide Web Consortium (W3C) recommendation that defines a standard data model for expressing cryptographically secure, privacy-respecting digital credentials on the web.
Chainscore © 2026
definition
STANDARD

What is the W3C VC Data Model?

The W3C Verifiable Credentials Data Model is the foundational international standard that defines the structure, syntax, and core semantics for creating, issuing, and verifying cryptographically secure digital credentials on the web.

The W3C Verifiable Credentials (VC) Data Model is a formal specification, published as a W3C Recommendation, that provides a standardized format for expressing credentials—such as digital driver's licenses, educational diplomas, or professional certifications—in a way that is cryptographically secure, privacy-respecting, and machine-verifiable. It defines the core data model using JSON-LD, which enables credentials to be understood across different systems and jurisdictions. The model specifies essential components like the issuer, holder, credentialSubject, proof, and expirationDate, creating a common language for trust on the internet.

A primary innovation of the data model is its separation of concerns between the credential's data and its proof. The credential data contains the claims (e.g., "Alice has a Master's degree"), while the proof—typically a digital signature or a zero-knowledge proof—provides the cryptographic verification of those claims' integrity and origin. This allows credentials to be shared and verified without requiring a direct call to the original issuer for every transaction, enabling portable identity and user-centric data control. The model is designed to be extensible and interoperable, supporting various cryptographic suites and signature types.

The standard underpins a wide range of decentralized identity (DID) and self-sovereign identity (SSI) ecosystems. By providing a universal data format, it allows credentials issued by one organization (a university) to be reliably verified by another (an employer), even if they use different vendor systems. This interoperability is crucial for scaling digital trust. The model is also presentation-agile, meaning holders can create selective disclosures—verifiable presentations—to share only necessary information, enhancing privacy through data minimization.

In practice, implementing the W3C VC Data Model involves creating JSON-LD documents that conform to the specification and securing them with Linked Data Proofs. These proofs bind the credential data to a Decentralized Identifier (DID) for the issuer, ensuring non-repudiation. The model does not mandate a specific blockchain or ledger; instead, it is blockchain-agnostic, allowing DIDs to be resolved on various verifiable data registries. This flexibility has made it the cornerstone for projects in digital identity, supply chain provenance, and compliant decentralized finance (DeFi) known-your-customer (KYC) processes.

Key related concepts include the W3C Decentralized Identifiers (DIDs) specification, which provides the mechanism for issuer and holder identification, and Verifiable Presentations, which are the packaged data formats used for sharing credentials with verifiers. The VC Data Model, together with DIDs, forms the technical bedrock of the Trust over IP (ToIP) stack and is integral to emerging regulatory frameworks like the European Digital Identity Wallet (EUDIW). Its role is to provide the essential, vendor-neutral interoperability layer for the next generation of digital trust infrastructure.

etymology
THE FOUNDATION

Origin and Standardization

The W3C Verifiable Credentials Data Model (VC-DM) is the international technical standard that defines the architecture, data model, and formats for creating, issuing, and verifying cryptographically secure digital credentials.

The W3C Verifiable Credentials Data Model (VC-DM) is a formal World Wide Web Consortium (W3C) Recommendation, establishing it as the definitive international standard for digital attestations. Its development was driven by the need for an interoperable, privacy-preserving, and cryptographically secure method to express credentials on the web, analogous to physical credentials like driver's licenses and diplomas. The standardization process, involving extensive collaboration from industry, academia, and the open-source community, ensures that verifiable credentials work consistently across different systems, vendors, and jurisdictions, preventing vendor lock-in and fostering a decentralized ecosystem.

The core specification defines the essential data model and terminology, including the roles of issuer, holder, and verifier, and the components of a verifiable credential and its companion verifiable presentation. It is intentionally format-agnostic, meaning it does not mandate a specific cryptographic proof or serialization format. This separation allows the data model to be implemented using various cryptographic suites (like JSON Web Tokens (JWT) or Data Integrity Proofs with Linked Data Signatures) and encoding schemes (like JSON-LD), providing flexibility while maintaining semantic interoperability. The standard's foundation in Linked Data principles ensures credentials are machine-readable and can be understood in context.

The path to standardization began with the creation of the W3C Verifiable Credentials Working Group in 2017, which published the first official Recommendation (VC-DM 1.0) in November 2019. A subsequent Working Group later published an updated VC-DM 1.1 Recommendation in March 2022, which introduced clarifications, better internationalization support, and more precise definitions. This iterative, consensus-based process under the W3C's rigorous patent policy guarantees the standard is royalty-free and developed in the open, making it the trusted bedrock for countless projects in decentralized identity (DID), Self-Sovereign Identity (SSI), and enterprise attestation systems worldwide.

key-features
W3C VC DATA MODEL

Key Features of the Data Model

The W3C Verifiable Credentials Data Model defines the core structure for creating, transmitting, and verifying digital credentials that are cryptographically secure, privacy-respecting, and interoperable.

01

Core Data Model Structure

The model is built around three primary entities: the Issuer, the Holder, and the Verifier. A Verifiable Credential is a set of tamper-evident claims made by an Issuer. A Verifiable Presentation is how a Holder presents one or more credentials to a Verifier. This structure separates the roles of credential creation, storage, and consumption.

02

Cryptographic Proofs & Integrity

Credentials are secured using digital signatures or zero-knowledge proofs. The proof is linked to the credential data, making it tamper-evident. This allows any Verifier to cryptographically confirm that the credential was issued by the stated Issuer and has not been altered since issuance, without needing to contact the Issuer directly.

03

Selective Disclosure & Privacy

A key privacy feature is the ability for a Holder to perform selective disclosure. This allows them to prove specific claims from a credential (e.g., "I am over 21") without revealing the entire credential document (e.g., their exact birth date or other attributes). This is often implemented using BBS+ signatures or zero-knowledge proofs.

04

Decentralized Identifiers (DIDs)

The model uses Decentralized Identifiers (DIDs) as the primary method for identifying Issuers, Holders, and Verifiers. A DID is a URI that points to a DID Document containing public keys and service endpoints. This enables verification without reliance on a central registry, aligning with the principles of self-sovereign identity (SSI).

05

JSON-LD & Semantic Interoperability

The standard uses JSON-LD (JavaScript Object Notation for Linked Data) as a primary serialization format. JSON-LD adds context to JSON data, linking it to globally understood vocabularies. This ensures credentials from different issuers can be understood and processed uniformly by verifiers, enabling true semantic interoperability across ecosystems.

06

Credential Status & Revocation

The model defines mechanisms to check if a credential is still valid. Common methods include:

  • Status List 2021: A privacy-preserving bitstring where each bit represents a credential's status.
  • Revocation Registries: Used in implementations like Indy-AnonCreds.
  • Direct query to the Issuer's status endpoint. This allows Issuers to revoke credentials without compromising holder privacy.
how-it-works
DATA MODEL

How the W3C Verifiable Credentials Data Model Works

An explanation of the core structure and components that enable the issuance, holding, and verification of digital credentials on the web.

The W3C Verifiable Credentials (VC) Data Model is a standardized framework that defines the data structures and formats for creating cryptographically secure, machine-verifiable digital credentials on the web. It provides a common language for expressing claims—such as a university degree, a driver's license, or a proof of age—in a way that is tamper-evident, privacy-respecting, and interoperable across different systems. The model itself is credential-agnostic, meaning it does not specify the underlying cryptographic proofs or transport protocols, allowing for flexibility in implementation while ensuring semantic consistency.

At its core, the model is built around three primary entities: the Issuer, the Holder, and the Verifier. An Issuer (e.g., a university) creates a Verifiable Credential, which is a set of one or more claims packaged with metadata. The Holder (e.g., a graduate) receives and stores this credential, typically in a digital wallet. When needed, the Holder can present a Verifiable Presentation—a wrapper for one or more credentials—to a Verifier (e.g., an employer) who can cryptographically verify its authenticity and integrity without needing to contact the original Issuer.

The data model specifies key JSON-LD properties for structuring these documents. A credentialSubject contains the actual claims about the Holder. issuer and issuanceDate provide provenance. Crucially, a proof property (or a verifiableCredential array in a Presentation) contains the digital signature or cryptographic proof that binds all the data together. This proof is what makes the credential verifiable, allowing any party to check that it was issued by the stated entity and has not been altered since issuance.

A critical design principle is selective disclosure, enabled through mechanisms like Zero-Knowledge Proofs (ZKPs) or BBS+ signatures. This allows a Holder to prove a specific claim from a credential (e.g., "I am over 21") without revealing the entire credential document (which might contain their exact birthdate, name, or other irrelevant data). This minimizes data exposure and enhances user privacy, moving beyond the all-or-nothing sharing model of physical or simple digital documents.

The model's reliance on Decentralized Identifiers (DIDs) for subject and issuer identification is a key feature. By using DIDs—URIs that point to a DID document containing public keys—the system avoids centralized registries. This allows entities to prove control of their identifier cryptographically, enabling trustless verification. The combination of the VC Data Model, DIDs, and a chosen cryptographic suite forms the complete architecture for a decentralized identity ecosystem, often referred to as Self-Sovereign Identity (SSI).

core-components
W3C VC DATA MODEL

Core Data Structures and Components

The foundational specification for creating, transmitting, and verifying digital credentials in a machine-readable, privacy-preserving, and interoperable format.

The W3C Verifiable Credentials (VC) Data Model is a standardized data format for expressing cryptographically secure, privacy-respecting digital credentials on the web. It defines the core data structures—Verifiable Credentials and Verifiable Presentations—and the rules for their issuance, storage, and verification. This model is credential-agnostic, meaning it can represent any type of claim, from a government-issued driver's license to a university degree or a professional certification, enabling a universal ecosystem of trust.

At its heart, the model uses JSON-LD (Linked Data) or plain JSON to structure credential data, ensuring semantic interoperability. A Verifiable Credential contains several key components: the issuer (who creates it), the credentialSubject (who it's about), the credentialSchema (defining the data structure), and cryptographic proofs like digital signatures or zero-knowledge proofs. These proofs, attached via a proof object, allow any verifier to cryptographically confirm the credential's authenticity and integrity without contacting the original issuer.

A critical innovation is the separation of the credential from its presentation. A holder can create a Verifiable Presentation to selectively disclose information from one or more credentials to a verifier. This enables powerful privacy techniques, such as presenting only a proof of being over 21 without revealing one's exact birthdate. The model also supports Decentralized Identifiers (DIDs) for issuer and holder identification, allowing credentials to function independently of centralized registries or walled gardens.

The specification is designed for extensibility, supporting advanced features like status mechanisms (e.g., checking revocation), refresh services, and evidence fields to document how a claim was established. By providing this common framework, the W3C VC Data Model is the essential technical bedrock for Self-Sovereign Identity (SSI), decentralized trust networks, and verifiable data ecosystems across blockchain and traditional web platforms.

examples
W3C VC DATA MODEL

Examples and Use Cases

The W3C Verifiable Credentials Data Model provides the foundational structure for creating, transmitting, and verifying digital credentials. These examples illustrate its practical implementation across various domains.

ecosystem-usage
W3C VC DATA MODEL

Ecosystem Implementation

The W3C Verifiable Credentials Data Model provides the foundational architecture for creating, transmitting, and verifying digital credentials. This section details the key components and real-world systems that implement this standard.

01

Core Data Structures

The model defines the essential JSON-LD objects for credentials. A Verifiable Credential contains claims (the data), a credentialSubject, an issuer, and a proof. A Verifiable Presentation is a wrapper that packages one or more VCs, often for presentation to a verifier. These structures ensure data integrity and semantic interoperability across different systems.

02

Proof Formats & Cryptography

Credentials are made verifiable through attached cryptographic proofs. Common formats include:

  • JWT (JSON Web Token): A compact, URL-safe proof format using JSON-based claims.
  • JSON-LD with Linked Data Proofs: Enables selective disclosure and advanced features using BBS+ signatures.
  • Ethereum EIP-712: A standard for structuring typed data for signing on Ethereum. The choice of proof format determines the cryptographic suite (e.g., Ed25519, ES256K) and capabilities like zero-knowledge proofs.
03

Decentralized Identifiers (DIDs)

The VC model uses Decentralized Identifiers (DIDs) as the primary identifier for entities (issuers, holders, verifiers). A DID is a URI pointing to a DID Document containing public keys and service endpoints. This decouples identity from centralized registries. Common DID methods include did:ethr: (Ethereum), did:key: (simple key), and did:web: (web domains).

04

Credential Status & Revocation

Mechanisms to check if a credential is still valid. Key methods are:

  • Status List 2021: A privacy-preserving bitstring method where a credential's status is a bit in a publicly available list.
  • Revocation List 2020: An earlier JSON-based list of revoked credential IDs.
  • On-Chain Registries: Using a smart contract (e.g., Ethereum) as a status registry. These systems allow issuers to revoke credentials without contacting the holder directly.
05

Implementation: SSI Wallets & Agents

User-controlled software for managing VCs and DIDs. Digital Wallets (e.g., Trinsic, Spruce ID, Lissi) store private keys, hold credentials, and create verifiable presentations. Agents (like those built on Aries frameworks) enable automated, interoperable credential exchange between issuers, holders, and verifiers over protocols like DIDComm.

06

Real-World Ecosystem Examples

The VC model is deployed in major ecosystems:

  • EU Digital Identity Wallet (EUDIW): The pan-European framework for citizen credentials.
  • OpenID for Verifiable Credentials (OIDC4VC): Bridges VC issuance/presentation with OAuth 2.0.
  • CHAPI (Credential Handler API): A browser API for credential exchange.
  • DIF's Presentation Exchange: A specification for defining presentation requests and submissions between parties.
COMPARISON MATRIX

VC Data Model vs. Related Standards

A technical comparison of the W3C Verifiable Credentials Data Model with related identity and attestation standards.

Feature / StandardW3C VC Data ModelX.509 CertificatesOpenID Connect (OIDC)

Primary Purpose

Machine-readable, portable attestations

Machine-to-machine authentication (TLS/SSL)

User authentication and identity federation

Data Model

JSON-LD (Linked Data)

ASN.1 (Binary/DER)

JSON (OAuth 2.0 tokens)

Cryptographic Proof

âś… (LD-Proofs, JWT)

âś… (Digital signatures)

âś… (JWT signatures)

Decentralized Identifiers (DIDs)

âś… (Native support)

❌ (Not applicable)

❌ (Not applicable)

Selective Disclosure

âś… (Zero-Knowledge Proofs, BBS+)

❌ (Full certificate presented)

❌ (Full token presented)

Revocation Mechanism

Status List, Bitstring, On-chain registry

Certificate Revocation List (CRL), OCSP

Token introspection, Back-channel logout

Schema Definition

âś… (JSON Schema, custom contexts)

âś… (X.509 v3 extensions)

âś… (OIDC claims, scopes)

Portability & Holder Control

âś… (User-held, wallet-based)

❌ (Issuer/CA-controlled)

❌ (Reliant on Identity Provider)

security-considerations
W3C VERIFIABLE CREDENTIALS DATA MODEL

Security and Privacy Considerations

The W3C VC Data Model provides a foundational framework for creating, transmitting, and verifying digital credentials. Its design incorporates several core principles to ensure the security of the credential lifecycle and protect the privacy of the credential holder.

01

Selective Disclosure

A core privacy-enhancing feature that allows a holder to reveal only specific claims from a credential, rather than the entire document. This minimizes data exposure. For example, a holder can prove they are over 21 from a driver's license credential without revealing their exact birthdate, name, or address. This is often implemented using cryptographic techniques like BBS+ signatures or zero-knowledge proofs (ZKPs).

02

Holder Binding & Non-Transferability

Ensures a credential is cryptographically bound to its rightful owner and cannot be used by anyone else. This is achieved by linking the credential to a Decentralized Identifier (DID) or a public key controlled solely by the holder. The verification process requires the holder to prove control of the corresponding private key (e.g., via a digital signature), preventing credential theft and unauthorized sharing.

03

Data Minimization & Unlinkability

Guiding principles to limit data collection and prevent correlation across different interactions. Data minimization is enforced by selective disclosure. Unlinkability ensures that multiple presentations of credentials from the same holder cannot be linked together by a verifier, protecting against profiling. Techniques like using unique presentation tokens or ZKPs for each interaction are critical here.

04

Credential Status & Revocation

Mechanisms to invalidate credentials before their expiration date, which is crucial for security. Common methods include:

  • Status Lists (e.g., StatusList2021): A cryptographically signed list of revocation statuses.
  • Revocation Registries: Used in Indy-based systems, where a ledger holds revocation accumulators. The choice impacts privacy; some methods can reveal to the verifier which specific credential was checked.
05

Issuer Authentication & Trust

The integrity and authenticity of a VC depend entirely on trust in the issuer. Verifiers must authenticate the issuer's DID and verify the cryptographic signature on the credential. Trust is established through trust registries, verifiable issuer credentials, or recognized public key infrastructure (PKI). A compromised issuer key invalidates all credentials it signed.

06

Secure Storage & Key Management

The security of the credential lifecycle hinges on the holder's ability to securely store credentials and manage their private keys. This is the responsibility of a digital wallet. Best practices include:

  • Using hardware security modules (HSMs) or secure enclaves.
  • Implementing robust key recovery mechanisms without creating backdoors.
  • Protecting against phishing and malware that could steal signing keys.
W3C VERIFIABLE CREDENTIALS

Common Misconceptions

Clarifying frequent misunderstandings about the W3C Verifiable Credentials Data Model, a foundational standard for digital trust.

No, a W3C Verifiable Credential (VC) is a data model standard, not a specific implementation technology. The VC Data Model defines the structure for creating cryptographically secure, machine-verifiable digital credentials, specifying formats for the credential metadata, claims, and proofs. While a decentralized identifier (DID) and its associated cryptographic keys are often used to sign VCs for trust, the standard itself is blockchain-agnostic. VCs can be issued and verified using various cryptographic suites and trust registries, including but not limited to blockchain-based systems. The core innovation is the portable, vendor-neutral data format, not the underlying ledger technology.

W3C VERIFIABLE CREDENTIALS

Technical Deep Dive

Explore the foundational data model and core technical components that define digital credentials on the web, enabling secure and interoperable proof of identity, qualifications, and attributes.

The W3C Verifiable Credentials (VC) Data Model is a standardized format for expressing cryptographically secure, privacy-respecting digital credentials on the web. It defines the core data structures—Credentials, Presentations, and the roles of Issuer, Holder, and Verifier—that enable trusted information exchange. The model is protocol-agnostic, meaning it can be implemented using various cryptographic suites (like JSON Web Tokens or Linked Data Proofs) and transport mechanisms. Its primary goal is to create a common language for digital credentials, ensuring interoperability across different systems and platforms while giving individuals control over their data through Selective Disclosure.

W3C VC DATA MODEL

Frequently Asked Questions

The W3C Verifiable Credentials Data Model is the foundational standard for creating, issuing, and verifying digital credentials on the web. These FAQs address common developer and architect questions about its structure, implementation, and role in decentralized identity.

The W3C Verifiable Credentials (VC) Data Model is a standardized framework for expressing credentials—like digital driver's licenses or university degrees—in a way that is cryptographically secure, privacy-respecting, and machine-verifiable. It defines the core data structures, including the Verifiable Credential itself and the Verifiable Presentation, which are independent of any specific cryptographic proof format or blockchain. The model enables interoperability by specifying how to encode claims (the actual data), metadata (issuer, issuance date), and proofs (digital signatures, zero-knowledge proofs) in a consistent JSON-LD or plain JSON format. This allows credentials issued by one organization to be reliably verified by another, forming the backbone of Self-Sovereign Identity (SSI) ecosystems.

ENQUIRY

Get In Touch
today.

Our experts will offer a free quote and a 30min call to discuss your project.

NDA Protected
24h Response
Directly to Engineering Team
10+
Protocols Shipped
$20M+
TVL Overall
NDA Protected Directly to Engineering Team
W3C VC Data Model: The Standard for Verifiable Credentials | ChainScore Glossary