BlindProof¶
A private, verifiable record of how a book actually got written — so authors can prove their manuscript is their own without revealing a single word of it.
BlindProof sits quietly alongside your writing. Every time you save, it notes — privately, on your own computer — that a document of a certain length existed at that moment. Once a day, it takes a summary of those notes to an independent public registrar, which stamps them with the date in a way nobody can forge or alter. Your words never leave your machine.
When the book is ready, you produce a single document — the proof bundle — that your publisher can verify on their own, with a small checking tool that anyone can run. The bundle shows when you worked, how your manuscript grew, and proves that this exact manuscript existed on those dates. Not a different book of similar length. This one, down to the last comma.
Who this documentation is for¶
-
A plain-language guide for anyone writing a book. No technical background needed. Read this if you want to understand what BlindProof does, how to set it up, and what you'll hand your publisher.
-
A technical reference covering the three-layer architecture, the cryptographic primitives, the API, the proof bundle format, and how to run or deploy each layer. Read this if you maintain BlindProof, write verifiers, or want to understand how the evidence is constructed.
The product in one sentence¶
BlindProof produces a signed, timestamped, independently verifiable artifact that a manuscript was written by a human over time — without ever exposing the manuscript's content to the server, the publisher, or any third party.