Blockchain in intellectual property: what a timestamp proves for freelancers

Blockchain in intellectual property does one narrow job well: it puts a date on a file. You hash the file, the hash goes into a block, and from then on anyone holding the same bytes can show that this exact version existed no later than that block. That's useful evidence. It isn't copyright, it isn't registration, and it doesn't say who made the work.

For a freelancer, that difference decides what you can do in a dispute. A blockchain record helps when the fight is about when: a client says they came up with the concept, a copycat says their version came first. It does very little when the fight is about who owns it. Ownership comes from the contract you signed, and in the US your right to sue and to collect statutory damages comes from registering with the Copyright Office.

If you sell work to clients, the Chaindoc page for freelancers shows how the same record attaches to a signed contract.

Nothing you made goes on the chain. What goes there is a hash: a fixed-length fingerprint computed from the file's bytes with a function such as SHA-256. Change one pixel or one comma and the hash changes completely. You can't rebuild the file from its hash, so recording one doesn't publish your work.

Each block carries a time, so the record says, in effect, "a file with this fingerprint existed by this moment". Using it later takes three things:

• the original file, byte for byte, kept somewhere you control;
• the transaction that holds its hash;
• someone who shows the two match, by recomputing the hash and reading the block time.

That last step is ordinary forensic practice, and it's where blockchain in intellectual property gets its credibility. US federal courts already let a qualified person certify that a copy is identical to an original by comparing hash values (Federal Rules of Evidence, Rule 902(14)). A blockchain adds an outside date to the hash being compared.

Here's what Chaindoc puts on chain, in plain terms. When you upload a document, the server computes its hash. When you publish a version, that version's hash is written to a public blockchain. When every signer has signed, a proof for each signer is recorded. Your file never goes on chain, and neither do names, emails or other identities: those stay in Chaindoc's audit trail, off chain.

Think of a hash record as a very good postmark. It answers one question with high confidence: did this exact file exist by this date? Everything else is inference, and a court will want other evidence for it.

A record helps most in a priority fight. Say you pitched three logo concepts in March, the client walked away, and in June their new brand looks a lot like concept two. To prove copyright infringement you need ownership of a valid copyright and copying of what's protected in it. Your March hash doesn't prove copying. It does pin your concept to a date before theirs existed, which makes "we came up with it ourselves" much harder to sustain next to the emails showing they saw your drafts.

What it can't do is a longer list. A hash doesn't identify an author: whoever uploaded the file made the record, and an uploader can record someone else's work. It doesn't show originality, because you can timestamp a stock image as easily as your own drawing. It doesn't show that no earlier version existed somewhere else. It doesn't transfer or reserve a single right. And it only matches the exact bytes you recorded, so the JPEG a social network recompressed, or the PDF a client re-exported, won't match the hash of your original.

Honestly, most of what's written about blockchain in intellectual property blurs these limits. A record is evidence of existence and integrity. Authorship you still prove the old way, with source files, sketches, the dates inside your working files, the brief, the invoice. The blockchain makes the date part of that story hard to argue with. It doesn't write the rest of the story for you.

In the US, copyright exists from the moment the work is fixed in a tangible form. No filing is needed, and the Berne Convention bars member countries from making protection of foreign works depend on one. So why do US lawyers keep telling freelancers to register? Because registration buys three things no timestamp does.

The right to sue. For a US work, the Copyright Office's own FAQ is plain: you have to register before you can bring an infringement suit. A blockchain record doesn't meet that requirement.

Statutory damages and attorney's fees. They're off the table for infringement that started before registration, unless you registered within three months of first publication. For a freelancer that often decides whether a case is worth bringing, because proving actual lost profit on one illustration is hard.

A presumption. A certificate issued before or within five years of first publication is prima facie evidence that the copyright is valid and that the facts in it are true. The burden moves to the other side. A blockchain record has no such statutory weight in the US. It's evidence the court weighs like any other.

So the honest split between registration and blockchain in intellectual property looks like this. Register the works you would actually sue over: a flagship illustration, a typeface, a book, a photo series you license. Use a timestamp for the volume in between, meaning drafts, concepts, rejected pitches and client revisions, all the things you'd never register one by one but might need to date later.

Mailing yourself a sealed copy is the oldest version of this idea. The Copyright Office says the law has no provision for a "poor man's copyright" and that it's no substitute for registration. A postmark is ordinary evidence of a date.

WIPO PROOF, the digital version, issued tokens holding a file's fingerprint and a date until January 31, 2022. France's INPI still runs e-Soleau, a paid deposit it calls proof that a creation existed at a given date. For a date that's hard to challenge, a notarial record of the facts is the heavier option.

No amount of blockchain in intellectual property answers this one. The contract does, and US law starts from a default that surprises a lot of clients: if you're a freelancer and nothing is signed, you own what you made. Paying for the work doesn't transfer the copyright.

Work made for hire

A work is "made for hire" in only two ways under 17 U.S.C. § 101. An employee creates it within the scope of the job, or it's specially commissioned, falls into one of nine statutory categories, and both parties sign a written instrument that calls it a work made for hire. The nine are a contribution to a collective work, part of a motion picture or other audiovisual work, a translation, a supplementary work, a compilation, an instructional text, a test, answer material for a test, and an atlas. If the work qualifies, the client is the author from day one and you have no termination right later.

Whether you're an employee is a separate question, and the contractor-versus-employee tests decide it, not your job title.

Assignment and licence

Everything outside those nine needs an assignment: a transfer in writing, signed by the owner (§ 204(a)). An exclusive licence counts as a transfer too and needs the same signed writing; a nonexclusive one doesn't. After an assignment you're still the author, and US law lets an author end a transfer during a five-year window that opens 35 years after the grant (§ 203). Clients' lawyers know this, which is one reason they reach for "work made for hire" first.

If your clients are in Germany, the copyright itself can't be transferred at all. Clients receive rights of use instead, under § 29 of the German Copyright Act. A US-style "all right, title and interest" clause doesn't do in Berlin what it does in New York.

Most countries don't require registration before you sue, so the question of who had the work first carries more weight there.

Under the Berne Convention, countries can't attach formalities to the rights it covers (Article 5(2)), and whoever is named as author "in the usual manner" is presumed to be the author (Article 15(1)). Germany writes the same presumption into § 10 of its Copyright Act, Spain into article 6 of its intellectual property law. Put your name on the work and the burden starts on the other side.

EU law goes further on dates. Under the eIDAS Regulation, a court may not reject an electronic time stamp only because it's electronic (Article 41(1)), and a qualified time stamp is presumed accurate as to date, time and the integrity of the data it's bound to (Article 41(2)). Since the 2024 amendment, electronic ledgers get parallel treatment. A ledger can't be denied legal effect for being electronic, and records in a qualified electronic ledger are presumed to be in unique, accurate chronological order and intact (Article 45k). Qualified ledgers have to be run by qualified trust service providers (Article 45l), and that status can be checked on the EU Trusted List. An ordinary public blockchain record, including the one Chaindoc writes, can't be thrown out just for being electronic (Article 45k(1)). The stronger presumption belongs to qualified ledgers only.

Several countries also keep optional public registries: Spain's Registro de la Propiedad Intelectual, Mexico's INDAUTOR, Brazil's Biblioteca Nacional. None of them is a condition of protection. That's where blockchain in intellectual property fits best abroad: as a cheap, dated record for the many files you'd never register, next to the formal registry for the few you would.

Dating files is the part of blockchain in intellectual property that works today. Other blockchain intellectual property use cases are uneven:

• Licensing and royalties. Smart contracts can pay a licensor automatically when a licence token changes hands. That works inside one marketplace. Outside it, a court reads the licence text, not the code.
• NFTs. Buying one usually transfers a token, not the copyright, unless a signed writing says otherwise (§ 204(a) again).
• IP offices exploring shared ledgers. WIPO runs a standards workstream on blockchain for IP offices; none of it changes how your copyright comes into being.
• Anti-counterfeit tracking of physical goods, which is closer to trademarks than to freelance work.
• Signed agreements with a dated record of each version. The least exciting item, and for freelancers the most useful, because it ties the file, the version and the client's signature together.

The common thread in blockchain intellectual property rights and management projects: a ledger is good at recording that something happened and when. It isn't good at deciding what the law makes of it. Anything that needs the second part still ends in a contract and, now and then, a courtroom.

None of this needs a lawyer on retainer or a crash course in blockchain in intellectual property. It needs a few habits you keep while the work is fresh.

1. 1.
   Record drafts at milestones, as well as the final file. The concept round, the approved direction and the delivered files each get their own hash.
2. 2.
   Keep the original bytes next to their record. A re-saved PSD has a new hash, and so does an exported copy of it.
3. 3.
   Hash the source, not just the export. Layered files, sketches and project folders show process; a flat PNG shows only a result.
4. 4.
   Write ownership into the contract before work starts: licence or assignment, which uses, which territory, from when. Say whether rights pass on signature or on final payment.
5. 5.
   Get the transfer signed. A signed writing is what § 204(a) asks for, and an e-signature counts for most US commercial contracts (see when the law accepts an electronic signature).
6. 6.
   Register what you'd sue over. In the US, do it before publication or within three months after.
7. 7.
   Keep the delivery trail: what you sent, when, to whom, and what the client approved. A signing tool keeps part of it for you; here's what a signing audit trail records.

Fair warning: step 1 is the one people skip. It's also the only one you can't do after the fact.

It's worth it when you produce a lot of work you'd never register piece by piece but might one day need to date: concepts, drafts, pitch decks, code, copy. It's worth it when clients dispute versions, because a hashed, signed version settles that argument quickly. And it's worth it when you already send work for signature, since the record comes with the contract instead of as a separate chore.

Where it falls short: as a stand-in for registration on the handful of works you'd actually sue over, or for a clear ownership clause. Nor will it rescue a dispute about work you recorded after the fact.

If we had to pick one change for a freelancer reading this, it would be two lines long. Put the ownership clause in writing on your next contract. Then record the drafts that go with it. Blockchain in intellectual property is the second line, not the first.