
An open-source, public-good platform tracking the risks and guarantees of Ethereum projects, and tending the CROPS. Previously @l2beat ๐
Ethereum
Joined July 2021
- Tweets3.4K
- Following234
- Followers42.4K
- Likes2.9K
ETHBEAT ๐ (prev L2BEAT) retweeted
From L2Beat to ETHBeat
Luca from @ethbeat_org highlighting how the Michelin Guide for CROPS will bring even more transparency to Ethereum and all users.
ETHBEAT ๐ (prev L2BEAT) retweeted
ETHEREUM EVERYTHING @ethbeat_org
ETHBEAT ๐ (prev L2BEAT) retweeted
typical thursday in centralized L2 slop land: @HSKChain has replaced the main rollup contract *for 6 minutes* with one that can generate L2 txs with any `from` to forcefully transfer 142K USDT out of an L2 EOA without their signature
ETHBEAT ๐ (prev L2BEAT) retweeted
Join us this Wednesday, Oct 14 for our monthly meetup at @fullnode_berlin, starting at 18:30! ๐๏ธ
Following Martinโs talk on public goods funding last month, weโll explore @l2beat with @sergeyshemyakov to explore one of Ethereumโs impactful public goods projects and how its open-source research and tools strengthen transparency, security, privacy and the broader Ethereum ecosystem.
RSVP links ๐๐งต
ETHBEAT ๐ (prev L2BEAT) retweeted
The final, 6/6 installment of the privacy challenge by @l2beat - this one is about @Zcash - can we actually de-anonymise the user there? teapawt.org/l2beat/status/21049183โฆ
We have a special treat for you at Lฬต2ฬตPrivacyBEAT today: an amazing treasure hunt to unleash your inner @zachxbt! ๐
This was originally part of an internal workshop, but now weโre opening it up to you! All details here: privacyhunt.gwei.domains/ or in the thread below.
ETHBEAT ๐ (prev L2BEAT) retweeted
The 4/6 of treasure hunt - we're more than half way through ๐ This one will be, hopefully, somewhat entertaining so follow along. And - as usual - check the original challenge teapawt.org/l2beat/status/21049183โฆ
We have a special treat for you at Lฬต2ฬตPrivacyBEAT today: an amazing treasure hunt to unleash your inner @zachxbt! ๐
This was originally part of an internal workshop, but now weโre opening it up to you! All details here: privacyhunt.gwei.domains/ or in the thread below.
ETHBEAT ๐ (prev L2BEAT) retweeted
current zama txes are 95% public. so people are not able to use it as a privacy protocol, or maybe do not care. that is not optimal for a privacy protocol.
sekuba.github.io/zama-graph/
be gentle to that little explorer, it strictly displays only public onchain data
Replying to @bkiepuszewski
But is there a way to use Zama so that indeed the amounts are hidden ? And what exactly is the use case for hiding just the amounts and not the links ?
ETHBEAT ๐ (prev L2BEAT) retweeted
The 3/6 installment of the Privacy Treasure Hunt from @l2beat - this one will teach you how @zama confidential amount tokens work. Our starting address is 0x906ff67514449638DadDC09b007f0b7b3023EF33 teapawt.org/l2beat/status/21049183โฆ
We have a special treat for you at Lฬต2ฬตPrivacyBEAT today: an amazing treasure hunt to unleash your inner @zachxbt! ๐
This was originally part of an internal workshop, but now weโre opening it up to you! All details here: privacyhunt.gwei.domains/ or in the thread below.
ETHBEAT ๐ (prev L2BEAT) retweeted
announcing nativerollups.fyi, a closed devnet based on frames-devnet-0 running a (half mocked) native rollup on top
a native rollup is an L2 that inherits L1's STF directly, greatly reducing complexity, governance and bug risks. here's how it works ๐งต
ETHBEAT ๐ (prev L2BEAT) retweeted
kinda disappointed seeing @ethlabs_org still claiming that the FCR is live and used on CCIP today when it's still not, so here's a short lesson on how to check the chain (and how CCIP works) ๐
ETHBEAT ๐ (prev L2BEAT) retweeted
๐ค As ZK Researcher at L2BEAT, I'm speaking at the TUM Blockchain Conference 26 โ the First Conference Day on October 29!
The full conference runs Oct 29 to 31 in Munich, hosted by @tbc_munich, with the Digital Assets Day by @bundesblock on Oct 30 โ conference26.tum-blockchain.โฆ
ETHBEAT ๐ (prev L2BEAT) retweeted
privacy pools v1 now has four green dots on @l2beat ๐ข
Link privacy against the network observer is now green for @0xprivacypools! ๐ข
This is a result of two recent fixes to their frontend, the latest being custom RPC support ๐
teapawt.org/0xprivacypools/status/โฆ
ETHBEAT ๐ (prev L2BEAT) retweeted
Here's @l2beat research team Hegotรก ranking, which represents the combined opinions of @sekubalias, me, @sergeyshemyakov and @vincfurc.
Detailed motivations below ๐
ETHBEAT ๐ (prev L2BEAT) retweeted
NEW SPEAKER ANNOUNCEMENT ๐ข
@radina_nt, Product Manager at @l2beat, is joining ETH Belgrade.
Having worked on L2BEATโs interoperability research and data, Radina will break down how cross-chain infrastructure works today, from bridge designs to the trust and security trade-offs behind them.
ETHBEAT ๐ (prev L2BEAT) retweeted
just opened a proposal to enable native rollups via STARK-carrying frame transactions (8141 + 8288)
with this registry native rollups can enforce proofs that follow L1 semantics and automatically upgrade with it or pin a specific fork
github.com/ethereum/EIPs/pulโฆ
ETHBEAT ๐ (prev L2BEAT) retweeted
I didn't visit @l2beat for some time as L2 wars are now just a chapter of history.
But yay โ they shipped such cool updates recently.
ETHBEAT ๐ (prev L2BEAT) retweeted
Native rollups let Ethereum verify L2 state transitions with its own execution, so chains inherit L1 security and upgrades by default.
We started with the re-execution path: L1 re-runs each L2 block through the EXECUTE precompile, no prover required. Our PoC on ethrex is a full end-to-end native rollup, with live deposits and withdrawals.
Now we're targeting the verify path: L1 verifies a proof of each block instead of re-running it. That's native proof verification, where the research is heading.
@l2beat just launched a page tracking native rollups research. Start here ๐
For the past couple of months we've been looking into Native Rollups - the idea of turning L2 blocks into proof-carrying transactions on L1.
In that time, the work has moved from research posts and draft EIPs to a working PoC from the @class_lambda @ethrex_client team.
Today we're launching a page to help you learn more about the ongoing research and follow its progress!
Here's a summary of where we are, plus some insights from @ethrex_client on the PoC they've been working on ๐


































