Not everything on this site is settled. The VC guide v1.1 (EUNIS SIG, July 2026), Verifiable Credentials in Higher Education: W3C-VC and SD-JWT VC, and the Badges guide v1.1 (EUNIS SIG, July 2026), Badges and Digital Credentials in Higher Education, both from the EUNIS Special Interest Group – Mobility & Digital Credentials (EUNIS SIG), name several issues that remain open. Here they are, each with why it matters to institutions and what to watch. The table maps each problem to the stack it affects. Problems 1 to 7 follow the guides; 8 to 10 are this site’s additions: 8 and 9 reframe as open questions two SD-JWT traits documented elsewhere on this site as design characteristics, and 10 follows a regulatory change of July 2026.
| # | Open problem | Stack | Nature |
|---|---|---|---|
| 1 | Device-bound holder keys over a 30-year credential | Both | Wallet design |
| 2 | Long-lived credentials in short-lived issuance flows | Both | EUDI ecosystem design |
| 3 | Rendering: per-instance or type-bound display | Both | Spec maturity |
| 4 | Wallet support for bbs-2023 | W3C-VC | Deployment |
| 5 | Open Badges v3.0 and EDC | W3C-VC | Missing interop profile |
| 6 | VCDM 1.1 legacy | W3C-VC | Migration |
| 7 | Specifications still in draft | Both | Spec status |
| 8 | Unlinkability via batch issuance | SD-JWT | Profile decision, deployment |
| 9 | Suspension in Token Status List profiles | SD-JWT | Profile decision |
| 10 | W3C VCDM profiles for the EUDI Wallet | W3C-VC | Regulation, spec status |
1. Device-bound holder keys over a 30-year credential [Both stacks]
The problem: holder binding ties a credential to wallet keys that usually live on one device, and in the worked example Aina will change phones many times over her career; both stacks are affected. Why it matters: a degree that cannot survive a phone upgrade becomes a support burden for the registry. Watch: the options under discussion, covered in Credential lifecycle.
2. Long-lived credentials in short-lived issuance flows [Both stacks]
The problem: EUDI issuance flows are built around short-lived attestations refreshed through OAuth-style tokens that live hours to weeks. A degree outlives every token that issued or refreshed it; over decades, refresh automates the paperwork of re-issuance rather than removing it. Why it matters: renewal routes, and who keeps them working, become a lifetime commitment. Watch: how your national wallet plans to handle long-lived credentials; ask in writing. See Credential lifecycle.
3. Rendering: per-instance or type-bound display [Both stacks]
The problem: W3C’s renderMethod attaches display instructions to the individual credential, inside the signed object, but its specification is an early, experimental draft with little wallet support. SD-JWT VC binds display to the type through Type Metadata, so each institution wanting its own look defines a new type. Why it matters: a diploma is also a visual object, and institution-faithful documents depend on rendering. Watch: renderMethod’s progress and wallet uptake; a dimension to follow rather than decide on today.
4. Wallet support for bbs-2023 [W3C-VC]
The problem: bbs-2023 delivers unlinkability cryptographically, but wallet support is still maturing. Why it matters: the property eIDAS 2.0 names is hardest to deploy today. Watch: wallet roadmaps; meanwhile the W3C data model can travel under an SD-JWT envelope (VC-JOSE-COSE) and move to bbs-2023 later, although that envelope is not the SD-JWT VC format named in the EUDI Wallet implementing acts, and whether national wallets will accept it is not settled by the current acts (see problem 10).
5. Open Badges v3.0 and EDC [W3C-VC]
The problem: both build on the W3C data model, yet no established interoperability profile between Open Badges v3.0 and European Digital Credentials exists in production. Why it matters: institutions combining badges and formal credentials must bridge them themselves. Watch: harmonisation work and emerging practice, where university networks can contribute.
6. VCDM 1.1 legacy [W3C-VC]
The generic EDC SHACL profile still references the VCDM 1.1 context while EBSI JSON Schemas follow VCDM 2.0, which complicates validation. Migration is additive and new deployments should target 2.0; see The W3C-VC stack.
7. Specifications still in draft [Both stacks]
The problem: several specifications are not final. On the SD-JWT side, SD-JWT is RFC 9901 but SD-JWT VC is still an Internet-Draft (post-Last Call, with open security-review issues) and Token Status List is IESG-approved but awaiting the RFC Editor, with no RFC number yet (status as of October 2026). On the W3C-VC side, the BBS signature scheme behind bbs-2023 is still an IRTF/IETF Internet-Draft and renderMethod is an experimental W3C draft. Why it matters: details can change under deployed credentials. Watch: final publication, and which versions your wallet and verifiers implement.
8. Unlinkability via batch issuance [SD-JWT]
The problem: an SD-JWT presentation carries the issuer’s signature and the salted-hash digests unchanged every time, so even with attributes withheld those values act as a persistent identifier that verifiers comparing notes can correlate. The mitigation is batch issuance: the wallet holds many single-use copies, each freshly signed and salted, and presents each one once. That is a deployment practice, not a property of the format: it needs issuer support, a wallet that manages the pool and a refresh before the pool runs out, and it offers nothing when the presentation must identify the holder anyway. Why it matters: eIDAS 2.0 Article 5a(16) makes unlinkability a requirement of the wallet framework, and for a thirty-year degree a finite pool of single-use copies brings back the re-issuance dependency of problem 2. Watch: whether the European profiles mandate batch issuance and at what pool size, and whether education-sector issuers support it. See Selective disclosure vs unlinkability.
9. Suspension in Token Status List profiles [SD-JWT]
The problem: the Token Status List specification defines a suspended value alongside valid and invalid, but the European profiles adopted for SD-JWT deployments use revocation only: a credential is valid or it is not. A disciplinary hold or an administrative correction, temporary by nature, has no status to express it; the credential either stays valid while under review or is revoked and re-issued when the hold is lifted. Why it matters: universities put credentials on hold far more often than they withdraw them. Without a suspended state, “on hold” collapses into a false invalid or an unrecorded valid, and the registry carries the gap in procedure rather than in the credential. Watch: whether the European profiles adopt the suspended value once Token Status List is published as an RFC; until then, institutions issuing on SD-JWT need a written procedure for holds. See Credential lifecycle.
10. W3C VCDM profiles for the EUDI Wallet [W3C-VC]
The problem: since Implementing Regulation (EU) 2026/1731 (in force 11 August 2026), the binding annexes of the EUDI Wallet implementing acts name SD-JWT VC and ISO/IEC mdoc for person identification data and for attestations (ETSI TS 119 472-1 profiles). W3C VCDM is not among them today, but the regulation’s recitals state that wallets should also support it, as the reference format for attestations in education, once new W3C VCDM profiles are available. ARF v3.0 currently treats W3C VCDM as optional and for non-qualified attestations only. Why it matters: until those profiles exist, a degree or formal microcredential on the W3C-VC stack reaches the wallet only as a non-qualified attestation, and only where the national wallet supports the optional format; the recital sets no date. Watch: ETSI publishing the W3C VCDM profiles, an amendment bringing them into the binding annexes, and an ARF release revisiting the optional status; meanwhile keep an SD-JWT VC route for credentials that must work in national wallets. See EUDI Wallet.
Corrections welcome
This list will age. If something here has been resolved, or an open problem is missing, please get in touch.
