When French fashion house AZ Factory took clothing wholesaler Valeria Moda to court over counterfeit garments, it introduced an unconventional piece of evidence: blockchain timestamps proving its design files predated the infringing copies.
The dispute centered on two signature creations, Love from Alber and Hearts from Alber. Valeria Moda challenged both the infringement claims and AZ Factory’s underlying copyright ownership. AZ Factory faced a dual burden: proving its chain of title and establishing an incontrovertible timeline of creation.
On 20 March 2025, the Marseille Judicial Court ruled in AZ Factory’s favor. Central to the decision were two blockchain timestamps registered on 5 May and 15 September 2021. An independent bailiff’s report from 19 October 2022 corroborated these records. In France, a bailiff (commissaire de justice) is an authorized legal officer whose formal observations carry significant evidentiary weight in court; here, the report documented the formal verification of the timestamp records. Alongside evidence of public release under AZ Factory’s name, the court accepted the timestamps as legitimate proof of prior existence. (Read the full EUIPO case summary).
For creators across fashion, jewelry, and furniture design, the takeaway is clear: the strongest defense against infringement is built while the work is taking shape, long before a dispute surfaces. Contemporaneously certifying and preserving your designs as they evolve establishes a verifiable, objective record of what you created and precisely when.
What the timestamp contributed
Digital files are inherently fragile evidence. Operating system metadata—such as file names and local "Date Modified" stamps—carries little weight in court. Files are routinely renamed, moved, duplicated, and re-exported, altering local timestamps in the process. When an infringement dispute arises years later, local file metadata rarely withstands legal scrutiny.
A blockchain timestamp anchors the file to an immutable reference point outside your personal computer.
The process begins with a cryptographic hash, a unique digital fingerprint calculated mathematically from the file's contents. If a single pixel, curve, or character changes, the hash changes completely. Anchoring this fingerprint into a public ledger like Bitcoin provides tamper-resistant proof that the exact matching file existed on or before that entry was recorded. Beyond verifying existence and integrity, this mechanism also establishes proof of possession: by demonstrating control over the private key used to sign the Bitcoin transaction containing that fingerprint, the owner can provably show they held the file at the time of registration.
Crucially, only the fingerprint is written to the blockchain; the design file itself remains entirely private. This distinction is vital when handling unreleased collections, sensitive client proposals, or proprietary prototypes. You can establish incontrovertible proof of prior existence without exposing commercial assets on a public ledger.
However, you must keep the exact source file. A blockchain certificate cannot reconstruct a misplaced sketch, nor can it validate an export altered after the timestamp was generated. (In this post, we break down three common ways you might inadvertently sabotage your own digital certificates. )
Show how the design evolved
A solitary timestamp answers a narrow question: Did this specific file exist by this date?
In copyright disputes, however, an organic creative trail tells a far more compelling story. A persuasive narrative rarely starts with a polished final export; it begins months earlier with the first rough sketch, pattern experiments, revised color palettes, factory sample revisions, and technical production packs.
By certifying these milestones throughout development and maintaining them within a version-controlled project, you build an unbroken chronology of creation. Each certificate benchmarks a specific iteration. Together with the stored source files, these records allow a judge, adversary, or examiner to trace how a concept matured into a finished design.
This developmental history reinforces your final claim. It proves that distinctive aesthetic features were not copied at the last minute, but evolved organically across revisions. An infringer claiming independent creation will struggle to counter a dated, chronological trail of iterative work. Crucially, this record cannot be retrofitted: certifying a batch of legacy drafts today only proves they exist today, not when they were originally drawn.
Chronological proof must also connect directly to the individuals involved. Always store design briefs, contributor agreements, sign-offs, and delivery emails alongside your certified files. Anyone can timestamp an arbitrary digital file; timestamping someone else's work does not grant ownership. Regular timestamping does not create copyright—it supplies the verifiable evidentiary foundation needed to enforce it.
Three situations where this matters
Certification and secure storage serve distinct, complementary roles. Certification delivers a legally defensible, verifiable date; storage preserves the exact source files required to substantiate it. Encrypted, versioned storage ensures your confidential iterations remain protected without being overwritten as designs evolve.
1. Sharing unreleased collections with third parties
Before production begins, you often need to share technical drawings, patterns, or renders with external manufacturers for quoting. The risk of leaks or unauthorized copying is high. Even with a signed non-disclosure agreement (NDA), parties frequently dispute which specific files were covered.
Before sharing, certify the collection and securely store that exact version. Reference the certificate's unique identifier directly in the NDA or its annex. This binds both parties to an unambiguous, tamper-proof inventory of disclosed files without embedding large, proprietary designs into the contract text itself. Keep an audit trail of what was sent and to whom.
When design revisions occur, update the certified references accordingly. The agreement defines the legal obligations; the certificate and stored files establish the exact subject matter. See our guide on the NDA and contracts use case.
2. Managing fragmented studio workflows
Modern creative workflows are rarely linear. An illustrator sends a draft by email, a colleague adjusts the color scheme, and a freelance CAD specialist delivers the production files. If team members depart or a client questions a design’s provenance months down the road, reconstructing its history across scattered inboxes and shared drives is nearly impossible.
Consolidating versions into a centralized project and certifying them upon arrival preserves the creative chain of custody. Storing contributor identities, copyright assignments, and sign-offs alongside the timestamped files allows you to instantly trace every contribution and defend your intellectual property.
3. Defending against lookalike launches
A competitor debuts a product unmistakably derived from yours. You scramble to assemble evidence, only to find your working directory contains only the latest production export—dated weeks after the competitor’s launch—while earlier working sketches were overwritten or discarded.
If you have systematically certified and stored iterative milestones, you can readily retrieve earlier drafts and their corresponding timestamps. Demonstrating that signature motifs existed in your studio months before the competitor’s release shifts legal leverage decisively in your favor. A timestamp secured today cannot rescue an overwritten file from last year, making proactive archiving essential.
Build the evidence as you work
Bernstein unifies certification, storage, and secure sharing into a single creative workflow. Encrypted, version-controlled storage safeguards your proprietary files as concepts evolve, while Secure Sharing lets you govern access, log recipient consent, and maintain an immutable audit trail. Certificates integrate directly into contractual agreements to identify protected IP unambiguously.
Should you ever need to demonstrate ownership or provenance, every file and its corresponding cryptographic proof are instantly accessible. Using Bernstein’s validator, you, your legal counsel, or opposing parties can independently verify file authenticity without complex technical workflows.
For an in-depth legal analysis of the admissibility of cryptographic proof across international courts, read our open-access study: Blockchain Evidence in Court: A Cross-Jurisdictional Study of Admissibility and Weight.
