# L2BEAT > L2BEAT is an independent analytics and research website about Ethereum scaling. It tracks layer 2s and layer 3s, data availability layers, interoperability protocols, privacy protocols and zero-knowledge proving systems, assessing their risks, maturity stages, value secured, activity, liveness and costs. Risk assessments are backed by on-chain contract discovery and all project data is open source. Important notes: - Links ending in .md are markdown: summary pages list every tracked project with its page URL, and the Markdown pages section covers single projects. The other links are HTML pages. - Prefer the .md URLs: page URLs also answer Accept: text/markdown, but an edge cache may serve them as HTML. - Slugs and interop token ids are case-sensitive: use them exactly as listed. - {slug} in API paths is the last segment of a project page URL, e.g. arbitrum for https://l2beat.com/layer2s/projects/arbitrum. - All API endpoints except the scaling summary wrap their result as { success, data }. - "Stage" is the rollup maturity level (Stage 0, 1 or 2) defined by the stages framework linked below. When to use L2BEAT: - To answer which layer 2s exist, how mature they are (stage), what their risks are and how they compare. - To get current or historical total value secured, activity, liveness or cost figures for a layer 2, via the pages or the JSON API. - To check where a layer 2 posts its data and how secure that data availability layer and its bridge are. - To look up which proving system, stack or ecosystem a project uses, or the definitions behind L2BEAT terms. - Not for token prices, exchange data, wallet balances or anything outside Ethereum scaling and its infrastructure. ## Scaling (layer 2s and layer 3s) - [All scaling projects](https://l2beat.com/layer2s/summary.md): Markdown list of every tracked layer 2, layer 3 and ecosystem with category, stage, stack, host chain and page URL. - [Summary](https://l2beat.com/layer2s/summary): Every tracked layer 2 and layer 3 with its stage, risk rosette, total value secured, category and stack. - [Risk analysis](https://l2beat.com/layer2s/risk): Per-project risk rosette: state validation, data availability, exit window, sequencer failure and proposer failure. - [State validation](https://l2beat.com/layer2s/risk/state-validation): How each project proves or challenges its state: proof system, challenge period, verifier and upgrade delays. - [Data availability risks](https://l2beat.com/layer2s/risk/data-availability): Where each project posts its data and the risks of that choice: layer, bridge, mode and attestations. - [Sequencing](https://l2beat.com/layer2s/risk/sequencing): Who orders transactions on each project and what users can do if the sequencer fails or censors. - [Total value secured (TVS)](https://l2beat.com/layer2s/tvs): Value secured by each layer 2, split into native, canonically bridged and externally bridged tokens, with 7- and 30-day changes. - [TVS breakdown](https://l2beat.com/layer2s/tvs/breakdown): Every token counted in TVS across all projects, with amount, USD value, category and bridging source. - [Activity](https://l2beat.com/layer2s/activity): Transactions and user operations per second for each layer 2, compared with Ethereum, with 7- and 30-day changes. - [Liveness](https://l2beat.com/layer2s/liveness): How often each project submits batches, state updates and proofs to Ethereum, with intervals and anomalies. - [Costs](https://l2beat.com/layer2s/costs): What each project pays Ethereum for calldata, blobs, compute and overhead, in ETH, USD and gas, per transaction or in total. - [Archived projects](https://l2beat.com/layer2s/archived): Layer 2s and layer 3s that shut down or are no longer tracked, with their last known data. - [Stages framework](https://l2beat.com/stages): The rollup maturity framework: what a project must satisfy to be Stage 0, Stage 1 or Stage 2. - [Native rollups](https://l2beat.com/native-rollups): Explainer and tracker for native rollups, which verify state transitions with an Ethereum precompile. ## Data availability - [All data availability layers](https://l2beat.com/data-availability/summary.md): Markdown list of every tracked data availability layer and bridge, public and custom, with type, risks and page URL. - [Summary](https://l2beat.com/data-availability/summary): Data availability layers and their bridges to Ethereum, with economic security, throughput and the projects using each. - [Risk analysis](https://l2beat.com/data-availability/risk): Per-layer and per-bridge risks: economic security, fraud detection, committee security, upgradeability and relayer failure. - [Throughput](https://l2beat.com/data-availability/throughput): Data posted per day to each layer, its maximum capacity and which projects post the most. - [Liveness](https://l2beat.com/data-availability/liveness): How regularly data is posted to each layer and whether its bridge keeps up. - [Archived layers](https://l2beat.com/data-availability/archived): Data availability layers no longer tracked. - [Data availability risk framework](https://l2beat.com/da-risk-framework): How L2BEAT evaluates the risks of data availability layers and their bridges. ## Interoperability - [All interop protocols](https://l2beat.com/interop/summary.md): Markdown list of every tracked cross-chain protocol with type, bridge types and page URL. - [Summary](https://l2beat.com/interop/summary): Cross-chain protocols and token frameworks connecting Ethereum and its layer 2s, with activity and message volumes. - [Non-minting bridges](https://l2beat.com/interop/non-minting): Protocols that move messages or liquidity without minting new token representations. - [Lock-and-mint bridges](https://l2beat.com/interop/lock-and-mint): Bridges that lock tokens on one chain and mint a representation on another. - [Burn-and-mint bridges](https://l2beat.com/interop/burn-and-mint): Bridges that burn tokens on the source chain and mint them on the destination. - [Token frameworks](https://l2beat.com/interop/token-frameworks): Standards for multi-chain tokens such as xERC20, OFT and NTT, and which tokens use them. - [Intent bridges](https://l2beat.com/interop/intent-bridges): Protocols where solvers fill user intents across chains and settle afterwards. ## Other trackers - [Privacy](https://l2beat.com/privacy/summary): Privacy protocols on Ethereum and its layer 2s, with what they hide, anonymity set sizes and trust assumptions. - [All privacy protocols](https://l2beat.com/privacy/summary.md): Markdown list of every tracked privacy protocol with category, exit window and page URL. - [ZK catalog](https://l2beat.com/zk-catalog): Zero-knowledge proving systems used by tracked projects, with their verifiers, trusted setups, audits and which projects rely on them. - [All proving systems](https://l2beat.com/zk-catalog.md): Markdown list of every active proving system in the ZK catalog with creator, trusted setups, verifier counts and page URL. - [Governance](https://l2beat.com/governance): L2BEAT governance research, delegate activity and the projects L2BEAT holds delegated voting power in. - [Multisig report](https://l2beat.com/multisig-report): Report on how multisigs are used to govern and upgrade layer 2s. ## Reference - [Glossary](https://l2beat.com/glossary): Definitions of the terms used across L2BEAT. - [FAQ](https://l2beat.com/faq): How L2BEAT works, what it tracks, how TVS and risks are computed and how to get a project listed. - [Publications](https://l2beat.com/publications): Research, explainers, monthly ecosystem updates and governance reviews published by L2BEAT. - [Changelog](https://l2beat.com/changelog): Dated log of changes to the site, its frameworks and its methodology. - [About us](https://l2beat.com/about-us): The mission, team and funding of L2BEAT. ## Markdown pages - [Scaling project](https://l2beat.com/layer2s/projects/{slug}.md): One layer 2 or layer 3 as markdown: stage and its requirements, risks with sentiments, TVS and activity, technology, permissions and contracts. - [Data availability project](https://l2beat.com/data-availability/projects/{layer}/{bridge}.md): One data availability layer with one of its bridges as markdown: economic security, risks with sentiments, technology, committee, permissions and contracts. The {layer}/{bridge} pairs of active layers are listed in /data-availability/summary.md; archived layers keep their pages but are not listed. - [Privacy protocol](https://l2beat.com/privacy/projects/{slug}.md): One privacy protocol as markdown: what it promises to hide and how that holds against each adversary, trusted setup, exit window, deposits and value locked per asset, governance, permissions and contracts. - [Interop protocol](https://l2beat.com/interop/protocols/{slug}.md): One bridge as markdown: last 24h volume, transfers, top path, transfer time and top token, description, volume by chain, permissions and contracts. Canonical bridges of scaling projects redirect to /layer2s/projects/{slug}.md. - [ZK catalog project](https://l2beat.com/zk-catalog/{slug}.md): One proving system: trusted setup risks, verifier IDs and deployments, program hashes. - [Interop token](https://l2beat.com/interop/tokens/{slug}.md): One token across bridges as markdown: past-day volume, transfers and top path, the protocols moving it, and its onchain deployments with minting bridges. {slug} is the case-sensitive token id, the segment right after /interop/tokens/ in a token page URL; interop protocol pages link their top token. ## Public API - [Scaling summary](https://l2beat.com/api/scaling/summary): JSON of every active layer 2 and layer 3 (stage, risks, TVS breakdown, category, stack) plus a 30-day TVS chart. - [Scaling TVS](https://l2beat.com/api/scaling/tvs): Current USD and ETH value plus a TVS chart (native, canonical, external, ETH price); query params: range, type, projectIds, excludeAssociatedTokens, excludeRwaRestrictedTokens (defaults to true). - [Project TVS](https://l2beat.com/api/scaling/tvs/{slug}): Current USD and ETH value plus a TVS chart for one project; query params: range, excludeAssociatedTokens, excludeRwaRestrictedTokens (defaults to true). - [Project TVS breakdown](https://l2beat.com/api/scaling/tvs/{slug}/breakdown): The tokens making up one project TVS, with amounts, USD values, category and bridging source. - [Scaling activity](https://l2beat.com/api/scaling/activity): Chart of transaction and user operation counts for layer 2s; query params: range, type, projectIds. - [Project activity](https://l2beat.com/api/scaling/activity/{slug}): Chart of transaction and user operation counts for one project, or for Ethereum with slug ethereum; query param: range. ## Optional - [Source code and project configs](https://github.com/l2beat/l2beat): The L2BEAT monorepo: frontend, backend, and every project config with risks, contracts, permissions and discovery history. - [Governance forum](https://forum.l2beat.com/): Discussion of L2BEAT governance research and delegation. - [Medium](https://medium.com/l2beat): Long-form articles and framework announcements. - [X](https://x.com/l2beat): Announcements and short updates. - [Donate](https://l2beat.com/donate): How to support L2BEAT as a public good. - [Terms of service](https://l2beat.com/terms-of-service): Terms of use for the site and its data.