Hivemapper (HONEY) — the revision ledger

Generated 2026-09-02T19:23:23Z from live ClickHouse queries against this estate's ledger. Point-in-time archive held for Hivemapper: 8,371 observations · 47 distinct series · 5 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-09-02 18:58:01 · every one of the 8,371 rows carries a verify_url · 38 series refreshed in the last 24h (767 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where Hivemapper's archive comes from

5 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 — 545 rows over 27 snapshots (2026-08-06 → 2026-09-01) — 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 (75 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.

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.

Gauges that moved backward — deliberately NOT revisions

These series fall outside the detector's cumulative-by-construction class (NOT_TRULY_CUMULATIVE and plain gauges in propintel/revision_ledger.py): a drop there is a real population or market change, not upstream rewriting history. Publishing them as "revisions" would be exactly the fake-metric behaviour this product exists to eliminate. HONEY's archive holds 14 such series that oscillated across the snapshot window — prices, market cap, supply figures, rolling fee windows and market-cap rank.

Same-timestamp conflicting values on record for HONEY: none

The task-level conflict check, run live: any (metric, timestamp) family where this estate recorded two or more different values. The query ran at generation and returned 0 groups in both depin_onchain and depin_daily — every (metric, timestamp) pair the estate holds for HONEY carries exactly one value. Zero here is the live query result, not a gap; the archive kept every write it made, and none of them disagree.

The ledger, live — every restatement recorded estate-wide (18 deduped events)

Deduped on revision identity exactly as /v1/revisions dedupes it. This is the same feed a subscriber polls; it is rendered live from ClickHouse at generation, not copied from a snapshot. Each row is an upstream source replacing the value of a (network, metric, date) it had already published — after this estate recorded the original. The superseded value is retained, never deleted; that retention is the only reason a rewrite is detectable, and it is the part every overwriting vendor discards. Note the GRT rows: fees_alltime_usd restated for The Graph by the same DefiLlama upstream that feeds HONEY's clean trail.

How detection works — and what it cannot see

The detector (propintel/revision_ledger.py) diffs every daily snapshot this estate holds of every cumulative-by-construction series — counters that cannot decrease unless upstream rewrote them (block heights, transaction and transfer counters, lifetime fees). A row enters default.depin_revision_ledger iff two snapshots disagree for an already-observed date; zero human judgement. Resolution rule: latest observation wins for current-state reads, the superseded value is retained, never deleted. Population gauges (provider sets, node counts, prices, capacity) legitimately move both ways and are deliberately excluded — a drop there is a real population change, not a rewrite; the gauge table on this page is the worked example. Honest boundary: this catches value-history rewrites ex-post; identical-schema semantic drift with plausible values is what the hash-pinned derivation_replay layer is for. The detector's full classification is inspectable at /v1/revisions and frozen daily at /revision-ledger/REVISIONS_20260902.json.

Estate grades for HONEY (graded 2026-08-20 13:54:15.000)

Served by /v1/network/HONEY — the same grades a paying agent receives. Scores are the engines' own 0–100 outputs, published exactly as the engines emitted them, unflattering parts included.

Verify any cell yourself — the exact commands

No account, no key, no trust required. Commands 1–2 hit this estate's public API (the same rows this page queried — every row carries source / as_of / verify_url); commands 3–5 hit the upstream families the network-side rows came from; command 6 is the estate's graded network row; command 7 is the frozen daily snapshot of the ledger. One polite call per endpoint, no hammering.

# 1) The served revision feed for HONEY — the same rows this page queried, live:
curl -s "https://kairossignal.com/v1/revisions?symbol=HONEY" | python3 -m json.tool
# 2) The estate-wide feed (every network, both sides of every diff):
curl -s "https://kairossignal.com/v1/revisions" | python3 -m json.tool | head -80
# 3) DefiLlama's fees API for Hivemapper (the watched counter's origin — fees_alltime_usd):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/summary/fees/hivemapper" | python3 -m json.tool | head -40
# 4) Hivemapper's own explorer API (the first_party_api upstream):
curl -s -H "User-Agent: kairos-check" "https://beemaps.com/api/explorer" | python3 -m json.tool | head -30
# 5) GitHub API for Hivemapper/hivemapper-data-logger (the dev-velocity upstream family):
curl -s -H "User-Agent: kairos-check" "https://api.github.com/repos/Hivemapper/hivemapper-data-logger" | python3 -m json.tool | head -30
# 6) This estate's public API row for HONEY (grades + provenance):
curl -s "https://kairossignal.com/v1/network/HONEY" | python3 -m json.tool | head -60
# 7) The public daily snapshot of the ledger (frozen copy):
curl -s -o /dev/null -w "%{http_code}\n" "https://kairossignal.com/revision-ledger/REVISIONS_20260902.json"

Method & honesty notes. All counts are queries against the live ledger at generation time, not restamped copy — this page is regenerated by gen_revision_page_honey.py and the hourly claim_drift_check.py run grades its claims against the live API like every other published surface. The HONEY revision count is the live result of SELECT count() FROM default.depin_revision_ledger WHERE network='HONEY'; the page refuses to ship if the served /v1/revisions?symbol=HONEY disagrees with it. The 18 estate-wide events shown are deduped on revision identity (deterministic hash of network, metric, current_date, prior_date) exactly as the API dedupes them; detected_at is the first detection and never moves. Series absent from a section are absent, not zero: the daily-snapshot ledger for HONEY is genuinely empty today — because the one watched counter the archive holds proved monotonic under the detector's diff, a measured negative published as found, with the full trail rendered above — and this page says so instead of inventing restatements. The same-stamp conflict check is likewise the honest live answer: 0 groups in depin_onchain and 0 in depin_daily. The first-party explorer capture is a single snapshot held since 2026-08-09 and is labelled as such on the page. Upstream probes ran serially by this generator immediately before rendering: api.llama.fi /summary/fees/hivemapper HTTP 200; beemaps.com/api/explorer HTTP 200; GitHub API Hivemapper/hivemapper-data-logger HTTP 200; CoinGecko Hivemapper page HTTP 403; estate /v1/revisions?symbol=HONEY HTTP 200; estate /v1/network/HONEY HTTP 200.