Beamable Network (BMB) — the revision ledger

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

Provenance — where Beamable Network's archive comes from

4 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. Beamable Network does not expose a public first-party stats API and runs on Solana (not an EVM chain — the estate holds no Blockscout or PublicNode rows for it), so BMB's archive is built from four independent families: CoinGecko's market series; DefiLlama's protocol fees under the beamable-network slug (all-time, 30d, 7d, 24h fees and revenue — the all-time counter is the exact series class this ledger watches); DefiLlama's protocol-level TVL and staking rows; and the estate's own solana_rpc collector reading holder concentration and total supply off the BMB mint BMBtwz6LFDJVJd2aZvL5F64fdvWP3RPn4NP5q9Xe15UD.

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

The ledger query ran during generation and returned 0 rows for BMB — and BMB's zero is a measured negative: the daily archive this estate holds for BMB — 456 rows over 24 snapshots (2026-08-09 → 2026-09-01) — contains two cumulative-class all-time fee series the detector watches (DL_FEES_ALLTIME_USD from the estate's own first-party DefiLlama collector and fees_alltime_usd from DefiLlama), every snapshot pair of both was diffed, and every pair is monotonic — both trails are in fact flat at 162,176 across their entire windows, and the two independent collectors record the same value, which is cross-source corroboration of the same underlying counter. Real watched counters were diffed; none was rewritten. Where a sibling network (AR) shows a BLOCKS restatement (1,988,930 → 1,702,206, on the estate-wide ledger below), BMB's watched fee counters show nothing of the kind. Unlike archives that hold no watchable series at all, BMB's archive holds the exact fee-counter class that produced real restatements elsewhere in this estate — so this zero is a measured negative over the strongest evidence class the detector has, not an absence of evidence. Zero here is the live query result plus the measured trails below, not a gap — the ledger itself is at /v1/revisions?symbol=BMB (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=BMB cross-check passed: the served API reports 0 row(s), matching the ledger count rendered on this page.

What the detector watches for Beamable Network — 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 BMB. Two watched fee series are held and were fully diffed; neither produced a backward pair. That is the structural content of the zero above: watchable counters exist, and they are clean.

The trails behind the zero — watched fee counters, end to end

These are the actual counter trails the detector diffed for BMB, rendered live from the archive. Each is a series that cannot decrease unless upstream rewrote history — which is exactly what makes their monotonicity the proof behind the zero, and the same trail class where an AR/SOGNI/AUKI/R1-style restatement would appear if it ever happened. Both trails sit at 162,176: the estate's own first-party collector and DefiLlama agree on the same all-time-fees counter, independently archived.

DL_FEES_ALLTIME_USD — lifetime protocol fees for Beamable Network (estate first-party DefiLlama collector, depin_first_party; this watched class produced real restatements for AR, SOGNI, AUKI and R1 elsewhere in the estate):

fees_alltime_usd — the same all-time fees counter as recorded by the DefiLlama /overview/fees collector under its own metric spelling:

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. BMB's worked example: market cap, fully-diluted valuation, price and its high/low bands, rolling-window price changes, volume, staking TVL, market-cap rank and the supply spellings are all revalued at every snapshot — BMB is a young token and its market series oscillate accordingly.

Same-timestamp conflicting values on record for BMB: 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 BMB 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.

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 BMB (graded 2026-08-20 13:54:15.000)

Served by /v1/network/BMB — 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 BMB — the same rows this page queried, live:
curl -s "https://kairossignal.com/v1/revisions?symbol=BMB" | 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 fees for beamable-network (the all-time-fees upstream):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/summary/fees/beamable-network" | python3 -m json.tool | head -40
# 4) DefiLlama protocol row for beamable-network (TVL / staking upstream):
curl -s -o /dev/null -w "%{http_code}\n" -H "User-Agent: kairos-check" "https://defillama.com/protocol/beamable-network"
# 5) Solscan token page for the BMB mint (the solana_rpc rows' verify origin):
curl -s -o /dev/null -w "%{http_code}\n" -H "User-Agent: kairos-check" "https://solscan.io/token/BMBtwz6LFDJVJd2aZvL5F64fdvWP3RPn4NP5q9Xe15UD"
# 6) This estate's public API row for BMB (grades + provenance):
curl -s "https://kairossignal.com/v1/network/BMB" | 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_bmb.py and the hourly claim_drift_check.py run grades its claims against the live API like every other published surface. The BMB revision count is the live result of SELECT count() FROM default.depin_revision_ledger WHERE network='BMB'; the page refuses to ship if the served /v1/revisions?symbol=BMB 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 BMB is genuinely empty today — because every watched fee counter the archive holds proved monotonic under the detector's diff, a measured negative published as found, with the full trails 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. Upstream probes ran serially by this generator immediately before rendering: api.llama.fi /summary/fees/beamable-network HTTP 200; defillama.com/protocol/beamable-network HTTP 403; CoinGecko BMB page HTTP 403; solscan.io/token/<BMB mint> HTTP 403; estate /v1/revisions?symbol=BMB HTTP 200; estate /v1/network/BMB HTTP 200.