Completion certificates that stay verifiable after the system that issued them is gone.
CertHash is a learning management system that records a fingerprint of every certificate it issues on a public blockchain. Anyone can check a certificate against that record. No CertHash account, no API, no CertHash at all.
Stamping runs on RecordStamp, a timestamping service on the Monad blockchain. Only the hash goes on chain. The certificate and the learner's name never do.
Jordan Avery Reyes
has completed Hazard Communication for Supervisors, 4.0 hours, with instructor review.
computing…
A certificate is only as durable as the database behind it.
When the issuer goes away
Training vendors shut down, platforms get migrated, and records get lost in the move. The PDF survives on someone's laptop, but there is no longer anyone to ask whether it is real.
When the PDF is edited
A completion certificate is a document anyone can open in an editor. A changed name, date or course title looks exactly like the original. Verifying today means emailing the issuer and waiting.
When the verifier has no account
Employers, auditors and licensing boards are not users of your LMS. A verification method that needs a login, a vendor portal or an API key is a method most of them will not use.
How a CertHash certificate is issued and checked
Four steps. The first two happen inside CertHash. The last two work without it.
-
1
A learner completes a course
Modules, SCORM packages, assessments and instructor review, the ordinary work of a learning management system. When the completion is approved, CertHash renders the certificate as a PDF.
-
2
The PDF is fingerprinted and stamped
CertHash computes the SHA-256 hash of the finished file and submits it to the RecordStamp contract on Monad from its issuing wallet. The chain records the hash, the block time and the wallet that sent it. It never sees the file.
-
3
The learner keeps the PDF
The certificate carries its own hash and the transaction reference in its footer. That is everything a verifier needs. Nothing about the learner is stored on chain, so the file is the only copy of their name.
-
4
Anyone verifies, anywhere, any time
A verifier hashes the PDF they were given and looks the hash up on RecordStamp or directly on the chain. A match proves this exact file existed at the stamped time and was registered by CertHash. One altered byte and there is no match.
See what gets stamped
Hash any file or some text right here. It is computed in your browser with the Web Crypto API and nothing is uploaded. This is the same fingerprint CertHash records for a certificate.
—
Change one character and watch every cell change. That is why a tampered certificate cannot match its record.
Look up a hash on RecordStampWhat a verifier actually gets
The lookup returns four facts. Together they answer the question an employer or auditor is really asking: is this the document that was issued, and when?
- Exists
- Whether this exact hash has ever been stamped. A forged or edited PDF produces a different hash and returns nothing.
- Timestamp
- The block time when the stamp was recorded. The certificate cannot have been created after this moment.
- Registrant
- The wallet address that submitted the stamp. CertHash publishes its issuing addresses, so a verifier can confirm the stamp came from the issuer and not from the learner.
- Metadata hash
- An optional second fingerprint covering the completion record itself: course, hours, instructor approval. It lets an organization prove the details without publishing them.
Built to outlive its issuer
Monad is a public blockchain and the RecordStamp contract is open for anyone to query. If certhash.com went dark tomorrow, every stamp it ever made would still be there, still answerable by any wallet, explorer or script that can read the chain. That is the whole point.
The platform behind the certificate
Stamping is the part that is new. The rest is a complete learning management system for organizations that have to prove training happened.
Courses and SCORM
Author modules in the platform or import existing SCORM packages. Track attempts, scores and time on task per learner.
Instructor review
Completions can require an instructor's sign-off before a certificate is issued, with course-scoped rights so instructors manage their own rosters.
External certificates
Learners upload, or email in, certificates earned elsewhere. They are reviewed, filed against the person and tracked for expiry alongside internal completions.
Compliance reporting
Who is current, who is lapsing, who has never completed. Reports by person, course, department or deadline, exportable for audits.
Roles and organizations
Administrators, instructors, staff and learners, with permissions tied to courses and departments rather than a single global switch.
Hardened by default
Hosted on infrastructure we operate. Email from the platform ships with SPF, DKIM and DMARC enforcement from day one, so notifications are delivered and impersonation is rejected.
CertHash is in development with a founding client. Early access is opening to a small number of organizations.
Questions people ask first
Is the certificate stored on the blockchain?
No. Only a 32-byte hash of the PDF is recorded, along with the time and the issuing wallet. The hash cannot be reversed into the document, and it contains no name, course or date.
What if the learner loses the PDF?
CertHash keeps the issued file and can re-issue it while the platform is running. The reissued file is byte-identical, so it matches the original stamp. Learners are also encouraged to keep their own copy, because the file is what gets verified.
Does a verifier need a crypto wallet?
No. Reading the chain needs no wallet and costs nothing. RecordStamp's verify page does it in a browser, and the contract can be queried by any public explorer or a few lines of code.
What does it cost?
CertHash is a paid platform. An LMS deployment is priced per user, and certificate issuers pay a fee for each certificate stamped on chain, which covers the stamping, the network gas and the hosted record. Pricing is shared with organizations during early access. Verifying a certificate is always free: anyone can check a hash against the chain without an account or a fee.
Can we stamp certificates we already issued elsewhere?
Yes. Any file can be stamped, including certificates from a previous vendor or paper certificates that have been scanned. The stamp proves the file existed as of now; it does not backdate it.
Who is behind CertHash?
CertHash is built by Pueblo Internet Publishing LLC in Pueblo, Colorado. RecordStamp is a sister project from Blockchain Integration Strategies, the company's consulting practice.
Talk to us about your training records
If your organization issues certificates that other people need to trust, we would like to hear what you issue, who verifies it, and how that goes today. Requests go through the consultation form at Blockchain Integration Strategies, our consulting practice.
Request a consultation