Skip to content

Academic records · public chain

Decentralized Transcripting on Algorand

Paper transcripts still move at the speed of an office. A seal can be copied. A PDF can be edited. And the student who did the work usually cannot produce the record without asking the institution that filed it.

metaCAMPUS keeps the education file with the student and writes only a cryptographic fingerprint to Algorand. Registrars still attest. Anyone can check that the fingerprint still matches — in seconds, without a fax or a fee that looks like tuition.

Algorand Global x402 Challenge

x402 Credential Verify

This site is marketing only. The paid check lives on a separate HTTPS API. An unpaid call returns HTTP 402. One real MainNet USDC settle is still required before the leaderboard can count a full eligibility.

Live API
metacampus-x402-verify.vercel.app
Routes
GET /health
POST /v1/credential/verify
Status
402 and discovery are competition-ready.

For registrars and students

Why transfers still take weeks

A registrar does not lose a week because the record is hard to read. The week is the queue: a request, a hold, a vendor, a second institution, and a fee schedule between a student and a yes or no.

  • The cost is staff time

    An official copy is labor. Someone confirms identity, clears a hold, pulls the academic history, certifies it, and answers the message that asks where it went. That work is real. It does not scale to every graduate school, employer, and licensing board that asks the same question.

  • Fraud fills the gap

    The certified channel is slow, so unofficial files travel faster. A PDF can be edited. A seal can be copied. The office that needs the record either waits or accepts a document it cannot prove. A chain does not stop a registrar from attesting something false. It does stop a silent edit after the attestation.

  • A third desk in the middle

    Ordering portals such as Parchment, enrollment checks through the National Student Clearinghouse, and international evaluations from World Education Services each do a real job. They also add another login, another fee, and another queue. The student holds a tracking number, not the record.

The cut

A public chain that refuses to hold the file

The Family Educational Rights and Privacy Act is wary of education records escaping into the open. A hash is not the record. It cannot be reversed into a transcript. It can only confirm one. That split is FERPA-minded design — not a certification, and not a legal opinion.

01

Student-owned records

Ownership is not a slogan on a portal. The student keeps the education file and the means to present it — a wallet, not a password issued by last semester’s student-information system. Institutions onboard and attest. They do not remain the only door.

02

Hashes on-chain. Names off-chain.

Algorand should never become a second student-information system. What belongs on the public ledger is a digest: proof that a particular statement existed, in a particular form, at a particular time. Names, birth dates, addresses, and the narrative of a course stay off-chain.

03

Instant global verification

A verifier in another country should not wait on business hours, a wet signature, or a fee schedule. They compare the document the student chose to share with the fingerprint already anchored. It matches, or it does not. Finality is a few seconds, not a term.

04

Course badges

A full transcript is a dossier. Sometimes the claim is smaller: this course, this outcome, this term. The student requests the badge; an authorized registrar mints it. metaBADGES began as competency tokens you could show without mailing an entire file. Course badges give that idea an approval step and an Algorand issuance path.

The path

Five moves, none of them a fax

Roles stay distinct: student, university admin, and a super admin who admits institutions. The reference contracts separate authentication from badge management, so approval is not the same keystroke as issuance.

Algorand is the ledger because outsiders can audit it, settlement takes seconds, and the fee does not impersonate tuition. A private chain would only hide the fingerprint again.

  1. 1

    Anchor a student hash

    A registrar creates a blockchain identifier. The person it points to stays unnamed on-chain.

  2. 2

    Keep coursework off the ledger

    Grades and learning outcomes live with the student or the institution. A fingerprint can be committed when someone attests.

  3. 3

    Request the badge

    The student asks, from their own wallet, for a discrete claim: one course, one outcome, one term.

  4. 4

    Approve, then mint

    An authorized approver signs. Issuance is a separate act from the request — the institution still says what is true.

  5. 5

    Let a stranger check

    A third party verifies the fingerprint. The underlying file appears only if the student chooses to show it.

The desk

Fingerprint a line you would not publish

Nothing on this page talks to Algorand. The desk runs in your browser. Write a sentence you would never put on a public ledger, then take its SHA-256 digest. That digest — not the sentence — is the kind of thing metaCAMPUS is willing to anchor.

The digest appears here. Change one character in the line and the fingerprint will not survive the edit.

Check a claimed fingerprint

Paste a digest and compare it with the line on the left. Edit the line after you copy the hash — a verifier should fail closed when the file and the anchor disagree.

Waiting on a comparison. This check never leaves the browser.