Glossary

What Is Blockchain Certificate?

A blockchain certificate is a digital certificate whose proof of existence is written to a public blockchain, so anyone can confirm it was issued at a given moment and hasn't been altered since.

Also called: blockchain credential, NFT certificate

What it's for

The problem a blockchain certificate sets out to solve is a narrow one: proving that a certificate existed, unchanged, at a particular moment, without anyone having to trust the issuer's records. Write a fingerprint of the certificate to a public chain, and the timestamp is beyond the issuer's power to edit later.

That's genuinely useful in a small number of situations. It's also, in most of the cases it gets sold for, solving a problem the buyer doesn't have.

How it works

The certificate itself almost never goes on the blockchain — it would be public forever, which is the last thing you want for a document carrying someone's name and email. What gets written is a hash: a short fingerprint computed from the certificate's contents.

Verifying means recomputing the hash from the certificate in front of you and checking it against the chain. Match, and this is the exact document that was anchored. Mismatch, and something has changed.

What that buys you is timestamping and immutability. What it does not buy you:

• Authenticity. The chain proves a hash was published, not that the publisher is who they claim. That still comes from a signature and a known key.
• Truth. A blockchain will faithfully preserve a false claim forever.
• Revocation. Immutability actively works against you here — withdrawing an anchored credential needs a second mechanism anyway.

An ordinary digital signature already gives you authenticity and tamper-evidence, which is what most people actually mean when they ask for a blockchain certificate.

Where you'll see it

MIT's Blockcerts work made the pattern well known in education, and it's standard in some national qualification registries. It also appears heavily in marketing, where "blockchain-verified" is often doing rhetorical rather than technical work — a certificate can be tamper-evident and independently checkable with no blockchain anywhere near it.

In Verifycate

We don't use a blockchain, and we'd rather say so plainly than dress up what we do. Certificates are signed with the workspace's own Ed25519 key as Open Badge 3.0 credentials, which gives tamper-evidence and independent verification — the two properties people are usually after. What it doesn't give is an issuance timestamp that survives us: our records are the record.

If a public, issuer-independent timestamp is a requirement for you — a national registry, a regulated qualification — pick a platform that anchors to a chain.

Everything on this page runs in Verifycate. The first 300 certificates are free, no card. Start for free

Common questions

Do I need blockchain to make certificates tamper-proof?

No. A digital signature makes a certificate tamper-evident: any change breaks it. A blockchain adds a public, issuer-independent timestamp on top. Useful, but a different property, and needed far less often than it's sold.

Is the certificate itself stored on the blockchain?

Almost never. Only a hash goes on-chain, because a public chain is permanent and a certificate carries personal data. The certificate stays with the issuer or the recipient.

Can a blockchain certificate be revoked?

Not by removing it — nothing on a chain can be removed. Revocation needs a separate published status list the verifier also checks, which means the issuer is back in the loop the blockchain was meant to remove.

Related terms

• Verifiable CredentialA Verifiable Credential is a claim about someone, signed by whoever made it, in a W3C format any verifier can check on its own — without contacting the issuer.
• Certificate VerificationCertificate verification is confirming that a certificate was really issued by the organisation it names, to the person it names, and hasn't been altered since.
• Open Badge 3.0Open Badge 3.0 is the current version of the Open Badges standard, rebuilt on the W3C Verifiable Credentials data model so a badge carries its own cryptographic proof instead of relying on the issuer's server staying online.
• E-certificateAn e-certificate is a certificate issued and delivered electronically instead of on paper — at minimum a file, and at best a link anyone can open and check.

Issue certificates people can actually check.

Every certificate gets a QR code, a public page, and an Open Badge 3.0 credential. 300 free credits, no card.

“We issued 2,000+ certificates for InCTF — winners, participants, the lot.” — Aravind BL, Amrita InCTF

Start for free

All glossary terms