Blockchain certification: what the record actually shows

Calling a certificate “blockchain” does not make an object authentic on its own. It makes a history checkable: what was declared, when, by which issuer inside the system, and under which public identifier. How solid that evidence is depends as much on how the facts were entered as on the anchoring tech.

What a certificate usually holds

You will often find a description of the specimen, the issuer, a timeline of events, sometimes attached documents. Those are structured declarations. They help you follow a piece and inspect it. They do not replace a physical review by someone who knows how to look at the object.

What an anchor lets you check

When a record is anchored (distributed ledger, cryptographic digests), a third party can check that the published data was not rewritten later in that ledger. MakeSure uses that idea: a public tracking identifier is bound to an integrity proof, without putting personal data on the public record.

What it does not prove on its own

• That the original information was true. A false declaration that gets anchored stays false, and fixed.
• The real condition of the object (materials, wear, attribution) without a competent human look.
• Legal title. A digital history is neither a court ruling nor a notarial deed.

Binding the piece to the record

Without a reliable link between the specimen and the file, the proof stays abstract. MakeSure presents a GS1 Digital Link QR today for public traceability and the digital product passport. An NFC chip is coming as a premium option for pieces where unit-level authentication really matters. It is not yet the default on every product.

The public technical overview is on the Technology page.

How to read a MakeSure certificate

The basic path is straightforward. The issuer creates the certificate and attaches a public identifier. The QR opens the tracking page: declared history, events, attached documents when there are any. If the piece also carries an NFC chip (premium option), a unit check sits on top of that reading. What you are checking then is the coherence of the file and the integrity of the anchor, not every physical attribute of the object.

Provenance, possession, ownership

These words are not synonyms. Provenance is the declared history. Possession is who holds the object or the authentication carrier. Ownership is a legal question, and depends on the evidence a dispute will accept. A protocol can log transfers and access checks. It does not settle the law for you.

What to check before you trust it

1. Does the QR or URL land on a coherent domain and identifier?
2. Can the declared issuer be identified outside the certificate?
3. What is public, and what stays private?
4. Is there a physical link (label, QR, NFC) actually on the piece?
5. Do the dates and events hold up, without odd gaps?
6. Does the certificate claim to settle a legal point it cannot settle?

Where MakeSure stands today

We open on art and collectibles. Other sectors sit on the roadmap. Today we draw a clear line between QR / Digital Link (traceability, digital product passport) and NFC (premium, upcoming). A verifiable proof is not a blanket guarantee against every fraud.

For a concrete case, write to us via Contact.