Comparison
Why “Poor Man’s Copyright” Doesn’t Work
Mailing yourself a sealed envelope is a popular myth. The US Copyright Office explicitly says it offers no legal protection. Here’s why — and what actually does work.
What “poor man’s copyright” claims to do
The theory: mail yourself your creative work in a sealed envelope. Don’t open it. If someone later claims they created the work first, show the sealed envelope with the postmark. The postmark proves you had the work on that date.
It’s appealing because it’s cheap and requires no legal knowledge. It’s wrong for a specific technical reason.
Why it fails: the postmark binds to the envelope, not the contents
A postal timestamp proves one thing: an envelope was mailed on a specific date. It doesn’t prove what was inside the envelope when it was mailed. The envelope can be opened and resealed. The contents can be swapped. There is no cryptographic link between the timestamp and the specific bytes you put inside.
The US Copyright Office addresses this directly in their guidance:
“The practice of sending a copy of your own work to yourself is sometimes called a ‘poor man’s copyright.’ There is no provision in the copyright law regarding any such type of protection, and it is not a substitute for registration.”
Courts don’t treat it as meaningful evidence of creation date. A sealed envelope produced in litigation can’t be verified without opening it — at which point it’s no longer sealed.
What a blockchain timestamp actually does differently
A blockchain-anchored timestamp solves the exact technical problem that makes the envelope myth fail. Instead of timestamping a container (the envelope), it timestamps the contents directly — by reducing the file to a 256-bit fingerprint (SHA-256 hash) and writing that fingerprint to a public blockchain.
The fingerprint IS the file
SHA-256 produces a unique identifier for the exact bytes of your file. Change one pixel, one character, one bit — the hash changes completely. There's no way to swap the contents after the fact.
The timestamp is on a public ledger
The hash is written to a blockchain transaction. Anyone with the file and a block explorer can verify the timestamp independently. No trust required.
It can't be forged
Rewriting the blockchain record would require rewriting every subsequent block — computationally infeasible on a major chain. The postmark can be forged; the blockchain record cannot.
It works before publication
You can anchor a draft, a demo, a working file — anything — before sharing it with anyone. The Copyright Office can't accept unfinished works.
Comparison
| Property | Sealed Envelope | Blockchain Timestamp |
|---|---|---|
| Binds timestamp to file contents | No — binds to envelope only | Yes — SHA-256 hash is file-specific |
| Tamper-evident | No — can be resealed | Yes — any change breaks the hash |
| Independently verifiable | No | Yes — any block explorer |
| Legal standing | None (Copyright Office says so) | FRE 901(b)(9) process authentication |
| Works pre-publication | Yes | Yes |
| Cost | Postage (~$0.68) | Cents per file |
| Speed | Days (mail delivery) | Seconds |
| Recognized by courts | No | Yes, in US federal proceedings |
Why the myth persists
The sealed-envelope technique became popular before digital tools existed. If you created something in 1985 and your only option was expensive, slow, and procedurally complex copyright registration, mailing yourself was at least something. It felt like a record.
Today the cost of a blockchain timestamp is under $1 and the anchoring takes seconds. There’s no reason to use the envelope technique except inertia and not knowing the alternative exists.