Here is a summary of Alexey Akhunov’s speech about Ethereum and key concerns regarding its development:
Dangers and Principles for Ethereum
Alexey Akhunov expresses concerns about certain decisions in Ethereum’s development that could hinder its evolution and competitiveness. He highlights the importance of several fundamental projects, even if they seem outdated or difficult to implement.
1. Verkle Trees: A Necessary Step
Verkle Trees are part of Ethereum’s roadmap, but some worry that advancements in quantum computing might render them obsolete before they are fully implemented. However, Akhunov argues that their development is essential as a “practical drill” for modifying Ethereum’s state commitment system. Even if Verkle Trees eventually become outdated, completing the project will refine the process of blockchain upgrades, which will be crucial for future innovations like Poseidon hash adoption.
2. EOF (Ethereum Object Format): A Crucial Framework
There has been discussion about removing EOF from the Ethereum roadmap, as many developers believe it is unnecessary. However, Akhunov argues that EOF is not just about performance improvements—it is a fundamental framework for making the Ethereum Virtual Machine (EVM) upgradeable. If EOF is removed without a clear alternative, Ethereum could struggle to evolve its EVM in the future. Additionally, abandoning both EOF and Verkle Trees would send a negative signal to the developer community, discouraging future contributions.
3. Account Abstraction: Eliminating the Mempool and Improving Efficiency
Account Abstraction is another key topic Akhunov discusses, particularly in relation to the real merge. He explains that in an Erigon-Caplin setup, the execution layer (EL) would no longer need to fetch blocks from its network, as all headers and blocks could be received through the consensus layer (CL). This has major implications for Account Abstraction, especially if the second proposed approach is chosen—where transactions would be handled in a way that removes the need for a traditional mempool. If this happens, devp2p (Ethereum’s peer-to-peer networking layer) could be deprecated altogether, simplifying the network architecture. However, for this to be possible, a clear decision needs to be made regarding how Account Abstraction is integrated into the network’s evolution.
4. The Real “Merge”: Full System Unification
Ethereum transitioned from Proof of Work to Proof of Stake in 2022, but Akhunov believes the network remains split into two separate systems: the Execution Layer (EL) and the Consensus Layer (CL). The “real merge” would unify these systems, improving communication and knowledge sharing among development teams. Erigon has made progress with Caplin, but resistance to merging EL and CL teams remains a major challenge. This issue is more about human capital than technical limitations—without convergence, Ethereum risks not having enough experts who understand both layers, limiting its future development.
Conclusion: The Need for Consistency and Long-Term Vision
Akhunov warns that abandoning projects like Verkle Trees and EOF at the last minute, after years of effort, would be a critical mistake. The decision should not be based solely on potential future obsolescence but on the value these projects bring in creating smoother upgrade processes. Additionally, Ethereum must maintain continuity and trust among developers, avoiding the impression that complex projects are discarded arbitrarily.
In summary, Akhunov’s main message is that Ethereum must preserve its ability to evolve by staying committed to strategic projects, making bold architectural decisions (such as real merge and Account Abstraction), and strengthening its developer community to tackle future challenges.
Original video on the Akexey Akunov Monoblunt channel on Telegram: https://t.me/monoblunt/114
