Shipping daily
Changelog →

Kolaboro / Open data / Daily dataset snapshots

Daily dataset snapshots

Every day the project dataset is published, its exact bytes get a SHA-256 fingerprint. Each day's entry includes the previous entry, so changing any past day afterwards would break every entry after it. A copy of each day's file is kept here, so anyone can check it.

Check it in your browser


Nothing is uploaded: the file is hashed on this device.

DayProjectsSizeSHA-256 of the fileEntry headCopy
18 Nov 2026 (provisional tip)7.13 MB8625769cbba8…2f34b1bb24e4…named.json
17 Nov 20261,7455.3 MB4f2af79bff82…4daf5607fe66….gz 1.09 MB
15 Nov 20261,5955.03 MBdba30f19f959…79765ee63139….gz 1.06 MB
13 Nov 20261,5955.03 MB7acc1dfebfff…9345c845c93c….gz 1.06 MB
12 Nov 20261,5954.68 MB48669c97d332…014459c8e0ca….gz 1.02 MB
11 Nov 20261,1743.98 MB7473d728f81a…d0a15a4a57f4….gz 0.92 MB
9 Nov 20261,1243.9 MB36e35f34f564…8f152f37e321….gz 0.91 MB
7 Nov 20261,1243.9 MB2dcfb2d68311…01d6d090f7ac….gz 0.91 MB

Entries up to 16 Nov 2026 were rebuilt on 17 Nov 2026 from the version history of the published file.

Check it without us

Download a copy, unzip it and compare its SHA-256 with the table. Then recompute each head with the rule below; the first entry uses "genesis".

Rule

head = SHA-256 hex of the UTF-8 text "kolaboro-snapshot-v1|" + day + "|/data/named.json|" + sha256 + "|" + bytes + "|" + prev, where prev is the head of the entry before (the first entry uses "genesis")

curl -sO https://kolaboro.com/data/snapshots/2026-11-17/named.json.gz
gunzip -c named.json.gz | sha256sum
printf '%s' "kolaboro-snapshot-v1|DAY|/data/named.json|SHA256|BYTES|PREV" | sha256sum

The public log, which fixes the open dataset every day with a Bitcoin timestamp, is at /log/. The API answer of this page is /api/v1/snapshots. API v1 · Data quality

Protect my purchase