For listing agents and brokers
One receipt covers a whole listing date. Show one photo later without showing the rest.
A listing's photographic record on a chosen date is sealed together in one step. Any single image can be proven part of that set on any future date.
What this means for you
- Photo bytes are hashed on your device rather than uploaded; the manifest sent for anchoring contains relative paths, file digests, sizes, and the root.
- One receipt covers the listing as of the chosen anchor date.
- Show one photo later without showing the rest.
How it works
Each image gets a fingerprint — a 64-character code that changes if a single byte of the file changes. The fingerprints are computed on your own machine; the files themselves are not uploaded.
The fingerprints and relative paths are combined into one fingerprint for the whole folder. The anchoring request includes the manifest metadata and root, but not the photo bytes.
The combined fingerprint is anchored to the Bitcoin chain. Anyone, on any future date, can confirm the folder existed by the moment of that block — and that a single image was part of it — without ever seeing the other photos.
For the technically curious
Show the cryptographic detail
The natural unit is one folder per anchor point in the listing's life — the listing-walk folder, anchored at the moment the listing goes active; the inspection-day folder, anchored at the moment of contract; the closing-day folder, anchored at recordation. The MLS photo set is the typical core; the agent's full walkthrough is the typical superset.
The desktop or browser tool computes a SHA-256 fingerprint of each image, binds the relative path into a leaf hash, and assembles the leaves into a Merkle tree whose root is submitted to the OpenTimestamps calendars. The images themselves never leave the device. Successive anchor points within a single listing produce successive anchored folders.
Eight months after closing, the buyer alleges that the basement showed a water stain at listing time. The agent produces an inclusion proof for the four basement photographs in the listing-walk folder anchored on the day the listing went active. Other rooms in the seller's house, and the agent's other active listings on the same day, are not exposed by the proof. The receipt does not establish that the property was free of defects; it establishes that the disclosed photographs, under the recorded relative paths, were part of the anchored listing-walk set as of the recorded Bitcoin block.
The folder receipt records the Merkle root, per-leaf relative paths, SHA-256 digests, byte sizes, and available OpenTimestamps attestations. The root commits to each relative path and file digest; the byte sizes are recorded beside them but are not part of what the root commits to. An optional valid did:key signature can show that the corresponding private key signed the manifest. Orphograph does not establish who controls that key, validate a real-estate license, or certify that the signer is the listing agent.
Questions
Where do my listing photos go?
The photo bytes remain on your machine. The service receives the folder manifest metadata and root, including literal relative paths, so use non-sensitive filenames or renamed copies where path disclosure matters.
Does this cure a defective disclosure form?
No. The receipt records that a particular set of images existed by the time of the recorded Bitcoin block. The disclosure form itself remains the responsibility of the agent and counsel.
Can I anchor multiple dates in one listing's life?
Yes. A separate folder may be anchored at any anchor point — listing-walk, inspection day, closing day, or any other date the agent and counsel choose. Each receives its own root and its own Bitcoin attestation.
Will this integrate with my MLS feed?
The receipt is independent of any MLS data feed. The agent anchors whichever folder represents the listing's photographic state at the chosen anchor point; the receipt is portable and travels with the listing.
Orphograph anchors evidence of existence; it does not certify authorship, ownership, or legality. Each user retains responsibility for the underlying files, their consent to capture, and their handling under applicable law. The office is not a law firm, not a regulated medical-records system, not a qualified electronic trust service, and not a legal or financial advisor. No claim of compliance with any state's real-estate-disclosure statute is asserted; independent counsel review is required before any productized claim of disclosure-litigation utility.