Content
@
https://ethereum.org
0 reply
0 recast
0 reaction
Koolkheart
@koolkheart.eth
I really appreciate the transparency in this post, but I’ve got some concerns about the direction Ethereum’s heading with these changes. The goal of “simplifying the L1” is awesome—I totally get why “keeping the protocol simple brings a number of benefits” like making it “simpler to reason about” and reducing “the risk of catastrophic bugs.” But when you say “historically, Ethereum has often not done this (sometimes because of my own decisions),” it makes me wonder if we’re just trading one kind of complexity for another. The “3-slot finality redesign” sounds promising with its “near-optimal security properties,” but I’m nervous about the execution layer changes. Switching from the EVM to RISC-V for a “radical improvement in simplicity” sounds great, but what about all the existing dApps?
1 reply
0 recast
6 reactions
Koolkheart
@koolkheart.eth
The post mentions “a backwards compatibility strategy” where “existing EVM contracts switch to being processed by being run through that interpreter” after several years—that’s a long time to wait, and I’m worried about how messy that transition might get. Also, the “orange and yellow areas” of encapsulated complexity make sense, but will new devs really understand what to skip? I’m glad Fede, Justin Drake, and Tim Beiko gave feedback, but I’d love to hear from others—how do you feel about this VM switch? Am I overthinking this?
0 reply
0 recast
0 reaction
