A technology in the service of proof

Blockchain is not an end in itself here. It serves one precise purpose: guaranteeing that a certificate has not been altered since the day it was issued.
This page describes the architecture in accessible terms: what is calculated, where it is recorded, who can verify and what guarantees result.
The technical choices favour sobriety: little data on the chain, no personal data, and an architecture deliberately simple to audit.
The architecture in figures
From certificate to anchoring
- Fingerprint
An algorithm calculates a 256-bit fingerprint of the certificate and its file.
- OIMAP Registry
The fingerprint is recorded on a permissioned distributed ledger, kept by OIMAP and its Member States.
- Grouping
The day's fingerprints are grouped in a cryptographic tree.
- Anchoring
The root of the tree is published on a public blockchain.
- Time-stamping
The date of publication proves that the fingerprint existed at that moment.
Why two layers?
A permissioned ledger makes it possible to control who writes: only OIMAP can record a fingerprint. A public blockchain allows anyone to verify that this record exists, without depending on OIMAP.
The combination brings the discipline of one and the neutrality of the other: no one, not even OIMAP, can backdate or alter a fingerprint that has already been anchored.



OIMAP ledger or public blockchain

OIMAP Registry
Permissioned- Written only by OIMAP
- Data associated with the file
- Consultable by professionals
Keeps control and confidentiality.

Public blockchain
Open- Readable by all
- Contains only the root of the tree
- Impossible to rewrite
Guarantees the date and neutrality.
No personal data
What is stored, and where
| Data | OIMAP Registry | Public chain |
|---|---|---|
| Certificate fingerprint | Yes | Via the root of the tree |
| OIMAP number | Yes | No |
| Owner's name | No (kept in the Registry) | No |
| File and documents | No (kept in the Registry) | No |
| Date of entry | Yes | Yes |
The technical choices
- Permissioned ledger
Choice of a controlled ledger for writes.
- Public anchoring
Daily publication of the root.
- Audit
First independent audit of the architecture.
- States' nodes
Member States host verification nodes.
Case study: detecting a forgery
An altered certificate
A certificate is doctored to change a dimension. A buyer has it checked.
- The file received is submitted to the verification page.
- The recalculated fingerprint differs from the anchored one.
- The page displays “document altered”.
The forgery is exposed in a few seconds, without any intervention by OIMAP.



Good practices
An engineering principle

« The simpler a system is, the easier it is to audit, and so to trust. »
Technical vocabulary
- Hash
- Digital fingerprint of a file.
- Merkle tree
- Structure that groups many fingerprints into a single root.
- Node
- Computer taking part in the verification of a ledger.
- Anchoring
- Publication of a fingerprint on a public chain.
Frequently asked questions
Does blockchain consume a lot of energy?
Anchoring is published only once a day; the energy footprint is negligible.
What happens if the public chain disappears?
The OIMAP ledger keeps the fingerprints and the anchoring proofs; a new anchor is published on another chain.
Who can verify?
Everyone, thanks to the verification service.
Can OIMAP modify a fingerprint?
No: it can publish a new one (revocation, update), but never erase the old one.
Technical documents
Contacts

Verify a certificate
Image credits (16)
- Historiated Initial (O) Excised from an Antiphonary: The Donor, Gorus Fucci, Kneels before Christ (c. 1300–1350) — Cleveland Museum of Art, CC0 1.0
- Seal with Two Qilin Playing (1849) — Cleveland Museum of Art, CC0 1.0
- Jar with Design in Underglaze Iron (1800s–1900s) — Cleveland Museum of Art, CC0 1.0
- Turtleback Reading Lamp, Tiffany Glass & Decorating Company (c. 1895–1902) — Cleveland Museum of Art, CC0 1.0
- Mirror with Concentric Circles, an Immortal, and Auspicious Animals (100 BCE–100 CE) — Cleveland Museum of Art, CC0 1.0
- Carved Lacquer Scroll Box (1736–95) — Cleveland Museum of Art, CC0 1.0
- Lampas with foliate medallions in ogival lattice (1400s) — Cleveland Museum of Art, CC0 1.0
- Jar with Stamped Decoration (1400s) — Cleveland Museum of Art, CC0 1.0
- Daffodil Table Lamp, Tiffany Studios (c. 1910–13) — Cleveland Museum of Art, CC0 1.0
- Teapot with Landscape and Imperial Poem, Chen Hanwen (1762–95) — Cleveland Museum of Art, CC0 1.0
- Arion on a Sea Horse and Bacchante on a Panther (pair), William Adolphe Bouguereau (1855) — Cleveland Museum of Art, CC0 1.0
- Egypt and Nubia, Volume I: The Great Temple of Aboo-Simble, Nubia, Louis Haghe (1846) — Cleveland Museum of Art, CC0 1.0
- Prayer Niche (Mihrab) (c. 1500s or mid-1900s) — Cleveland Museum of Art, CC0 1.0
- Mirror with Concentric Circles, an Immortal, and Auspicious Animals (25–100 CE) — Cleveland Museum of Art, CC0 1.0
- Dr. James Stuart; Mary Campbell Stuart, Gilbert Stuart (c. 1815) — Cleveland Museum of Art, CC0 1.0
- Annunciation to the Shepherds: Leaf from a Book of Hours (1 of 6 Excised Leaves), Henri d'Orquevaulx (c. 1420–30) — Cleveland Museum of Art, CC0 1.0
Cleveland Museum of Art · CC0 1.0
VerificationCheck the authenticity of a digital certificate free of charge and without an account: number, QR code, file or token.›
Backed NFTsThe non-fungible token backed to a work's file: what it is for, how it is passed on and what it does not do.›
Directive No. 2019-07The protocol for authenticating cultural property: five titles and twenty-four articles that set the common method of certification.›