L2BEAT 💗
@l2beat
Followers
41K
Following
2K
Media
543
Statuses
2K
L2BEAT is an open-source, public-good analytics and research platform dedicated to L2 scaling solutions 💗
Layer 2
Joined July 2021
L2BEAT Recategorisation is LIVE! 🔀. This is the biggest update to our framework yet - redefining what it truly means to be an Ethereum L2. 130+ projects re-evaluated. New standards. Clearer definitions. Higher expectations. Here’s what changed - and why it matters 👇
64
216
472
This update helps both us and you track these incidents more transparently. Be sure to check the Liveness section regularly:.
0
0
6
🔴 Major ongoing anomalies as of now:. - no stage updates @DeGateDex .- no tx data submissions & no state updates @kroma_network .- no tx data submissions & no state updates @pepe_unchained.
1
0
5
You can find the new Anomalies view at the top of the Liveness page. It shows details like:.- Total time with no state updates / data submissions.- Time of last update.- Average update frequency
1
0
5
Frequent or long-running anomalies can also suggest deeper problems:. – Operational issues.– Fragile infrastructure.– Risky design trade-offs. Over time, this affects whether an L2 can be trusted.
1
0
5
Monitoring uptime and data publication isn’t just due diligence - it’s the only way to know the system is still safe to use.
1
0
5
If you’re using L2s regularly, this matters. Trusting an operator once is not enough - without regular state updates, even a well-intentioned system becomes unreliable.
1
0
9
The new view alerts when an L2 hasn’t posted data for an unusually long time - like over 24h. That could point to technical issues, a scheduled upgrade, or something more serious. It’s an early signal that the system might be unavailable or unstable for their users.
1
0
8
If that data flow stops, there’s a real risk that recent chain activity - including state updates - could be lost entirely or withheld maliciously. In some cases, users may even be unable to withdraw their funds if no new state is published.
1
0
8
First, a reminder: Liveness tracks whether L2 systems are posting tx data, state and proofs to their respective Data Availability (DA) and settlement layers - Ethereum, Celestia, Avail, etc.
1
0
8
We just shipped a small but important update to the Liveness section on L2BEAT. You can now see ongoing anomalies across L2s in real time in a single view. Why should you care? 👇
7
8
61
RT @l2beatgov: 1/ There's a new upgrade proposal on @Optimism currently up for a vote. What is it about, and how does it work?. Let's brea….
0
10
0
RT @donnoh_eth: one of the most annoying thing of reviewing projects through etherscan is when contracts import other contracts just to use….
0
7
0
JUD - Just Use Disco.
one of the most annoying thing of reviewing projects through etherscan is when contracts import other contracts just to use them as an interface, and etherscan gives you the full code as if any of it is actually relevant, misleading you. worry not, we have a fix 👇
2
0
3
RT @hubkotl: New @RobinhoodApp L2 is on the way in the coming months - built on the @arbitrum Orbit stack. We’ll be there to add it to @l2….
0
7
0
If you're building an L2 - or building on one - you'll want to catch this. L2BEAT cofounder @bkiepuszewski takes the @EthCC main stage to discuss the L2 Recategorisation landfall and how the Stages assessment is evolving. 📍 Monroe Stage.🕐 June 30th, 1:35 PM
5
7
41
Learn more about Kroma shutdown here:.
🚨 8 Days Left: Unstake & Withdraw All Assets from Kroma Network. The Kroma Mainnet shuts down on June 30, 2025 — just 8 days to go ⏳. Please make sure to unstake and withdraw all your assets from Kroma Network, including:.🔹 WEMIX.🔹 spETH.🔹 st.WEMIX.e.🔹 WETH.🔹 USDT.🔹 USDC
0
0
7
🚨 Warning: @kroma_network is shutting down on June 30!. There’s still $2.48M sitting on the chain - and after the deadline, those assets will be unwithdrawable (yes, gone). If you’ve got funds there, withdraw ASAP!
24
42
263
To dig deeper, head to EigenDA’s detail page. You’ll see which scaling projects contribute to the data - and how much of it remains unattributed for now.
0
0
5
You can easily switch between those views on the main throughput chart. Interestingly, even with this additional data, EigenDA is still using less than 2% of its maximum theoretical capacity.
1
1
11
There’s actually ~22 GiB of additional data, but since it’s not attributed to any scaling solution, it’s marked as 'Unknown' and is hidden by default on the main chart.
1
0
9