Encypher vs WordProof
Blockchain timestamping proves your content existed at a point in time. Embedded provenance proves you own it, wherever it travels.
Timestamping vs Provenance
WordProof and Encypher both aim to help content creators prove ownership. The difference is architectural, and it has real consequences for how enforcement works.
WordProof works by hashing your content - producing a short cryptographic fingerprint - and recording that hash on a blockchain. The blockchain creates a timestamped, immutable record. If someone disputes when you published something, you point to the on-chain record. This is a timestamp: evidence that a specific version of content existed at a specific time.
The limitation is that this proof is external. The blockchain record lives on a blockchain. The content lives on your server. When an AI system scrapes your article, it gets the text. It does not get the blockchain record, the lookup link, or any indication that a record exists. The proof stays behind.
Encypher embeds the ownership proof in the text itself, using proprietary invisible encoding. When an AI scraper copies your article, the provenance record travels with it. When the scraped text is processed as training data, the embedded signature is there. When a downstream output is examined, the marker identifies the source content. The proof follows the content.
The Distinction in One Line
Timestamping proves content existed. Provenance proves ownership wherever content appears.
What WordProof Does Well
For its intended purpose, WordProof works. Blockchain timestamping has several genuine advantages.
The on-chain record is decentralized and auditable. Anyone can verify the timestamp without trusting WordProof specifically - the record is on a public blockchain. This is valuable for content disputes where the question is "who published this first?" and both parties have external records to compare.
WordProof integrates cleanly with WordPress, which is where a large portion of the world's web content lives. The friction to adopt is low. You install the plugin, authenticate, and your content is timestamped at publication without changing your workflow.
The Schema.org integration in WordProof is a practical SEO benefit: timestamped content can carry structured data indicating when it was published, which some search engines use for freshness ranking.
Where External Proof Reaches Its Limits
The architectural constraint of external proof becomes most visible in the AI training data context.
When AI companies train models on web content, they scrape text. They do not follow the provenance links. They do not query blockchain records. They get the raw text, and the raw text - in WordProof's architecture - contains no ownership signal.
Once your content is inside a training corpus, or inside an AI system's knowledge, or reproduced in an AI-generated output, there is no path back to the blockchain record. The timestamp proved that the content existed. It cannot prove, at that point, that this specific piece of training data was sourced from your article.
The second limitation is licensing signals. A blockchain timestamp records a hash and a timestamp. It does not encode licensing terms. There is no way to express "this content is licensed for indexing but not for training" inside a WordProof timestamp. Those terms exist somewhere else, in a robots.txt file or a terms of service page, and AI systems have varying degrees of compliance with those mechanisms.
Encypher addresses both gaps by embedding a signed payload directly in the content. The payload includes the publisher identity, publication timestamp, content hash, and machine-readable licensing terms. Every copy of the content carries this information regardless of how it was distributed.
The Syndication Problem
Publishers syndicate content. Articles appear on partner sites, in RSS feeds, in news aggregators, in email newsletters, in social media reposts. Each of these is a copy that has traveled outside the original publication context.
With WordProof, each of these copies is a dead end for provenance: the text is present, the blockchain record is not. Tracking which copies exist, who published them, and whether they have licensing authority requires manual tracking or third-party tools.
With Encypher, every copy carries the same embedded signature. Verification is possible on any copy, anywhere it appears. The signing identity in the payload identifies the original publisher. When AI-generated text reproduces marked content verbatim, the embedded signature travels with it, linking the output back to the original publisher.
Side-by-Side Comparison
| Feature | Encypher | WordProof |
|---|---|---|
| Proof location | Embedded in content (travels with text) | External blockchain record (stays behind) |
| Proof type | Ownership + identity + licensing terms | Existence + timestamp only |
| Survives copy-paste | Yes (invisible chars in the text) | No (hash is separate from text) |
| Machine-readable licensing | Yes (Bronze/Silver/Gold tiers embedded) | No |
| Works during AI scraping | Yes (markers present in scraped text) | No (blockchain not queried at scrape time) |
| Publisher identity | Cryptographically signed, in the content | Associated with hash in external record |
| Verification without lookup | Yes (signature in the text itself) | No (requires blockchain query) |
| Blockchain dependency | None | Requires accessible blockchain |
| Tamper detection | Yes (hash mismatch detects modification) | Yes (hash mismatch detects modification) |
| Priority dispute evidence | Yes (signed timestamp embedded) | Yes (blockchain timestamp) |
| CMS integration | API + WordPress plugin + SDK | WordPress plugin (primary) |
| Formal notice capability | Yes (willful infringement trigger) | No |
Use Case Fit
Choose WordProof when...
- The primary need is a public, auditable timestamp for priority disputes
- You are a WordPress publisher looking for low-friction adoption
- Blockchain-anchored evidence fits your legal or compliance requirements
- You want Schema.org timestamp data for SEO freshness signals
Choose Encypher when...
- You need proof that travels with your content into AI training pipelines
- Machine-readable licensing terms must be embedded in every copy
- You are building an enforcement case for AI copyright use
- Your content is syndicated widely and you need tracking across channels
- You want formal notice capability against willful infringement
Frequently Asked Questions
What does WordProof do?
WordProof timestamps content by hashing it and recording the hash on a blockchain. This creates an external record proving that a specific version of content existed at a specific time. It integrates with WordPress and other CMS platforms to automate this process at publication.
What is the difference between timestamping and provenance?
Timestamping proves that a specific version of content existed at a point in time - useful for establishing priority in disputes. Provenance proves ownership and carries that proof with the content wherever it travels. A timestamp is an external record you have to look up. Provenance is embedded in the content itself. When text is copied, scraped, or syndicated, the timestamp stays behind. The provenance travels with it.
Why does it matter that the proof is external vs embedded?
External proof requires a lookup. You have the content, you look up the blockchain record, you see if there is a match. This works when you have both pieces. When an AI scrapes your content and uses it without attribution, you typically only have the output - not a provenance link back to the original. Embedded proof travels with the content. The signing identity, timestamp, and licensing terms are in the text itself, visible during scraping and downstream use.
Does WordProof prevent AI training data use?
No. WordProof's external hash record is not readable by an AI crawler at scrape time. There is no signal in the scraped text indicating licensing terms. Encypher's invisible embedded markers are present in the text itself and can be parsed by any system that reads the text, making licensing terms machine-readable at the point of use.
Are WordProof and Encypher complementary?
They address different aspects of content protection. WordProof provides a public timestamp record on-chain that is useful for establishing priority. Encypher provides ownership proof that travels with the content. A publisher could use both: WordProof for the public, auditable timestamp record and Encypher for the embedded provenance that works during downstream distribution.
Sign your archive, free
The free tier signs 1,000 documents per month. Embed ownership proof before your next article goes out.