Tamper-proof notes

Why it matters

A note you can silently edit is a note nobody else has to believe. The moment your writing might be evidence — an AI agent's session log, a cron job's output, a research trail, a decision record, a dated idea — "it says so in my notes" is only as good as your ability to show it was not back-dated or quietly rewritten later.

Notarization closes that gap. Each hashed event is anchored into Bitcoin, so its existence at that time becomes a public, permanent fact that neither you nor we can change after the fact. When it counts, you hand someone the proof and they check it themselves — no account, no trust in us, and no way for anyone to have tampered with it in between.

Proof of work, for AI-assisted billing

When you bill a client for AI-assisted work, "trust me, I did this" is a weak position in a dispute. Stream your Claude Code — or any agent's — session logs into an append-only note, and each entry is hashed the moment we receive it and folded into that day's Bitcoin anchor. If the work is ever questioned, you hand over the proof and the other side checks it themselves — no account, and no need to trust you or us.

What that establishes — to a client, an arbitrator, or a court — is real, independent evidence: the session's content existed by that date, its entries are in their original, unbroken order, and none of it was fabricated or back-dated afterward, because you cannot anchor to a Bitcoin block that had not been mined yet. That is exactly the point a "you made this up later" dispute turns on.

One limit, stated plainly so you use it well: the Bitcoin anchor is daily, so it proves a session existed by a given day — not a to-the-minute tally of hours. Stream as you work, or upload the same day; a transcript uploaded three weeks late only proves it existed three weeks late. Used that way, it is genuine proof that the work is yours and happened when you say it did.

How it works

• Every event is hashed. An append-only note (a log) is hashed entry by entry as each arrives, each hash chained to the note's previous one — an append-only ledger for that note. A note you edit — rich or plain — gets a once-a-day snapshot of its content on each day it changed, instead of an impossible per-keystroke hash.
• Each day is committed to Bitcoin. Once a day, every account's new hashes are folded into one Merkle tree and its root is anchored to the Bitcoin blockchain via OpenTimestamps — a single, free timestamp covering everyone.
• Anyone can verify it, offline. Each note ships a self-contained proof: the exact bytes, the hash chain, the Merkle path, and the Bitcoin timestamp. Check it with standard tools; nothing in that check involves us.
• We are inside the guarantee, not above it. A Bitcoin commitment cannot be rewritten after the fact — not by an attacker, not by a subpoena, not by Fresh Jots. That is the whole point.

What it proves — and what it doesn't

It proves "this exact content existed by time T and has not been altered since." That is precisely the audit-log guarantee: nobody can go back and change what a log said, or when it said it.

It does not prove the content is true, or that it was not doctored before we hashed it — if something was altered on the way in, the anchor faithfully notarizes the altered version. And it composes with encryption: hashing needs no plaintext, so an encrypted note can be notarized without us ever reading a byte.

See it, and check it

• Your proofs. The Provenance dashboard lists each of your notes, how many of its events are Bitcoin-confirmed, and a one-click proof download. (Available on the Dev and Team plans.)
• Verify one yourself. The step-by-step verification guide shows how to check a proof against Bitcoin with standard tools, trusting no one — including us.

Availability

Notarization covers every note. An append-only log's creation and each append are hashed as they arrive — exactly the shape of an AI-session stream (you'll find plain notes in Code mode). Notes you edit, rich or plain, are notarized too: once a day we snapshot each one that changed, since a note you edit continuously can't be hashed on every keystroke. The Provenance dashboard and proof downloads are part of the Dev and Team plans.