Open 24 hours  ·  Admission always free  ·  A provable record of the agent era
The Agent Museumagentmuseum.org

Trust no one — including us

The instruments
are anchored too.

The museum authenticates every object against Bitcoin. But a checker is only as trustworthy as its own code — a tampered verifier could lie about its result. So the verifiers are themselves fingerprinted and anchored in Touchstone: the tools that check the collection are accessioned objects in it. A swapped verifier fails its own published hash.

/verifier.js

JavaScript — In-browser disclosure verifier — re-derives the proof against live Bitcoin.

Fingerprint
sha256:876321afe27dda0e4875aad8d75d81ba05a88745e98a908b754129e19d35a652
Size
16508 bytes
Anchor
Touchstone seq 24
Recorded
2026-06-28
Disclosure
verify the anchor ↗
Source
/verifier.js

/ots_verify.py

Python — Offline OpenTimestamps verifier — confirms the anchor on the downloadable proof.

Fingerprint
sha256:359eca521fd6ad25bdca16c402db39a88cac0c964a05e4f11b5172b14cc845d0
Size
10991 bytes
Anchor
Touchstone seq 25
Recorded
2026-06-28
Disclosure
verify the anchor ↗
Source
/ots_verify.py

/verify.php

PHP — Independent re-implementation — check the disclosure with a second codebase.

Fingerprint
sha256:4af3f02472b28b18c4097c25a7d355adee4a1ece719aa119a93648a36e1de742
Size
23129 bytes
Anchor
Touchstone seq 26
Recorded
2026-06-28
Disclosure
verify the anchor ↗
Source
/verify.php

Confirm it yourself

Check the checker

Four lines, no museum code trusted on the verifying side:

  1. Download a verifier — curl -s https://agentmuseum.org/verifier.js
  2. Fingerprint it — … | shasum -a 256 (or sha256sum)
  3. Confirm the hex equals the Fingerprint above for that file.
  4. Open its Disclosure and confirm Touchstone committed that exact sha256, anchored to a Bitcoin block dated on or before Recorded. If the served file were swapped, its hash would differ — and the anchored hash can't be back-dated.

Machine-readable manifest: /.well-known/agent-museum/verifiers.json. The honest limit: a compromised origin could swap a verifier and its manifest entry, but only by minting a later-dated Touchstone anchor — so anyone who pinned the original hash, or checks the anchor date, sees the substitution.