Verifiable Credentials & Identity Wallets (W3C VC 2.0)

Cryptographically verifiable claims issued by trusted parties and presented via identity wallets, enabling selective disclosure and offline verification.

Overview

Verifiable Credentials (VCs) allow entities to issue cryptographically signed credentials that holders store and present through identity wallets. Verifiers check proofs without calling the issuer, enabling privacy-preserving flows and offline checks.

How it works

  1. Issuance: Issuer signs a credential to the holder’s wallet.
  2. Presentation: Holder creates a verifiable presentation with selective attributes.
  3. Verification: Verifier validates signature, status/revocation, and schema against trusted keys/registries.

Common use cases

  • Digital diplomas & licenses
  • Age or attribute checks
  • Travel & cross-border credentials

Strengths and limitations

Strengths: Privacy via selective disclosure; offline verification; open standards.
Limitations: Interop profiles; governance/trust frameworks; revocation/status infrastructure.

Key terms

  • Verifiable presentation: A bundle proving certain claims to a verifier.
  • Issuer/Holder/Verifier: Roles in VC ecosystems.

References

Latest Data Cards

  • Data Card

    DCSA ‘Identity Exchange’ Targets Verified Business Digital Identity in Container Shipping

    2025-11-17CC-BY-4.0verifiable-credentialsdigital-id

    The Digital Container Shipping Association introduced an ‘Identity Exchange’ to share verified business identity data across the shipping ecosystem, aiming to streamline trust and reduce fraud.

    • Sector initiative for verified business identity
    • Supports cross‑party interoperability in shipping
    • Maps to reusable credential patterns
  • Data Card

    HUB Cyber Security Introduces HUB Token for SSI on Trvsthub

    2025-11-07CC-BY-4.0verifiable-credentialsdigital-id

    HUB Cyber Security unveiled the HUB Token, a software credential designed for self‑sovereign identity workflows on Trvsthub, enabling selective disclosure and standards‑based verifiable credentials.

    • Targets SSI/VC use cases with selective disclosure
    • Positions Trvsthub as an issuance and verification hub
    • Aims to streamline cross‑border compliance and onboarding
  • Data Card

    Hopae Connect Becomes EU‑Registered eIDAS 2.0 Intermediary

    2025-09-03CC-BY-4.0verifiable-credentialsmobile-id

    Hopae Connect launched as one of the first private‑sector intermediaries registered under eIDAS 2.0 to support routing and interoperability for EUDI Wallet deployments.

    • Registered intermediary to bridge issuers, wallets, verifiers
    • Supports EUDI Wallet rollout across EU markets
    • Positions private sector roles in the eIDAS 2.0 ecosystem

Frequently Asked Questions

What is a Verifiable Credential (VC)?
A tamper-evident set of claims with metadata proving who issued it; holders store VCs in wallets and present verifiable proofs to verifiers.
How does selective disclosure work?
Cryptographic proofs reveal only needed attributes (e.g., ‘over 18’) rather than the full credential.
How do VCs relate to government IDs?
They can complement physical documents; issuers (e.g., agencies, universities) issue VCs that can be verified online or offline.
What about revocation/status?
Verifiers check credential status lists or cryptographic status proofs to ensure a VC hasn’t been revoked without contacting the issuer.