SD-JWT vs JSON-LD credentials: When to use which?

There's been a lot of discussion about SD-JWT vs JSON-LD credentials. Here's my breakdown of when to use each. ## SD-JWT (Selective Disclosure JWT) **Best for:** - Mobile-first applications - Performance-critical verification - Simple attribute disclosure - Compact credential size **Pros:** - Smaller payload size - Faster verification (no JSON-LD processing) - Native selective disclosure - Works well offline **Cons:** - Less semantic richness - Disclosure is per-claim, not arbitrary expressions ## JSON-LD Credentials **Best for:** - Complex semantic relationships - Interoperability with RDF systems - Academic/research credentials - Credentials requiring linked data **Pros:** - Rich semantic context - ZKP-based selective disclosure possible - Better for complex credential graphs **Cons:** - Larger payload - More complex verification - Requires JSON-LD processing ## My Recommendation For most production use cases (KYC, age verification, identity proofing), **SD-JWT is the pragmatic choice**. It's what the EUDI Wallet uses and what most wallets support well. Use JSON-LD when you have specific semantic interoperability requirements or need BBS+ signatures for advanced ZKP selective disclosure. What's everyone else using?