CertiProof
Web3 Academic Credential Platform

Tamper-Evident Certificates, Verified in Seconds

A Web3 academic credential platform: institutions issue tamper-evident certificates anchored on-chain, and anyone can verify authenticity instantly — with an AI layer that cross-checks uploaded documents against the on-chain record.

7–14 days

Traditional manual verification

2–3 days

Third-party proxy verification

~2 seconds

CertiProof on-chain lookup

The Problem

Manual Verification Doesn't Scale

Fake or altered academic certificates are difficult to catch during manual verification.
Centralized verification databases are single points of failure with no public audit trail.
Students have little control over how their credentials are shared and checked.
Employers routinely wait days or weeks on institutions just to confirm one document.
How It Works

Four Steps, Zero Middlemen

Step 1

Institution issues

An authorized issuer wallet computes a canonical hash of the credential's core fields and anchors it on-chain via CertificateRegistry.issueCertificate().

Step 2

Student receives

The certificate is handed to the student with a QR code encoding its verification URL — no app or account needed to use it.

Step 3

Verifier checks

Anyone — an employer, another institution — scans the QR or enters the certificate ID and gets an instant on-chain result.

Step 4

AI cross-checks

Upload the physical document instead: an AI layer extracts its fields and flags any mismatch against the on-chain record.

Three Roles

Built for Everyone in the Loop

Institutions & Issuers

Authorized university or organization wallets issue tamper-evident certificates in seconds, with a full on-chain audit trail of every issuance and revocation.

Students & Holders

Receive a QR-coded certificate you fully control — share it anywhere, and it stays verifiable without ever going back through the institution.

Employers & Verifiers

Confirm authenticity in seconds, for free, without emailing a registrar's office — by hash, QR code, or AI-assisted document upload.

Why On-Chain Hashes, Not Documents

CertiProof never stores certificate contents or personal data on-chain — only a keccak256 hash of the credential's canonical fields. This keeps gas costs low, keeps student data off a public and permanent ledger, and still lets anyone verify authenticity by re-deriving the same hash from a presented document and checking it against the registry.

Originally proposed as a Final Year Project at the University of Malakand — Department of Software Engineering by Engr. Muhammad Ansar and Danyal Afzal — this repository is the working engineering implementation of that proposal, extended with an AI document-verification layer.