Content provenance

A public, timestamped record of what this website published and when, so anyone can check that a page is the one we published.

How it works

Every day an automated job fetches /okf/manifest.json, which lists the SHA-256 hash of every file in our knowledge bundle: company facts, leadership, products, customer stories and every published guide. It saves the manifest and what changed to a public GitHub ledger, timestamps both files with OpenTimestamps (anchored in the Bitcoin blockchain), and submits changed pages to the Internet Archive.

Latest run

  • Date: 2026-10-06
  • Files recorded: 151 (151 changed since the previous run)
  • Spot-check mismatches between served bytes and manifest: 0
  • Proofs still waiting for Bitcoin confirmation: 0
  • Pages archived this run: 1, still queued: 150

Verify a page yourself

  1. Hash the page as served today: curl -s https://www.locafy.com/okf/company/locafy.md | shasum -a 256
  2. Find that hash in the ledger to see when it was first recorded.
  3. Install the client (pip install opentimestamps-client) and run ots verify on that day’s .ots proof.

A proof reads “Pending confirmation” for a few hours until it is committed to a Bitcoin block. A file that has been altered fails verification.

What this does and doesn’t prove

It proves that the exact bytes existed no later than the attested time and were served at the recorded URL. It doesn’t prove that the content is true, who wrote it, or legal ownership. The hashes are unsigned: anyone can recompute them from the public URLs. More about these files: AI info.