Receipts > Vibes: A Public Proof Stamp for Blog Posts (and a One-Click Verifier)

Most sites beg for trust with a footer slogan. We stamp it.

Every time we publish or update a post, we:

• Canonicalize the content to plain text

• Hash it (SHA-256)

• Append that hash to a public GitHub ledger (JSONL)

• Show the Proof on the page with a link to the exact commit

If we change the words later, the hash breaks. That’s the point.

---

Why we did it

AI makes content cheap. It also makes doubt cheap. We don’t argue in comments about “authenticity.” We ship receipts:

• Third-party timestamp (Git/GitHub)

• Immutable history (commit log)

• Verifiable now (rehash the live page and compare)

No permission from Google. No magic blockchain incantations. Just public logs.

---

Try the verifier

We published a tiny Verify page: paste a VibeAxis URL, and it will:

1. Re-hash the live page (now)

2. Compare it to our stored stamp

3. Compare it (if present) to the GitHub ledger

Green = match. Red = something changed. The Proof link points to the exact commit.

👉 Live example: https://vibeaxis.com/verify

---

How to do this on your site

We open-sourced a minimal WordPress plugin: VAX Proof Stamp

• Hash on publish/update

• Append one JSON line to a public GitHub repo

• Shortcode [vax_proof] renders the stamp

Repo: https://github.com/VibeAxis/vax-proof-stamp
(Yes, the plugin’s own README is stamped. We eat our dog food.)

---

“Why not blockchain?”

Because Git already gives you the three things you actually need:

1. Public (anyone can see it)

2. Append-only (history is the product)

3. Portable (clone it anywhere)

If you want a blockchain anchor later, mirror monthly digests to OpenTimestamps. Not required for trust; just extra theater.

---

The bigger take

“Content” isn’t scarce. Confidence is. If you publish anything you expect humans to care about, stop asking for trust—prove it.

Receipts > vibes.