Trust → Integrity → Verify
Re-hash any snapshot.
Every snapshot Fonteum publishes ships with a SHA-256 attestation. Look up any attested snapshot by its numeric id and you'll get the full envelope: the upstream archive URL, the published content hash, the attested-at timestamp, and (when available) the cached mirror URL on Fonteum's 90-day rolling S3 cache. Re-hash the bytes yourself; the result MUST equal the published hash.
Re-check it yourself
Every snapshot ships with a SHA-256 attestation. Look one up to get its source archive, published hash, and Ed25519 chain head — then re-hash the bytes yourself.
Or run the full flow at /verify · curl /verify/<id>
Or look one up the plain way
How the re-hash flow works
- Look up the snapshot —
GET /verify/<snapshot_id>returns the attestation envelope:content_hash,source_archive_url,cache_url(if mirrored),attested_at, andmethodology_version. - Download the bytes — fetch
source_archive_urlfrom the upstream agency, ORcache_urlfrom the Fonteum 90-day mirror if the upstream URL has rotated. - Re-hash —
shasum -a 256 archive.csv. The result MUST equalcontent_hash. If it doesn't, the bytes were altered (or the source agency rotated their archive without publishing a new snapshot id) — the discrepancy is reportable tocorrections@fonteum.com.