Learning records that can be proven, not just claimed.
ChainLMS records who authored each course, who holds access and who earned each certificate on a Byzantine-fault-tolerant blockchain, so any later alteration can be detected by anyone.
- Latest block
- …
- Validators
- 4 · tolerates 1 fault
- Consensus
- QBFT
- Latest anchor
- …
- Anchored at
- …
In a traditional LMS, whoever controls the database controls the truth.
Traditional LMS
- Scores and completions can be edited without leaving a trace
- Certificates are PDFs, easy to forge and slow to check
- Course authorship rests on the vendor's word
- Audits depend on logs that the same admin can change
ChainLMS
- Results are recorded on a ledger shared by independent validators
- Certificates are non-transferable tokens that anyone can verify in seconds
- Each course version is signed and fingerprinted
- Ledger history is anchored to public timestamps outside our control
From course creation to independent verification
- 1
Create and sign
Creators build a course. Its content is hashed into one fingerprint and signed.
- 2
Enroll with a license
Buying a course issues a non-transferable license token that unlocks the lessons.
- 3
Learn and earn
Encrypted video, files and quizzes. Passing issues a certificate on chain.
- 4
Verify anywhere
Employers enter a certificate number and see the on-chain record, with no account.
Six layers working together
Blockchain is one part of the design. Each layer covers a failure the others cannot.
Fault-tolerant consensus
Four QBFT validators must reach a 3-of-4 quorum. One failed or dishonest node cannot rewrite history.
Agreed reads
Access and certificate checks require matching answers from several nodes, so one lying node is caught.
Content fingerprints
Every lesson, file and answer key goes into a Merkle root. A swapped file no longer matches.
Creator signatures
Creators using MetaMask keep their own key, so nobody can publish under their name.
Sealed coin ledger
Every coin movement is hash-chained and sealed on chain, then audited against balances.
Public anchoring
Batches of block hashes are timestamped through OpenTimestamps, which commits to Bitcoin.
Check a certificate without an account
The record is read from the blockchain, then checked against public timestamp anchors.
Common questions
Do learners need a crypto wallet?
No. Signing in with Google creates a wallet managed by the platform. MetaMask is an option for people who want to hold their own key.
Is course content stored on the blockchain?
No. Videos and files stay in encrypted private storage. Only their fingerprints go on chain, which is enough to detect any change.
Are there gas fees?
No. ChainLMS runs its own permissioned chain with zero gas.
How do payments work?
Learners buy coins by bank transfer (1 coin = 1 USD, shown in VND) and pay for courses with coins. Creators can withdraw to USD or VND.
Can blockchain stop every attack?
No. It makes tampering detectable and attributable. It does not replace access control, backups or careful operations, and we use those as well.
Training records you can prove, not just store.
See how ChainLMS fits your organization, or start learning today.