Open Standards Demo

Verifiable Credentials

W3C VC Data Model 2.0 + Open Badges 3.0 — eddsa-jcs-2022 Cryptographic Signing
W3C VC 2.0 Open Badges 3.0 eddsa-jcs-2022
NO LICENCE FEE
open standard
Institution Issuer

Issued Credential JSON
Issue a credential to see the signed W3C VC here
Learner Wallet 0 credentials
No credentials yet. Issue one from the Issuer tab.
Credential Detail
Select a credential to inspect it
Employer / Agency Verifier
Quick Load

Select a credential from the wallet to load it into the verifier:

No credentials yet

Credential Flow

InstitutionIssues + Signs
GraduateHolds + Shares
Employer / AgencyVerifies
Cryptographic signature means verification requires no contact with the issuer

W3C Verifiable Credentials 2.0

Published May 2025 as a W3C Recommendation. Defines the data model for cryptographically verifiable claims. Free to implement by anyone, anywhere. Ratified by the global standards body — not self-certified.

Open Badges 3.0

Developed by 1EdTech. Built on top of W3C VCs. The global standard for digital achievement badges and credentials. Cryptographically signed so badges survive platform changes — including ransomware attacks.

eddsa-jcs-2022

The ratified W3C VC 2.0 cryptosuite. Uses Ed25519 public-key cryptography with JSON Canonicalization Scheme (JCS). The institution signs with a private key; anyone verifies with the public key. A tampered credential produces an invalid signature — immediately detectable.

What this demo proves

This demo runs entirely on open, freely implementable standards. No proprietary licence. No annual fee. No single company controlling the standard.

A credential issued here can be verified by any system that implements W3C VC 2.0 — which includes implementations across the EU (Europass), Singapore (MySkillsFuture), MIT (Digital Credentials Consortium), and 1EdTech members worldwide.

Crucially: because the signature is cryptographic, verification does not require contacting the issuing institution. The institution's server could go offline — or be ransomed — and credentials issued before the incident remain fully verifiable.

This is the architecture Australia could adopt for a National Skills Passport without building or licensing proprietary infrastructure.

Registered Issuers (this demo)
Checking browser support for W3C Digital Credentials API…
Employer Portal OID4VP + W3C VC 2.0
1
Generate Credential Request

The employer portal issues an OID4VP presentation request with a fresh nonce. In a live deployment, this is what navigator.credentials.get() sends to the candidate's wallet.


2
Present Credential from Wallet
or select from demo wallet
Issue a credential first, then select it here to simulate a wallet response.
Verification Result
Generate a request and present a credential to see the result.
Verifier Ecosystem — May 2026
Scenario Status
Browser portal via Digital Credentials API
Chrome 141+, iOS Safari / iOS 26
● LIVE
EU employer via EUDI Wallet
Member state rollouts 2026
● LIVE / IMMINENT
Singapore MySkillsFuture ● LIVE
OID4VP self-certification
Launched Feb 2026, 11 interop events
● PRODUCTION READY
Workday native W3C VC ◐ ROADMAP CONFIRMED
SAP SuccessFactors native W3C VC ◑ MIDDLEWARE AVAILABLE
Australian employer (no existing HR system) ● STRAIGHTFORWARD
Background checking (HireRight, Sterling) ◐ INTEGRATIONS BUILDING