Search

Search projects, tokens and protocols by name or address

L2BEAT is now
ETHBEAT

Our work has grown well beyond layer 2s, and our new name and mandate reflect that.

A new centre

L2BEAT was built around layer 2s. ETHBEAT is built around Ethereum, and layer 2s are one of the many things around it.

L2BEAT

DataavailabilityZKBridgesLayer 2s

ETHBEAT

Layer 2sPrivacyZKInteropAnd moreStakingDeFiTokensEthereum

Five years of L2BEAT

L2BEAT started more than five years ago with one goal: to shed some light on a new and quickly developing category of products built on top of Ethereum, the Layer 2s.

Times were different back then. We were just past DeFi Summer and ahead of the NFT craze. Ethereum was having its comeback moment, but it faced scaling issues: gas prices during network congestion were crippling broader adoption.

That's where L2s came in, promising to scale Ethereum while inheriting its security guarantees. But did they?

We tried to answer that question in many different ways:

  1. 1Tracking adoption

    We built dashboards to track the growth of L2s, starting with TVL, later reframed as Total Value Secured (TVS), and expanding into activity and other metrics.

  2. 2Understanding how systems actually work

    We examined the source code of deployed smart contracts to explain how projects implemented their promises onchain. We surfaced the gaps between those promises and the guarantees users actually received - the “training wheels” introduced to work around unresolved technical challenges.

  3. 3Developing and maintaining standards

    Through our risk assessments and the Stages Framework, we made the tradeoffs of using L2s more visible. We tracked progress toward removing training wheels and pushed for higher standards across the ecosystem.

  4. 4Monitoring changes

    We built a monitoring system to detect changes to the smart contracts behind the projects we cover. Our researchers review and classify those changes, keeping assessments up to date as the systems evolve.

  5. 5Participating in governance

    We took part in L2 DAO governance, at times as one of the largest and most active delegates in the Optimism Collective, Arbitrum DAO, ZK Nation, Scroll DAO, and others, helping shape decisions about how these systems are developed and governed.

  6. 6Bringing people together

    We organized conferences focused on the development of the L2 ecosystem, including Layer Two Amsterdam, L2Warsaw, and L2DAYS Istanbul, alongside smaller meetups and gatherings.

  7. 7Contributing to research and development

    Last but not least, we were active in R&D, joining various working groups and, most notably, driving the research on native rollups.

Over those years, we became a central reference point for Ethereum L2 development, keeping the space accountable and pushing it to live up to its "scaling Ethereum" claims.

But Ethereum has changed

Scaling is now being addressed directly at the L1 protocol level, and Layer 2s are finding product-market fit outside of scaling Ethereum, offering specialized onchain products that go beyond what a credibly neutral base layer can provide.

Meanwhile, more and more solutions are being built on Ethereum across privacy, interop, DeFi, and beyond. Users are asking the same questions about them that they once asked about L2s:

  • Which of Ethereum's core properties do these solutions inherit?
  • Which claims are real, and which are just marketing?
  • Whom do they actually have to trust?

We've been asking those questions too, gradually expanding what we cover: first ZK components through our ZK Catalog, then interop, privacy solutions, tokens, blob usage, and more to come.

We haven't been focused solely on Layer 2s for quite some time, so it only makes sense for our name to reflect that. This doesn't mean we're leaving L2s behind. Our coverage isn't going anywhere, and we'll keep monitoring them as closely as ever. They're just no longer our main focus.

We're excited about the future of Ethereum, and we want to work alongside other Ethereum-focused organizations to bring the transparency and scrutiny we're known for in the L2 space to the broader ecosystem.

To make clear what this means in practice, we've set out our plans and scope in a mandate that will guide our next steps.

Read the mandate

What this means for you

What changed

  • The name and the logo

    ETHBEAT, with a new hand‑lettered heart.

  • The address

    The site now lives at ethbeat.org. Every l2beat.com link redirects permanently to the same page there.

  • Link previews

    Pages shared on X, Telegram and elsewhere show new preview images. Platforms cache previews, so older posts may show the old ones for a while.

  • Social accounts

    On X we are now @ethbeat_org. Our other accounts will follow.

What stays the same

  • The team and our independence

    The same people do the research, funded in the open as a public good. How we are funded

  • The methodology

    Our risk frameworks, the Stages framework and every assessment are unchanged. No project was re‑scored because of the rename.

  • The data

    Every project page, chart and history is where it was, under the same path.

  • Open source

    The code and every project config stay at github.com/l2beat/l2beat.

Old links keep working

Only the domain changes. Everything after it stays the same, and the redirects stay indefinitely.

l2beat.com
ethbeat.org
l2beat.com/layer2s/summary
ethbeat.org/layer2s/summary
l2beat.com/layer2s/projects/arbitrum
ethbeat.org/layer2s/projects/arbitrum
l2beat.com/api/scaling/summary
ethbeat.org/api/scaling/summary
l2beat.com/llms.txt
ethbeat.org/llms.txt
  • The API

    Same endpoints, same responses. Point your clients at ethbeat.org when you can: most HTTP clients follow redirects, some do not.

  • Badges

    CROPS badges keep loading from their old URLs and now show the new name. A badge pasted as inline markup keeps its old text until you copy the markup again.

  • Forum, Disco and tools

    They move to ethbeat.org later on launch day, and their l2beat.com addresses redirect there too.

  • Citing us

    "ETHBEAT (formerly L2BEAT)" helps readers who know the old name.

Questions? Ask on the forum.