Imagine a university gives a student a digital diploma. When she applies for a job, she presents it and the employer checks where it came from, rather than relying on a logo or a scanned signature. That check can detect changes to the document. Even so, a question remains: does the employer trust what the university is attesting to?
Verifiable credentials are sets of claims made by an issuer and protected by mechanisms that allow their authenticity and integrity to be checked technically. They can state, for example, that a person earned a degree. The W3C data model sets out how to represent those claims and the relationships among those who issue, present, and verify them.
“Verifiable” describes the possibility of checking a claim. It does not make the claim true or guarantee that every institution must accept it.
From diploma to presentation
Take the hypothetical example further. The university issues a credential stating that the student earned a particular degree. She keeps it and, when an employer asks for proof of her education, shares the information needed for the employer to assess it.
Four roles appear in this process:
- Issuer: issues the credential; in this example, the university.
- Holder: keeps the credential and can present it; here, the student.
- Subject: the person, entity, or thing about which a claim is made; here, also the student.
- Verifier: checks the credential or presentation and decides whether to accept it; in this case, the employer.
The holder and subject need not be the same. A person could keep and present a credential about another entity. The distinction matters because possessing a credential does not establish that all its claims refer to the person presenting it. The W3C model explicitly distinguishes these roles.
This technology belongs to the broader field of digital identity, although a credential can attest to a specific attribute without purporting to describe someone's entire identity.
Credential, presentation, and wallet: three different pieces
The credential contains the issuer's claims and is protected by a verifiable mechanism. A presentation brings together information from one or more credentials to share with a verifier. Depending on the mechanism used, it can include the credentials themselves or proofs derived from them.
A digital wallet is a tool that lets the holder keep credentials and manage their use. It is neither the diploma nor the institution that issues it. An application calling itself a wallet does not, on its own, establish what protections it offers or which systems it works with.
Verification depends on a technical proof, not the appearance of a file. A scanned signature is an image; a QR code can carry data or direct someone to a webpage. Neither element by itself shows that a credential conforms to the W3C model.
Protection mechanisms include the cryptographic proofs described in Data Integrity. Their checks use appropriate algorithms and verification material to detect alterations and evaluate the proof. The result depends on the mechanism chosen and its correct implementation.
Nor must every credential use a blockchain or a decentralized identifier, known as a DID. An identifier refers to something; a credential expresses claims. These are different functions and should not be confused.
What the employer checks and what remains unresolved
When the employer receives the diploma, it should not treat verification as a single yes-or-no question. Several related checks and decisions are involved:
| Question | What it helps assess |
|---|---|
| Is the proof valid? | Whether it passes the technical checks required by the mechanism used. |
| Does it come from the expected issuer? | Whether the credential can be attributed to the issuer using accepted verification methods. |
| Is it within its validity period? | Whether it meets any stated time limits. |
| Is it suspended or revoked? | Its status according to the mechanism provided, if one is included. |
| Do we accept what this issuer attests to? | A question of trust and organizational policy. |
These questions are not interchangeable. A proof can be technically valid even when the claim it protects is mistaken. In our example, the university might have made an administrative error when issuing the diploma. Cryptography does not review academic records or certify the quality of teaching.
A credential can also be authentic yet insufficient for a particular job in the employer's judgment. According to the W3C model, verifying a credential and deciding whether to trust it are related but distinct operations.
Key idea: Verification helps establish the origin and integrity of a claim. Trusting the party making it still requires judgment.
The security of the presentation deserves separate attention. Some mechanisms allow a one-time challenge to reduce the risk that someone will reuse a captured presentation. That protection requires the system to implement and check it correctly; it does not automatically accompany every document called “verifiable.”
Validity, suspension, and revocation
Expiration and status address different problems. A credential can reach the end of its validity period. It can also be suspended or revoked earlier, for example if the issuer discovers it was issued in error. Knowing that a proof is valid does not settle those other questions.
A verifier does not always need to contact the issuer for every diploma presented. The W3C Bitstring Status List specification describes shared lists that can publish status information for many credentials. Distributing and caching them can reduce the signals left by an individual inquiry for each use.
The design involves a practical tradeoff: information must be sufficiently up to date to be useful for verification. An old copy may not reflect a recent change. At the same time, how lists are obtained and queries are organized affects privacy. Shared lists do not eliminate all communication or all tracking risks.
Sharing less data requires a design that permits it
The student wants to prove her educational qualifications. That does not mean she needs to hand over every other piece of personal information associated with her academic record. The distinction between what is necessary and what is available is central to digital privacy.
Some mechanisms allow selective disclosure: proving certain claims without revealing every field in a credential. The W3C BBS cryptosuites, a specification still under development, illustrate this capability. It should not be attributed to all verifiable credentials.
Moreover, hiding fields does not guarantee anonymity. If a presentation reveals a persistent identifier, a recognizable combination of data, or metadata that allows uses to be linked, it may still facilitate tracking. Privacy depends on what is disclosed, how the proof is constructed, and how participants behave.
Key idea: Revealing less information can reduce exposure. It does not ensure that two presentations cannot be linked.
A useful assessment should ask what data the verifier requests and why, as well as examining the wallet's technology. A tool with strong privacy capabilities offers little choice if access to a service requires sharing unnecessary information.
Who decides whom to trust?
Verifiable credentials can make checks easier, but the technical model does not itself determine who has the power to accept or exclude. Someone still decides which issuers are recognized, which claims are sufficient, and how errors are resolved.
From the standpoint of individual autonomy, it is worth assessing whether those decisions are transparent and can be challenged. In the diploma example, the student needs a way to correct a mistaken claim. If she changes wallets or loses access to her device, she also needs to know what recovery or reissuance options are available. There is no universal recovery procedure to assume.
As an editorial principle, a system should offer assistance and accessible alternatives for people who cannot or do not wish to use a particular wallet. It also matters whether they can change providers and continue using their credentials, and on what terms. These are questions about how a service operates and the rules it applies, not guarantees automatically provided by the standard.
The hypothetical diploma leaves two separate tasks. The employer can check the proof, dates, and status using the applicable mechanisms. It must then decide whether the university and its qualification deserve trust for that job. A verifiable credential makes part of that decision easier to check; the reasons for accepting it should remain clear to the person presenting it.
Share