“Verified on the blockchain” appears on a lot of credential marketing. Behind the phrase is a simple, useful idea, and a few common misunderstandings.
Fingerprints, not personal data
When a credential is anchored, the issuing system computes a fingerprint of it: a short hash that changes completely if a single character of the credential changes. Only that fingerprint is written to a public ledger, with a timestamp. No names or email addresses go on chain.
What it proves
- The credential existed at the time it was recorded.
- It has not been altered since, because any change would produce a different fingerprint.
- The proof does not depend on the issuer, or its software vendor, still being around.
What it does not prove
A ledger record cannot tell you whether the issuer is trustworthy, or whether a credential was later revoked. That is why anchoring works best alongside a digital signature from the issuer and a live status check on the credential page.
How Hyperstack does it
Every Hyperstack credential is signed with the issuing organisation’s key. On the Enterprise plan, a fingerprint of each credential is also written to the Hedera public ledger, so anyone can prove it existed and has not changed, even without Hyperstack.
Frequently asked questions
It should not be. A well-designed system writes only a fingerprint (a hash) of the credential to the ledger. The fingerprint reveals nothing about the person.
