Blockchain and CPD Credentials — What Is the Connection?
Blockchain has been proposed as a solution for credential verification — immutable tamper-proof records of learning that cannot be altered after they are issued. The pitch is compelling on the surface: a distributed ledger that anyone can query, with no central authority able to manipulate the record. For CPD credentials specifically, this sounds like exactly what the sector needs. But the reality is more nuanced than the hype suggests.
What Blockchain Actually Promises for Credentials
The core appeal of blockchain CPD credentials is permanence. Once a record is written to a blockchain, it cannot be quietly deleted or edited. This addresses a genuine concern: certificates get falsified, training providers close down, and databases become inaccessible over time. Blockchain proponents argue that decentralisation solves all three problems at once.
There are real implementations worth examining. MIT Digital Certificates is one of the most cited examples — a project in which the Massachusetts Institute of Technology issued academic credentials anchored to the Bitcoin blockchain. The Blockcerts standard, developed from that work, provides an open framework for issuing and verifying blockchain-based credentials across different platforms and institutions. These are serious technical efforts, not vaporware.
The practical question, however, is whether the problem they solve is the problem most training providers actually have.
The Infrastructure Problem for Small Providers
Blockchain credentials exist, but they require institutional infrastructure. Issuing to a blockchain means managing cryptographic keys, integrating with a ledger, and ensuring the technical chain of custody is maintained indefinitely. For a university with a dedicated IT department, this is manageable. For a small independent training provider running CPD courses, it is a significant overhead with limited return.
For small training providers, blockchain is overengineered. The verification problem they face is not that records are being tampered with at scale — it is that certificates are difficult to verify quickly, or that PDF certificates can be replicated with basic editing tools. Those are solvable problems, and they do not require a distributed ledger to solve them.
Deploying blockchain infrastructure also introduces dependency. If the network changes, if key management fails, or if the organisation maintaining the chain winds down, the credentials become difficult or impossible to verify. Permanence is only guaranteed if the infrastructure is genuinely permanent — which no commercial blockchain service can promise unconditionally.
What the Open Badges Standard Actually Does
It is worth being precise about a technology that is frequently conflated with blockchain in credential discussions: Open Badges. The Open Badges standard does not require blockchain — verification works via secure URL. A badge issued under this standard contains metadata baked into the credential itself, including a link that resolves to a verification endpoint hosted by the issuer or a compliant platform.
Open Badges was developed by Mozilla and is now maintained under the IMS Global Learning Consortium. It is a recognised standard for digital credentials across education and professional development. The verification mechanism is cryptographic and URL-based — not blockchain-dependent. That distinction matters, because many providers assume they need a blockchain to issue credentials that can be independently verified. They do not.
The standard separates two things that often get conflated: the portability of a credential and the immutability of its record. Open Badges solves portability. Immutability, to the extent it is needed, can be addressed through other means — including simple design decisions about how verification endpoints are structured and maintained.
How Verification Works Without Blockchain
The credential verification problem is solved by design, not by blockchain. If a certificate contains a unique identifier linked to a live verification record, and that record is hosted on infrastructure the issuer controls and maintains, then anyone with the link can confirm the credential is genuine. No login is required. No third-party service needs to be consulted. The check is instant.
Open CPD uses URL-based verification — no blockchain required, no login required, instant. When a certificate is issued through the platform, it contains a unique verification URL. Anyone — an employer, a regulator, a professional body — can visit that URL and confirm immediately whether the certificate is valid, who it was issued to, what the course covered, and when it was completed. The process takes seconds.
This approach is simpler than blockchain and equally effective for the actual verification scenarios that arise in CPD contexts. An employer checking a candidate’s certificate does not need a blockchain query. They need a URL that works and a clear confirmation page. That is what URL-based verification delivers.
From Badges to Blockchain — The Open CPD Context
When I built Open CPD, I looked at the full range of credential technologies — from badges to blockchain — and made a deliberate choice. The sector being served is independent training providers issuing CPD certificates in the UK. The verification need is real, but it is not exotic. Employers want to check certificates quickly. Professionals want to share credentials credibly. Regulators want an audit trail.
None of those needs require blockchain. They require a well-structured verification system that is reliable, accessible, and designed to last. The Open Badges standard provided the conceptual foundation — metadata-rich credentials with verifiable links — and URL-based verification provided the mechanism. The result is a system that any provider can use without technical complexity, and that any verifier can use without an account or specialist knowledge.
Blockchain CPD credentials will remain a topic of discussion, and in some institutional contexts they may make sense. MIT Digital Certificates and the Blockcerts standard demonstrate that the technology can work at scale. But for the majority of CPD providers operating in the UK, the architecture is disproportionate to the problem. Verification via secure URL is simpler, equally trustworthy, and does not require a provider to become a cryptography specialist to issue a credible certificate.
