About the office
Orphograph is an empirical notary.
It produces a Bitcoin-anchored receipt that a file existed at a given moment, without the file itself ever leaving your device.
What it actually does
You drop a file in your browser at orphograph.com. The office never receives the file; only a 64-character fingerprint of it. That fingerprint is committed to the Bitcoin chain by the next block.
Months or years later, you can prove the file existed at the recorded time — to a court, an adjuster, an auditor, anyone — without depending on the office. The proof is open-source and the Bitcoin chain is independent.
Folder anchoring (new this week) lets one receipt cover an entire working set, with the option to disclose any single file later without revealing the others.
What it does not do
- Does not claim the file is true.
- Does not claim you are the author.
- Does not store the file.
- Does not require an account for verification.
The details, by audience
For the technically curious
Each file is hashed locally with SHA-256, producing a 32-byte digest. The digest is submitted to the OpenTimestamps protocol, which aggregates submissions into a Merkle tree (per RFC 6962) and commits the tree root to the public Bitcoin chain in a single transaction. The customer receives a small proof file containing the path through the tree to the on-chain root. Verification reconstructs the digest from the file, walks the proof, and checks the root against the Bitcoin block. No service is required at verification time; the chain is the trust anchor.
For the folder case, the customer builds a second-level RFC 6962 tree over the files in a directory and submits only that root. The structure supports per-file inclusion proofs of roughly log₂ N sibling hashes — selective disclosure of any one file without revealing the rest.
For developers
Three install paths, all MIT-licensed:
pip install orphographnpm install orphographOffline verifier kit (single HTML file plus standalone Python script, no network required):
curl -O https://orphograph.com/dist/orphograph-verify.zipMCP server for direct integration with model-context-protocol clients:
orphograph-mcp --stdioFor lawyers, adjusters, auditors
The doctrinal grounding — what an Orphograph receipt does and does not establish under standard rules of evidence, the relationship to authentication and best-evidence doctrine, and the limits of timestamp testimony — is set out in /method/evidence-law.html. The page is itself anchored on publication and is intended as a plain-English reference for counsel reviewing a receipt in connection with a dispute, claim, or audit.
Contact
General correspondence: [email protected].
Security findings, vulnerability reports, and coordinated disclosure: [email protected]. The policy is recorded in /security.html.
Service availability is published at /status.html.
Press resources are at /press.html.
Disclaimer. The office is not a law firm, not a qualified electronic-trust-service provider, and not a financial advisor. The description above is a plain-English summary of the protocol; it is not legal advice and does not establish an attorney–client relationship. The evidentiary weight of a receipt in any particular jurisdiction depends on the rules and statutes of that jurisdiction and on the facts of the matter. A customer with an actual dispute should consult counsel admitted in the relevant jurisdiction.