A hash chain only proves editing was caught
A chain rebuilt from genesis after deleting inconvenient records still verifies. Counter-signed head attestation is the part that catches deletion, and you can verify a signature without an account.
For the person who has to check someone else’s evidence
You should never need an account to verify a claim.
A manufacturer hands you a Declaration of Conformity, an attestation, or a safety verification bundle. Your job is to check whether it is real, current, and internally consistent — and you should not need to buy anything to do it.
The clocks that apply to youThe regulations create the paper trail you are checking: CRA Art. 14 records (applies since 11 Sep 2026) and Machinery Reg. Annex III 1.1.9 evidence of intervention (applies 20 Jan 2027). Verification of that evidence is engineered to be free at every tier, permanently — the audience for a piece of evidence is a regulator or an insurer, never an account holder.
Why this matters for insurer / auditors
What the paperwork stops telling you
A label can lie about the bytes
The firmware says 3.9.0; the supplier’s published hash for 3.9.0 does not match what is on the machine. That mismatch is a first-class, reportable finding — not silently ignored.
You need to check, not take their word for it
Every verification route — Declaration check, manifest diff, bundle re-check, attestation verify — runs with no account, by design.
What this checks
Proof, not a pitch
Free forever, by design
Declaration check, bundle re-verification, and attestation verification are engineered as always-free — the buyer or auditor is never the paying customer.
Read moreCounter-signed head attestation
A signature over the ledger head by a key the operator does not hold — the one thing that catches a ledger that was quietly shortened.
Read moreYou should never need an account to verify a claim.
Verification stays free, forever, at every tier. Start there.