Published May 18, 2023

Did Ethereum Break? with Preston Van Loon & Terence Tsao

Explore the resilience of Ethereum as developers Preston Van Loon and Terence Tsao discuss the recent finalization issues that tested the network's security and developer community, shedding light on the importance of client diversity and consensus mechanisms in overcoming technical crises.
Episode Highlights
Bankless logo

Popular Clips

Episode Highlights

  • Liveness & Resilience

    Ethereum's consensus mechanisms prioritize liveness over high transaction throughput, ensuring the network remains operational even during disruptions. explains that this design choice allows Ethereum to continue processing transactions, unlike other blockchains that may go offline during issues 1. This resilience is further demonstrated by the network's ability to finalize transactions despite challenges, showcasing its robust design. highlights the network's anti-fragile nature, stating, "It just goes to show the resiliency that when things are going horribly wrong, it can still be okay and it still eventually finalizes" 2.

       

    Client Behavior

    The recent incident on Ethereum was not due to a fundamental flaw but rather unexpected client behavior. notes that while diagnosing the issue was straightforward, the solution required careful consideration of trade-offs in client software 3. The problem arose from certain clients producing unexpected attestations, which were valid but not anticipated by others like Prism and Teku 4. explains, "It was just some sort of unexpected behavior, valid behavior, but unexpected that Prism and perhaps Teku didn't consider or handle very well."

       

    Inactivity & Finality

    Ethereum's inactivity leak mechanism was tested during the recent finality incident, highlighting its ability to maintain network operations even under extreme conditions. describes this mechanism as crucial for Ethereum's resilience, allowing the network to continue functioning despite partial connectivity losses 5. The incident also revealed the emotional toll on developers, with recalling the stress of managing the situation: "I see this message I never want to see again... maintenance stopped finalizing" 6.

Related Episodes