Orphograph
For Writers · Draft Chain
Est. 2026
Paste each version of your draft as you write. Only the Merkle root of the chain leaves your browser.
Paste a version. Add it. Paste the next. When you're done, anchor the chain.
SHA-256 and SHA-512.Paste a saved manifest, or drop the JSON file. The browser recomputes the Merkle root from the version hashes and compares it to the receipt.
A description of observable behavior. No promises of what cannot happen — only an account of what does.
Each pasted version is hashed in your browser via the Web Crypto API. The list of hashes is held in this tab's memory and in this browser's localStorage. No version of the draft is sent to the office.
When you anchor, the version hashes are combined into a single Merkle root — a 32-byte number. The root is submitted to five independent OpenTimestamps calendars. Within roughly an hour, it is committed inside a Bitcoin block.
The downloadable session manifest contains every version hash, the Merkle root, and the receipt identifier. Anyone with the manifest can re-derive the root and verify it against Bitcoin using open-source tools, without contacting this server.
Evidence of process, not proof of authorship. A receipt shows that a sequence of text states existed in a particular order, on or before a Bitcoin block. It does not, by itself, identify the human who typed.
A scripted typist could simulate a drafting cadence. The instrument records what it is given; it does not adjudicate intent. The artifact is corroborating evidence, not a verdict.
Not legal evidence absent expert testimony. Admissibility in any proceeding is determined by counsel and the relevant court — not by this office. Not a substitute for retained counsel where stakes are material.
Free tier resets every twenty-four hours by the server's clock. The paid Pack uses the same calendars and the same chain.
For trying it out and for light use, perpetual.
Ten anchored sessions. Credits never expire.
One Merkle root per anchor — a 32-byte (64-hex-character) SHA-256 output — together with its SHA-512 sibling and a static label. No draft text, no version hashes, no filenames.
In this browser's localStorage, keyed by a random 16-character session identifier. They are not synced anywhere. Clearing browser data removes them. If you want a permanent copy, download the session manifest after anchoring.
That the Merkle root of your chain of version hashes existed on or before a specific Bitcoin block. By construction, that fixes the order and content of every version included in the root before that block. It is corroborating evidence of a drafting process. It is not, on its own, identification of the author.
The downloaded session manifest plus the .ots proof files (available from the receipt page) verify offline against the public Bitcoin blockchain using the open-source OpenTimestamps client. No Orphograph server is in the loop.
Ask for their session manifest (a small JSON file). Paste it into the verify box above, or drop the file. The browser will recompute the Merkle root from the listed version hashes and compare it to the root recorded in the receipt. To go further, fetch the .ots proofs from the receipt page and run them through the OpenTimestamps client against Bitcoin.
A single anchor of a finished draft proves only that the finished draft existed. A chain of version hashes records the order in which intermediate states existed — an account of editing over time. The Merkle root commits to all of it at once, with one transaction's worth of footprint.
It may or may not. Admissibility depends on jurisdiction, counsel, opposing counsel, and the trier of fact. Treat the artifact as one piece of corroborating evidence, not a verdict, and consult an attorney where stakes are real.