🔥Telegram İfşa

Just re-read vitalik.eth's Endgame article again. I'm increasingly aligned with the destination: "centralized production, trustless and highly decentralized block validation, and strong anti-censorship protection". ZK rollups make this achievable soon with low latency and

All the layer 2s actually already have "node specialization" — prover is a separate role with a very different hardware requirement. The only difference seems to be the replica node, however, a state diff-based replica node only makes sense with real-time ZK proving for

As a tech nerd and ideologist, Ethereum felt like paradise: We were building the perfect, decentralized endgame — for the future. But in chasing that vision, we forgot the present. Forgot what users actually need today. We built for ideals, not for people. Now the ship is

Getting to Stage 1 took more time and effort than anticipated. But consistent progress pays off — we’re here. Next stop: Stage 2. x.com/Scroll_ZKP/sta…

Last week I reported a Critical bug to Scroll via Immunefi. Massive shoutout to the team for their exceptional commitment to security. The issue was mitigated within minutes after the report. Glad to contribute to Scroll and the Ethereum ecosystem 🧙‍♂️📜

Agree with this. Kudos to OP for this + also doing a good job with their spec and docs! And yes, at Scroll we’re trying to simplify things massively. Not only contracts but the entire L2. Easier to understand and extend but also more performant, resilient, and secure.

I'm wondering what would be MegaETH motivation and benefits of choosing an "execute-then-order" design? Since order determines execution outcomes this would allow to stream the order of tx even before (speculative parallel) execution is finished. An order could be

Some thoughts on rollups

Check out this deep dive by Jonas Theis 📜, probably the most comprehensive piece on rollup design from first principles. It breaks down every component (inbox, sequencer, prover, bridge, L2 node) and explores key trade-offs like: tx data vs. state diffs, latency vs.

We've been thinking about this idea for a while: How can you make a rollup safer (fast off-chain finality within few seconds) and cheaper (better compression) at the same time? The answer is subcommitments.

Tbh I don’t really get the push for existing rollups to become native+based. 1. Technically some existing rollups that diverged too much/have different technology can’t become native. 2. Becoming native has benefits. But it essentially makes all native rollups equal in terms of