The only credential evidence
that survives cross-examination.
When an incident happens, the question is always: was this worker certified at the time?Other registries claim it. Meritus proves it — with cryptographic anchoring that traces back to Bitcoin.
After an incident, evidence matters.
Insurers, lawyers, and Ministry of Labour inspectors ask one question above all others.
“Was this worker trained?”
- ✗ An entry in your company database — easy to edit retroactively
- ✗ A PDF certificate — anyone with the file can alter it
- ✗ A vendor's claim — only as good as their integrity + uptime
- ✗ Email screenshots — trivially fabricated, lawyer's objection
“The credential existed at timestamp T.”
- ✓ Hash-chain ledger entry that can't be retroactively inserted
- ✓ Bitcoin block-time anchor — unforgeable past confirmation
- ✓ Independent verification — anyone re-runs the math
- ✓ Court-admissible cryptographic chain
How the cryptographic chain works
Cert attested
When a worker uploads a credential, Meritus hashes it (SHA-256), GPG-signs the attestation, appends to the hash-chain ledger, and submits to OpenTimestamps for Bitcoin anchoring.
Incident occurs
An admin or employer generates a forensic report at the incident timestamp, listing involved workers. The system reads the ledger to determine which credentials were valid at that exact moment.
Report hashed
The report's canonical JSON is SHA-256 hashed. The hash is appended to the meritus ledger as a new entry — bound to the prior entry by hash chain.
Bitcoin anchored
OpenTimestamps submits the report hash to a Bitcoin block. Once confirmed (~1 hour), the report's existence at-or-before the block time is mathematically uncontestable.
What you get
Tamper-evident PDF report
A one-page (when possible) PDF with status badges per worker, attestation hashes, BTC block references, embedded verification QR. Print it. Hand it to your lawyer. Anyone can scan + re-verify independently.
Public verify endpoint
Every report exposes /api/v1/forensic/verify/{hash} (no auth) returning proof metadata. A judge's clerk, an insurance adjuster, an MOL inspector — anyone can confirm the report's authenticity without a Meritus account.
Auto-generated from incident filing
When you file an incident, opt to auto-generate the forensic snapshot at occurred_at. Locks in cert state before evidence can drift. One click; cryptographic immortality.
Bound to a public Bitcoin block
Reports submitted to OpenTimestamps land in a Bitcoin block. The block height + timestamp prove "this report existed at or before [block time]" with mathematical certainty.
Workers see what was generated
Transparency: workers see (in their dashboard) which forensic reports included them. They can verify the anchor themselves. No surveillance — trust earned by mutual visibility.
Who needs forensic chain-of-custody?
General Contractors
After a fall, fire, or workplace death — your $93,500+ Ministry fine defense or $2M+ civil suit defense depends on proving every worker on site was certified.
Insurance Companies
Adjudicating a claim. Was the operator licensed? Did the welder hold current CWB certification at the time of the weld failure? Forensic reports turn argument into math.
Safety Officers / MOL
Site audits + investigation packages. Generate a forensic report for a crew, hand to the investigator, anyone can independently re-verify the cryptographic chain.
Ready to make your compliance defensible?
Free for workers. Free for employers to verify + generate reports. The cryptographic chain is built-in.
Want the technical deep-dive? Read the OpenAPI spec or the source on the public ledger.