Bridged TVL by chain: how much of a chain's capital came from somewhere else

The chain-kpis harness reads l2beat.com/api/scaling/summary once every 15 minutes. One request covers the whole cohort; each project entry carries tvs.breakdown with total, native, canonical and external in USD, and a 7-day change. The harness publishes chain_bridged_tvl_usd as canonical + external, chain_value_secured_usd split by origin, chain_tvs_usd as the total, chain_tvs_change_7d_pct as the raw weekly move and chain_tvs_change_7d_excess_pct as that move minus the median of every live project above a $200M size floor. The median and the cohort size are published as chain_tvs_cohort_median_7d_pct, chain_tvs_cohort_size, chain_tvs_cohort_layer3 and chain_tvs_cohort_under_review, so the subtraction can be re-derived from the series rather than taken on trust. Rows are the chains in the OCB registry that L2Beat tracks in its scaling summary, whatever category it files them under; settled L1s carry no id because a chain with no host chain has no bridged balance to report.

• ·Source: L2Beat /api/scaling/summary, one unauthenticated request per tick covering every tracked project. Poll cadence 15 minutes, matched to the DefiLlama cadence in the same harness. Neither is the instant it is read at: DefiLlama publishes one daily TVL aggregate, and L2Beat computes an hourly series that normally runs one to two hours behind, so the page reports the last point each source finished rather than the moment of the request.
• ·Bridged TVL = canonical + external from tvs.breakdown, in USD. Canonical is value escrowed on the host chain by the chain's own contracts; external arrived through a third-party bridge; native was minted on the chain itself and is excluded.
• ·The three origins reconstruct the total, so bridged TVL is exactly the value secured that is not native, and a chain whose value is entirely canonical reads 100 percent bridged. A row whose origins miss its total by more than 0.1 percent is not published at all: if the upstream field names change, every one of them binds to zero, and a $0 bridged TVL at full health would be a wrong number that looks measured.
• ·Weekly move: L2Beat's own change7d on total value secured, converted from a ratio to a percentage. The excess subtracts the median change across every live project above $200M of value secured.
• ·The $200M floor exists because the median is a yardstick. L2Beat tracks about a hundred projects and most of them are small, so without a floor the many dust chains outnumber the rest and their moves, which are incentive programs rather than capital rotation, own the middle of the sorted list.
• ·Cohort composition: every live project above the floor votes, layer 3s and projects L2Beat currently has under review included. They are counted, not filtered, because dropping them would make the yardstick a judgement rather than a measurement; chain_tvs_cohort_size, _layer3 and _under_review publish the composition. Below five projects no median is published and the excess series is cleared rather than frozen.
• ·Rows: every chain in the OCB registry that carries an L2Beat project id, each verified against a live read of the endpoint. Several ids differ from the OCB slug (polygon-pos, zksync2, roninnetwork, worldchain, mantapacific, galxegravity, nova, polygonzkevm, bobanetwork, immutablezkevm).
• ·Membership: a row is a chain in the OCB chain registry that L2Beat tracks in its scaling summary, whatever category L2Beat files it under (42 of L2Beat's roughly 100 projects on 2026-09-25, Plume mapped that day); L2Beat projects outside the registry are not rows. Settled L1s carry no id because a chain with no host chain has no bridged balance to report.
• ·A project L2Beat has archived, one reporting a zero total, and one whose origins do not reconstruct that total all publish nothing: the chain's gauges are deleted rather than carried forward, so the row reads unresponsive within the hour, and chain_kpis_health{source="l2beat"} drops to 0 for that chain. That health series is the success column, so a row that stopped reporting also stops reading 100 percent.
• ·Freshness reads L2Beat's own chart.syncedUntil, not the Prometheus scrape and not the time of our fetch. The first is always seconds old because the harness re-exports carried-forward gauges; the second stays green when L2Beat answers 200 with stale numbers. A row whose weekly move is missing keeps its balance and loses only its two weekly columns, rather than publishing a flat week that never happened.
• ·Every aggregate column reads the latest value rather than a window statistic, so the board and the origin panels always describe the same instant. p50, p90, p99 and the mean are equal by construction; the sample count is the number of Prometheus scrapes in the 24h window (about 2,880 at a 30 second scrape), not a count of measurements, since the underlying value refreshes every 15 minutes.
• ·L2Beat's figures are a third-party measurement, credited as the source. OCB does not re-derive the escrow balances; this bench republishes the split and computes the cohort-relative move on top of it.