Hivemapper (HONEY) — the revision ledger

Generated 2026-10-17T05:26:30Z from live ClickHouse queries against this estate's ledger. Point-in-time archive held for Hivemapper: 39,092 observations · 62 distinct series · 7 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-10-17 04:58:01 · every one of the 39,092 rows carries a verify_url · 54 series refreshed in the last 24h (785 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where Hivemapper's archive comes from

7 source families feed this network's ledger. Every row they wrote carries its own source, as_of and verify_url; this table is the live rollup of that. Hivemapper's market series come from CoinGecko, its protocol fees from DefiLlama /overview/fees (the same upstream whose restatement the detector caught for GRT — see the estate-wide ledger below), token supply and holder concentration from the Solana chain via solana_rpc, developer activity from the Hivemapper data-logger repository on GitHub, and a single point-in-time capture from Hivemapper's own explorer API (beemaps.com — active regions, contributors, events, km mapped; one snapshot, 2026-08-09). The token mint held for HONEY is 4vMsoUT2BWatFweudnQM1xedRLfJgJ7hswhcpz4xgBTy on Solana.

Revision ledger — 0 backward revision(s) recorded for HONEY

The ledger query ran during generation and returned 0 rows for HONEY — and HONEY's zero is a measured negative: the daily archive this estate holds for HONEY — 2381 rows over 72 snapshots (2026-08-06 → 2026-10-16) — contains one cumulative-class series the detector watches, every snapshot pair of it was diffed, and the trail is monotonic. A real counter was watched; it was not rewritten. Where sibling networks show restatements — AR's BLOCKS (1,980,116 → 1,702,204) and, pointedly, GRT's fees_alltime_usd (1,424,316 → 1,423,345), the SAME metric family from the SAME upstream that HONEY's watched counter comes from — HONEY's watched counter shows nothing of the kind. Zero here is the live query result plus the measured trail below, not a gap — the ledger itself is at /v1/revisions?symbol=HONEY (the same query this page ran, served live), and a restatement would appear on this page the day the detector records one. /v1/revisions?symbol=HONEY cross-check passed: the served API reports 0 row(s), matching the ledger count rendered on this page.

What the detector watches for Hivemapper — the intersection, measured

The detector diffs every daily snapshot of every cumulative-by-construction series. Below is the live intersection of the estate detector's cumulative watchlist — imported directly from propintel/revision_ledger.py (11 declared names, so this page can never drift from the detector) — with what the daily archive holds for HONEY. One watched series is held and was fully diffed; it produced no backward pair. That is the structural content of the zero above: a watchable counter exists, and it is clean.

Live query result: 0 watchlist series held for HONEY. The intersection query ran during generation and returned an empty set — none of the 11 cumulative-by-construction metric families the detector watches appear in HONEY's daily archive. This is the structural zero behind the ledger count above, published as the query found it.

The trail behind the zero — the watched counter, end to end

This is the actual counter trail the detector diffed for HONEY, rendered live from the archive. It is a series that cannot decrease unless upstream rewrote history — which is exactly what makes its smooth monotonicity the proof behind the zero, and the same trail where a GRT-style restatement would appear if it ever happened. It is the DefiLlama all-time cumulative protocol-fee counter for Hivemapper (source DefiLlama /overview/fees): ten snapshots, two small upward ticks (601,956.99 → 601,957.00 → 601,957.25 USD), never once backward. GRT's counterpart series from this same upstream WAS restated — see the estate-wide ledger below; the contrast between the two trails is the product.

fees_alltime_usd — the Hivemapper all-time cumulative protocol-fee counter (USD):

The first-party capture — Hivemapper's own explorer API

The estate also holds a direct pull from beemaps.com/api/explorer — Hivemapper's own public explorer (source first_party_api): a single point-in-time snapshot from 2026-08-09 23:53:15, kept exactly as captured. Six counters, each with its own verify URL back to the explorer. These are network-scale gauges (regions, contributors, cumulative events and km mapped) — they belong to the gauge class the detector deliberately excludes, and with a single snapshot held there is no pair to diff; they are published here as the point-in-time capture the estate retains, not as a series.