<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Orphograph — Blog</title>
    <link>https://orphograph.com/blog/</link>
    <atom:link href="https://orphograph.com/blog/rss.xml" rel="self" type="application/rss+xml"/>
    <description>Notes from the office. Method, doctrine, and edge cases of Bitcoin-anchored timestamps.</description>
    <language>en-us</language>
    <copyright>© 2026 Orphograph</copyright>
    <managingEditor>hello@orphograph.com (Orphograph)</managingEditor>
    <lastBuildDate>Thu, 21 May 2026 00:00:00 +0000</lastBuildDate>
    <item>
      <title>How to date-stamp a document permanently</title>
      <link>https://orphograph.com/blog/date-stamp-a-document-permanently.html</link>
      <guid isPermaLink="true">https://orphograph.com/blog/date-stamp-a-document-permanently.html</guid>
      <description>A plain-English guide to placing a permanent, third-party-verifiable date on a digital document — using a cryptographic fingerprint anchored to the Bitcoin chain, with no expiry and no trusted intermediary.</description>
      <pubDate>Thu, 21 May 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>How to prove a contract existed before a date</title>
      <link>https://orphograph.com/blog/prove-a-contract-existed-before-a-date.html</link>
      <guid isPermaLink="true">https://orphograph.com/blog/prove-a-contract-existed-before-a-date.html</guid>
      <description>A plain-English method for proving that a signed or unsigned contract existed in its present form before a specific calendar date. Anchor the document's cryptographic fingerprint to the Bitcoin chain and hold a third-party-verifiable date of record.</description>
      <pubDate>Thu, 21 May 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>How to prove a photo was not edited</title>
      <link>https://orphograph.com/blog/prove-a-photo-was-not-edited.html</link>
      <guid isPermaLink="true">https://orphograph.com/blog/prove-a-photo-was-not-edited.html</guid>
      <description>A plain-English guide to proving a photograph has not been edited since a specific moment, using a cryptographic fingerprint anchored to the Bitcoin chain. Verifiable by anyone, with no trusted intermediary.</description>
      <pubDate>Thu, 21 May 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>How to prove a piece of code existed before a competitor's commit</title>
      <link>https://orphograph.com/blog/prove-code-existed-before-a-competitors-commit.html</link>
      <guid isPermaLink="true">https://orphograph.com/blog/prove-code-existed-before-a-competitors-commit.html</guid>
      <description>A practical guide for engineers and engineering organisations: anchor a source tree's cryptographic fingerprint to the Bitcoin chain so a defensible date of record fixes the bytes before any competing commit. From the Orphograph office.</description>
      <pubDate>Thu, 21 May 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>How to prove you created something before someone else</title>
      <link>https://orphograph.com/blog/prove-i-created-something-before-someone-else.html</link>
      <guid isPermaLink="true">https://orphograph.com/blog/prove-i-created-something-before-someone-else.html</guid>
      <description>A plain-English method for establishing priority of creation — proving a draft, sketch, manuscript, or design existed in your hands before someone else's competing claim. Bitcoin-anchored, third-party-verifiable, permanent.</description>
      <pubDate>Thu, 21 May 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>How to prove you wrote it — not an AI</title>
      <link>https://orphograph.com/blog/prove-you-wrote-it-not-ai.html</link>
      <guid isPermaLink="true">https://orphograph.com/blog/prove-you-wrote-it-not-ai.html</guid>
      <description>A practical guide for writers, students, and journalists accused of using AI to produce text. Save the file, anchor its fingerprint to the Bitcoin chain, hold a verifiable date of record that pre-dates the accusation.</description>
      <pubDate>Thu, 21 May 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>What makes a digital timestamp legally defensible</title>
      <link>https://orphograph.com/blog/what-makes-a-digital-timestamp-legally-defensible.html</link>
      <guid isPermaLink="true">https://orphograph.com/blog/what-makes-a-digital-timestamp-legally-defensible.html</guid>
      <description>An institutional explainer of the properties that make a digital timestamp hold up under examination — independent verification, cryptographic binding, public anchoring, and continuity beyond the issuer. From the Orphograph office.</description>
      <pubDate>Thu, 21 May 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Why a Bitcoin block height is the strongest proof of existence in 2026</title>
      <link>https://orphograph.com/blog/bitcoin-block-height-as-source-of-truth.html</link>
      <guid isPermaLink="true">https://orphograph.com/blog/bitcoin-block-height-as-source-of-truth.html</guid>
      <description>Why a Bitcoin block height is the strongest existence-proof anchor in 2026. Sixteen-year track record, attack costs, what would have to fail.</description>
      <pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>How Bitcoin merkle roots make file timestamps un-falsifiable</title>
      <link>https://orphograph.com/blog/bitcoin-merkle-roots-unforgeable-timestamps.html</link>
      <guid isPermaLink="true">https://orphograph.com/blog/bitcoin-merkle-roots-unforgeable-timestamps.html</guid>
      <description>A technical walkthrough of why a timestamp anchored to Bitcoin is fundamentally different from a conventional database record. The math, the eight attacks an adversary would have to mount, and why each one fails in practice.</description>
      <pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Digital notary vs cryptographic timestamp — what each one proves</title>
      <link>https://orphograph.com/blog/digital-notary-vs-cryptographic-timestamp.html</link>
      <guid isPermaLink="true">https://orphograph.com/blog/digital-notary-vs-cryptographic-timestamp.html</guid>
      <description>Digital notary vs cryptographic timestamp — what each actually proves, why they are not interchangeable, and which one your use case needs.</description>
      <pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>How to prove a photo existed before an AI model was released</title>
      <link>https://orphograph.com/blog/how-to-prove-photo-existed-before-ai-model-released.html</link>
      <guid isPermaLink="true">https://orphograph.com/blog/how-to-prove-photo-existed-before-ai-model-released.html</guid>
      <description>Step-by-step walkthrough to prove a photo existed before AI training. Bitcoin-anchored timestamp, free tier, ten-minute setup.</description>
      <pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>OpenTimestamps for non-developers — a 10-minute walkthrough</title>
      <link>https://orphograph.com/blog/opentimestamps-for-non-developers.html</link>
      <guid isPermaLink="true">https://orphograph.com/blog/opentimestamps-for-non-developers.html</guid>
      <description>A practical explainer of what OpenTimestamps is, why it works, and how to use it without opening a terminal. Bitcoin-anchored proof of existence, with no per-record cost.</description>
      <pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>How to prove your photo existed before AI scraped it (without a lawyer)</title>
      <link>https://orphograph.com/blog/prove-photo-existed-before-ai.html</link>
      <guid isPermaLink="true">https://orphograph.com/blog/prove-photo-existed-before-ai.html</guid>
      <description>A practical guide for photographers who want timestamp-grade proof of when they made an image. Bitcoin-anchored timestamps, free tier, ten-second workflow.</description>
      <pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Reading an .ots file by hand — a forensic walkthrough</title>
      <link>https://orphograph.com/blog/reading-ots-file-by-hand.html</link>
      <guid isPermaLink="true">https://orphograph.com/blog/reading-ots-file-by-hand.html</guid>
      <description>A byte-by-byte walkthrough of what is actually inside an OpenTimestamps proof file. For investigators, journalists verifying a tip, and anyone who wants to confirm the math is real.</description>
      <pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Why Orphograph uses five OpenTimestamps calendars instead of one</title>
      <link>https://orphograph.com/blog/why-5-opentimestamps-calendars-not-1.html</link>
      <guid isPermaLink="true">https://orphograph.com/blog/why-5-opentimestamps-calendars-not-1.html</guid>
      <description>Why submitting to five OpenTimestamps calendars instead of one matters — independent operators, no single point of failure, receipt survives outages.</description>
      <pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate>
    </item>
    <item>
      <title>Why your domain dying shouldn&amp;#x27;t kill your timestamp receipt</title>
      <link>https://orphograph.com/blog/why-domain-dying-doesnt-kill-your-timestamp.html</link>
      <guid isPermaLink="true">https://orphograph.com/blog/why-domain-dying-doesnt-kill-your-timestamp.html</guid>
      <description>Most SaaS receipts are worthless when the company disappears. A Bitcoin-anchored timestamp is structurally different — the proof outlives the issuer by design.</description>
      <pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate>
    </item>
  </channel>
</rss>
