Presenting Academic & Employment Credentials

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

Three things at once: prove "held" without sending the original; let employers/schools verify independently; make it forgery- and tamper-proof.

PDFs/paper can be forged and altered, exposing the individual's contents each submission. Only a ZK proof does all three. Only work requiring all three at once is Lemma's territory.

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 / BBS+ 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.

All figures are directional.

The issuing side (universities, certification bodies) Issue forgery-proof, privacy-preserving credentials and cut query-handling load; strengthens brand and trust. e.g. issuance/queries shift from handling individual inquiries to verifiable issuance.

The verifying side (corporate HR, schools) Instantly verify "legitimately held" without seeing the contents; less original collection and authenticity checking. e.g. credential checks shift from collecting/eyeballing to verifying one proof.

The individual (student, job seeker) Carry it and present only what's needed; no full transcript or exam history exposed.

A company verifying qualifications/education in mid-career hiring collects certificate PDFs from applicants. Among them slip doctored PDFs and reuse from other purposes; authenticity checks are laborious, and per-issuer inquiries add burden.

Had Lemma been in place, the applicant presents a proof of "holds a legitimate degree/qualification" without sending the original. HR verifies authenticity without seeing the contents, with no need to query the issuer each time.

We don't replace your certificate-issuance or student-records system. We insert one proof step into the issuance and presentation paths.

• Issuer-signed credentials: universities/certification bodies issue records with issuer signatures (W3C VC 2.0 aligned).
• Selective disclosure: BBS+ over BLS12-381 — minimal disclosure of "legitimately held."
• Authenticity & provenance: fix with docHash and issuer signature; verify via Groth16 (Circom).

The original stays with the individual/issuer; only the cryptographic fact "legitimately held" travels.

• Proof that a person "holds a legitimate academic record, qualification, or enrollment"
• Authenticity via the original's docHash and issuer signature
• Interoperability aligned with standards (W3C VC 2.0 / BBS+)
• A trail that employers, schools, and third parties verify independently — without disclosing the contents

Not a standalone SaaS purchase. We enter through AI-adoption / data-governance consulting and a PoC, landing on an existing monthly plan.

1. A 30-minute review — identify credentials where forgery / query load concentrates.
2. Narrow to 1–2 decisions (results) to prove — e.g. "holds a legitimate degree," "passed the qualification." Not the full transcript.
3. Design issuance and standards alignment — issuance paths, alignment with W3C VC 2.0 / BBS+ / OP, and revocation handling.
4. Prove one path via a (quote-based) PoC.
5. Land on an existing monthly plan (indicative) — Lemma Civic / Compliance; pricing confirmed in conversation.

Tell us the one credential with the heaviest issuance/verification load, in the first 30 minutes. No disclosure of sensitive data required.