Public checklists → sealed timestamps → SHA-256 hashing. Proof buyers (and auditors) can verify independently.
HOW IT WORKS
Transparency you can prove — not “trust.”
We publish the checklist before the show, seal it with a timestamp + SHA-256, and keep the originals public forever.
1
PUBLISH
Public checklists
Every series checklist is posted before any show goes live.
2
SEAL
Timestamp + SHA-256
We freeze the file with a local timestamp and cryptographic hash.
3
VERIFY
Independent audit
Anyone can compute SHA-256 and compare it to our published value.
4
FOREVER
Public after the break
Same links before & after. Originals remain online for audit.
RESULT
If a single character changes, the hash changes.
That’s how you know it’s identical.
EXAMPLE
What we publish (example batch)
Timestamped + hashed + linked.
| Field | Value / Link |
|---|---|
| Series / Batch | Series 45 — Batch 10001 |
| sealed_at | Oct 2, 2025, 2:00 PM PT |
| json_url | GitHub JSON |
| csv_url | Published CSV (Google Sheets) |
| sha256 | 7223e607b4ab4af72b31a97a19603e862e9352c5e8da77cf11e71afe1abefb28 |
Sample entry for illustration. Live batches link to the actual sealed files.
VERIFY
Independent verification (for auditors)
Download → hash → compare.
macOS / Linux
curl -L -o checklist.csv "https://…/checklist.csv" shasum -a 256 checklist.csv
Windows
Get-FileHash .\checklist.csv -Algorithm SHA256 certutil -hashfile checklist.csv SHA256
Pass / Fail
Match = identical file.
If your computed hash matches the published sha256, the checklist is exactly what we sealed.
PUBLIC PROOF
Scan → checklist → trust
Transparency is built in. The room feels it immediately.