Beamable Network (BMB) — the network, measured

Generated 2026-09-02T16:10:56Z from live ClickHouse queries against this estate's ledger. Held inventory: 8,115 observations · 36 distinct series · 4 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-09-02 15:49:30 · 8,115/8,115 rows carry a verify_url. 33 series refreshed in the last 24h (778 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where every number 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.

30-day history — headline series (daily last-value, live)

One row per series: latest value, a 30-day sparkline of daily last-known values (scaled to the series' own min→max), day count, and window change. Series absent from the 30-day window are omitted from this table, not zero-filled.

Market reference — CoinGecko coin page, as held

Market-data reference rows: price, supply, capitalisation, diluted valuation, and the published change columns including ATH/ATL. These are the coin-page reference's own numbers — the estate does not model, smooth, or forward-fill them. The change columns start later than the price rows in our archive (each metric's caveat in the full inventory states its own first-held row) and are shown from their first held row.

Fees & revenue — DefiLlama protocol data, as held

Protocol-level fees and revenue from DefiLlama's public summary API. Fees rows verify against /summary/fees/beamable-network; revenue rows against /summary/fees/beamable-network?dataType=dailyRevenue — each row keeps its own verify_url. The latest 24h/7d/30d fee windows currently read 0 as DefiLlama reports them; that is the live upstream answer and it is published exactly as answered, while the 1y and all-time windows read non-zero (they ride a sparser collector generation than the short windows — shown as held, the archive's own shape, not smoothed). Revenue is DefiLlama's dailyRevenue slice (fees kept by the protocol after contributor payments) — a different measurement from fees, never netted against it on this page.

TVL — DefiLlama protocol page, as held

Two buckets of the same DefiLlama /protocol/beamable-network response: the protocol-page TVL (tvl[] series' last totalLiquidityUSD) and the staking bucket (currentChainTvls.staking). They are different measurements — the general TVL bucket currently reads 0 as DefiLlama reports it while the staking bucket reads non-zero — and both are published exactly as answered, never netted, summed, or reconciled against each other. A zero here is the upstream's live answer, not a gap (the history table shows the staking series' 30-day shape).

Solana-chain state — RPC reads, as held

Chain state for the Solana-mainnet mint BMBtwz6LFDJVJd2aZvL5F64fdvWP3RPn4NP5q9Xe15UD (catalog chains: Solana), read from public Solana mainnet RPC methods getTokenSupply (on-chain total supply) and getTokenLargestAccounts (holder-concentration percentages; the estate collector rotates to a free public endpoint for this method — see the verify commands). The concentration rows measure token ACCOUNTS, not owners — one owner can hold many accounts, and pools/treasuries/exchanges count as single holders — so they are an upper-bound proxy for owner concentration and are labelled as such. The concentrations are extreme as the RPC reports them (top-1 ≈ 28%, top-10 ≈ 92%, top-20 ≈ 98% at the last held read); they are published raw, never relabelled as owner data and never read as investment advice. onchain_total_supply is a different measurement family from the CoinGecko market reference; the two are never merged, and no ratio is derived between them.

Full metric inventory — 36 measured series, each with provenance

Every series held for BMB with rows in the last 30 days: latest value, when it was observed, which source observed it, how many rows we hold, how many of the last 30 days it reported, its comparability grade, and the origin link. "days/30" counts distinct dates with at least one row in the window.

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

Backward revisions are values upstream later replaced for a date we had already archived. The before-value is retained — that retention is the only reason a rewrite is detectable, and it is the part every overwriting vendor discards.

The ledger query ran during generation and returned 0 rows for BMB. Zero here is the live query result, not a gap — the ledger itself is at /v1/revisions.

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, not ours to smooth. The overall grade is middling and it is published as computed: the catalog lists no public stats API and the estate holds no first-party node telemetry for this network, so the engines grade on third-party and chain-state series alone — the revenue and data-coverage F grades are shown 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–3 hit the same upstream endpoints our collectors do (the coingecko.com browser coin page 403s plain curl, so the programmatic markets endpoint is given; api.mainnet-beta.solana.com applies a per-method quota to getTokenLargestAccounts, so that command uses the free public endpoint the collector rotates to); command 4 hits this estate's public API, where every row carries the same source / as_of / verify_url fields.

# 1) Solana-mainnet token supply (public RPC, the collector's method), as of 2026-09-02T16:10:56Z:
curl -s -H "User-Agent: kairos-check" "https://api.mainnet-beta.solana.com" -X POST -H "Content-Type: application/json" -d '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"getTokenSupply\",\"params\":[\"BMBtwz6LFDJVJd2aZvL5F64fdvWP3RPn4NP5q9Xe15UD\"]}' | python3 -m json.tool
# 1b) Holder-account concentration (the collector rotates endpoints for this method):
curl -s -H "User-Agent: kairos-check" "https://solana.lava.build" -X POST -H "Content-Type: application/json" -d '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"getTokenLargestAccounts\",\"params\":[\"BMBtwz6LFDJVJd2aZvL5F64fdvWP3RPn4NP5q9Xe15UD\"]}' | python3 -m json.tool | head -35
# 1c) The per-token page our verify_url points at (human view):
curl -s -o /dev/null -w "%{http_code}\n" "https://solscan.io/token/BMBtwz6LFDJVJd2aZvL5F64fdvWP3RPn4NP5q9Xe15UD"
# 2) Protocol fees (DefiLlama public API):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/summary/fees/beamable-network" | python3 -c "import json,sys; d=json.load(sys.stdin); print('total24h', d.get('total24h')); print('total30d', d.get('total30d')); print('totalAllTime', d.get('totalAllTime'))"
# 2b) Protocol revenue (same family, revenue slice):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/summary/fees/beamable-network?dataType=dailyRevenue" | python3 -c "import json,sys; d=json.load(sys.stdin); print('total24h', d.get('total24h'))"
# 2c) Protocol TVL + staking bucket (same /protocol response the rows read):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/protocol/beamable-network" | python3 -c "import json,sys; d=json.load(sys.stdin); t=(d.get('tvl') or [{}]); print('tvl_usd', (t[-1] if t else {}).get('totalLiquidityUSD')); print('staking', (d.get('currentChainTvls') or {}).get('staking'))"
# 3) Market reference (CoinGecko public API):
# CoinGecko public markets API (the endpoint family our collector
# reads for the price/supply/cap rows) — the coingecko.com browser
# coin page 403s plain curl, so the programmatic endpoint is given:
curl -s "https://api.coingecko.com/api/v3/coins/markets?vs_currency=usd&ids=beamable-network" | python3 -m json.tool
# 4) This estate's public API row for BMB:
curl -s "https://kairossignal.com/v1/network/BMB" | python3 -m json.tool | head -60

Method & honesty notes. All counts are queries against the live ledger at generation time, not restamped copy — this page is regenerated by gen_deep_dive_bmb.py and the hourly claim_drift_check.py run grades its claims against the live API like every other published surface. Comparability grades come from the served canonical-metric system via its own resolver: total_supply maps to token_supply_total (question-verified). The remaining series are BMB-native market/on-chain metrics with no cross-network concept; grading them would be fabrication, so they are labelled "bmb-native (unmapped)". THREE supply references are shown side by side as held, never summed, merged, or reconciled: CoinGecko's circulating and total supply, and the Solana-RPC on-chain token supply. The CoinGecko circulating_supply row is a different quantity (circulating vs total) and is never netted against the other reads. The currently-zero DefiLlama 24h/7d/30d fee windows and the currently-zero general TVL bucket are DefiLlama's live answers, published as answered with their shapes shown; they are never silently replaced or smoothed. The Solana concentration rows stay raw account-level percentages as the RPC reports them — an upper-bound proxy, never relabelled as owner concentration, never presented as investment advice. The estate holds no GitHub and no first-party snapshot rows for BMB — those sections are absent rather than zero-filled, and the queries rerun at every regeneration. Where a section has no data, it is absent — we do not publish zeros for gaps. Upstream probes run serially by this generator immediately before rendering: Solana mainnet RPC HTTP 200; DefiLlama fees API HTTP 200; DefiLlama revenue API HTTP 200; DefiLlama protocol API HTTP 200; CoinGecko markets API HTTP 200; estate /v1/network/BMB HTTP 200.