Every feed, every change, immutably timestamped.
Every 5 minutes, the snapshotter Lambda captures the state of all live JustHodl feeds and writes any changes to a DynamoDB time-series table with 365-day TTL. This page indexes that history — what feeds exist, when they last changed, and how many distinct snapshots have been recorded. The institutional "what did the system show at <timestamp>?" query.
Why this exists
For an institutional reader, the question "did the system actually call this regime change before the move?" is only credible if there's a verifiable record of what the system showed when. This is that record. Every feed at every 5-min tick is hashed and only changes are persisted (so a feed that updates daily takes ~365 rows over a year, not 105k).
Storage: DynamoDB justhodl-history · 365d TTL · pk=feed#<key> · sk=ISO8601 timestamp · content stored gzipped if >100KB · oversize bodies archived to S3 with pointer in DDB.
Feeds tracked in the history table
Every feed that has at least one snapshot. Click a row to see its recent timestamps. Snapshot count grows over time as feed contents change — feeds with rapid changes (report.json every 5min) accumulate quickly; weekly feeds (calibration snapshots) grow slowly.
| Feed key | Snapshots | First seen | Last change | Latest hash |
|---|---|---|---|---|
| Loading… | ||||
The history table is private (DynamoDB). This page calls a read-only Lambda Function URL (justhodl-history-api, reserved concurrency=5 for rate limiting) to fetch snapshot content. Diff is computed client-side after fetching both snapshots — no server round-trip beyond two /snapshot GETs.