Authenticity you can check.
Genuineness you can prove.
Integrity you can trust.
AI can now rewrite a CGPA, forge a signature, or generate a convincing transcript in seconds. VeriBlock makes that irrelevant — every credential is sealed to a SHA-256 hash the moment it's issued, anchored on Polygon, and re-verified byte-for-byte on demand. Change one character, and it's caught instantly.
Universal Credential Verification
Three steps from a document to a fact.
Every credential moves through the same sequence, in this order, before anyone outside the institution can see it.
The institution signs.
A registrar uploads the source document. AI-assisted extraction reads name, roll number, course, specialization, division and CGPA — but nothing goes on-chain until the issuer reviews and confirms it themselves.
The record is sealed.
The document is hashed with SHA-256, pinned to IPFS, and the hash is committed to a smart contract on Polygon. From here, altering even one character breaks the match.
Anyone can check it.
Enter the Verification ID and upload the PDF in hand. VeriBlock re-hashes it in your browser and compares it against IPFS and the chain — no login, no institution involvement.
A hash doesn't care how convincing the edit looks.
An AI-edited PDF can look flawless to the eye — different CGPA, a new date, a swapped name — and still pass a visual check. It cannot pass a hash check. Here's what each result actually tells the verifier.
File Integrity Confirmed
The uploaded PDF matches the original certificate on record, bit-for-bit. No edit, no re-export, no AI touch-up survives this check unnoticed.
File Mismatch — Possible Tampering
The uploaded PDF does not match the sealed hash. This file may have been modified after issuance — by hand or by a model — and should not be trusted as-is.
Credential Revoked
The file matches, but the issuing institution has since revoked it — a graduation reversed, a credential re-issued, an error corrected. The hash was never the whole story; the current on-chain status is.
Built for the people who issue, and the people who ask.
Issue once. Field verification calls, never again.
Registrars issue and revoke credentials from a wallet-gated dashboard. Every institution signs with its own key — nothing is shared.
- MetaMask signing per institution, not a shared admin login
- AI-assisted intake with a confidence score, always human-confirmed
- Low-confidence fields are flagged for manual review before anything is signed
- Structured records: course, specialization, division, CGPA
- Revoke a credential at any time — status updates on-chain
Check a claim without asking anyone's permission.
Students sign in with email and a one-time code — no wallet required — to find their Verification IDs. Employers just need that ID and the PDF in hand.
- Email + OTP dashboard, no crypto wallet needed
- Code expires after a few minutes — resend anytime from the same screen
- Verification ID doubles as the document's IPFS CID
- Every check links out to the live record on PolygonScan
- Revoked, unconfirmed, and verified are shown as distinct states
Starting with degrees.
Ending with every document that matters.
VeriBlock launches with academic credentials — where forged documents do the most damage first. The same hash-and-anchor foundation is built once and extended to professional and personal documents as the network grows. Same pipeline. Broader trust.
Academic credential verification
Universities and colleges issue degree certificates, transcripts, and course completions — sealed with SHA-256, anchored to Polygon, pinned to IPFS. Employers verify instantly with just a PDF and a Verification ID. No wallet, no phone calls, no registrar.
Professional credential verification
The same foundation extends to employers. HR teams issue offer letters, experience letters, and employment records on-chain. Recruiters verify without contacting HR. Revoke instantly when employment ends — no chasing anyone.
Personal document verification
Government-issued documents — passports, licences, residency certificates — with privacy-first architecture. Only the hash and signature ever touch the chain; no personal data stored on-chain. Citizens control what they share and with whom.
Universal trust network
Once the issuer network spans education, employment, and government — the infrastructure becomes a global trust layer. Any trusted issuer onboards, any verifier checks, anywhere in the world.
The questions verifiers actually have.
What if the institution's wallet is compromised?
Only the institution's own wallet can issue or revoke its credentials — there's no shared admin login to steal. If a wallet is compromised, the institution's issuing rights can be disabled from the admin panel while the key is rotated; nothing it already anchored is altered.
Can a credential be revoked after issuance?
Yes — only by the institution that issued it, from the same issuing dashboard, signed with that same wallet. Verifying always checks live status, so a revoked credential shows as revoked immediately, even if the PDF itself still hashes correctly.
Do I need a crypto wallet to verify one?
No. Verification is anonymous and free — a Verification ID and the PDF in hand is all it takes. Wallets are only needed on the issuing side, one per institution.
Why hash the file instead of just trusting the metadata?
Metadata can be edited to match anything — including by AI. A SHA-256 hash of the actual file changes completely the moment a single byte does, which is what makes "File Mismatch — Possible Tampering" a fact rather than a guess.
Stop taking a document's word for it.
Whether you're issuing credentials or checking one someone handed you, VeriBlock gives you a hash-backed answer, not a guess.