Presenting Academic & Employment Credentials
Prove you hold a degree, qualification, or employment record — without sending the original. Employers and schools verify without seeing the contents; forgery-proof. Aligned with W3C VC 2.0.
Who this is for.
For those presenting or verifying academic records, qualifications, and enrollment/graduation in hiring, transfer, and reskilling. Exchanging certificate PDFs or originals carries forgery, tampering, and reuse risk — and tends to over-disclose the individual's data.
-
Universities, education and certification bodies that issue records, completions, qualifications
-
Corporate HR and schools verifying credentials in hiring/transfer
-
Organizations wanting to make reskilling / CPD history provable
Hand over the source, or just the facts?
Change what reaches the AI, and the leakage risk goes with it.
- holder_id:
- P-345-67-8901
- name:
- Taro Yamada
- dob:
- 1995-04-12
- qualification:
- Class-1 electrician
- expires:
- 2025-03-14
- license_no:
- ABC123456789
- subject:
- did:lemma:holder-yamada-001
- issuer:
- did:lemma:authority-meti
- sourceHash:
- 0x6b2c…e4a9
- recordedAt:
- 2020-03-15T00:00:00Z
- integrity:
- poseidon-merkle
- ZK verified:
- ✓ VALID
Present only a proof that a person "holds a legitimate academic record, qualification, or enrollment." Full transcripts and exam history are not disclosed. Issued with the issuer's (university, certification body) signature, employers and schools verify without seeing the contents. Selective disclosure aligns with W3C VC 2.0 / and connects to standardization efforts like Originator Profile.
Held portably by the individual, there's no need to query the issuer each time it's presented.
Choose on three criteria.
Only work that needs all three at once — pass without exposing, independent verification, tamper-proof — is Lemma's domain.
| Method | Pass without exposing | Independent verification | Tamper-proof |
|---|---|---|---|
| Access control only | △ | ✗ | ✗ |
| Masking / anonymization | △ | ✗ | ✗ |
| Encryption only | ✓ | ✗ | ✗ |
| Lemma (ZK proof)the only one with all 3 | ✓ | ✓ | ✓ |
What's next
We enter through AI-adoption and data-governance support and a PoC, and stay alongside you through to operations.
- A 30-minute review — identify credentials where forgery / query load concentrates.
- Narrow to 1–2 decisions (results) to prove — e.g. "holds a legitimate degree," "passed the qualification." Not the full transcript.
- Design issuance and standards alignment — issuance paths, alignment with W3C VC 2.0 / BBS+ / OP, and revocation handling.
- Prove one path via a (quote-based) PoC.
- Hands-on support from rollout through operations — existing plan tiers (Civic / Critical / Compliance) serve only as a cost reference; the setup and pricing are designed together.
Tell us the one credential with the heaviest issuance/verification load, in the first 30 minutes. No disclosure of sensitive data required.
The bigger picture
The bigger picture this use case belongs to.
We map use scenarios across industries and workflows by the four axes.
See use scenarios for Verifiable Origin in Solutions →TRY LEMMA
Run it yourself.
No sales call needed — start hands-on with Lemma's products.