Horodatages blockchain & eIDAS : non légalement valides — Pourquoi ?
Les horodatages blockchain ne sont pas qualifiés eIDAS. Seul un horodatage RFC 3161 émis par un QTSP bénéficie de la présomption légale des articles eIDAS 41 et 42.
En avril 2025, un avocat munichois specialise en brevets a recu un client implique dans un litige de droit d'auteur logiciel. Le client avait utilise un service d'horodatage blockchain pour enregistrer un hash de sa base de code sur le reseau Ethereum six mois auparavant. La partie adverse disposait d'un horodatage RFC 3161 emis par un Prestataire de Services de Confiance Qualifie. L'audience a dure quarante minutes. L'horodatage blockchain a ete admis comme preuve complementaire. L'horodatage QTSP beneficiait d'une presomption legale en vertu de l'Art. 41 eIDAS. L'avocat du client savait dans les dix premieres minutes comment l'apres-midi se terminerait.
Les services d'horodatage blockchain commercialises comme outils de preuve juridique se sont multiplies. Beaucoup pretendent prouver l'existence d'un document a une date precise en enregistrant son hash sur un registre public. L'affirmation est partiellement vraie et significativement trompeuse.
Protégez votre travail avec Swiss Trust Layer AG
Scellez votre propriété intellectuelle avec un e-Sceau prouvé en justice, soutenu par Swisscom Trust Services.
Réserver une Démo GratuiteRelated Articles
The CHF 5 file that can save a CHF 200,000 IP dispute
Most IP disputes are not decided by who had the better idea. They are decided by who can prove it. A qualified electronic seal under ZertES Art. 14 and eIDAS Art. 25(2) shifts the legal burden of proof to the opposing party. Without one, you spend the dispute explaining yourself.
A checkbox is not proof: labelling versus evidence under the AI Act
A label and a record look identical on a page and behave completely differently the moment somebody questions them. This is what separates a self-declaration from evidence, why the usual internal records do not close the gap, and what a qualified timestamp changes.
Article 50 is live today. Here is how to prove your content is compliant.
The transparency obligations in Article 50 of the EU AI Act apply from today. This is what the obligation actually requires, why a label alone leaves the burden of proof with the publisher, and the four parts of a record that somebody outside your organisation can check.
What EU AI Act Article 50 actually asks you to do, in plain terms
Article 50 of the EU AI Act applies from 2 August 2026. This is a plain reading of what it asks for: who it binds, what content is in scope, what labelling actually means in practice, and the three questions worth settling before Monday morning.
Qualified signing in plain terms: everything we covered this month
A month of articles on qualified signatures, timestamps, provenance, and proof, collected into one explanation of how the pieces fit together and which one you actually need.