ECH Institute Podcast

The conversation covers the progress from the Svalbard Interop, including the launch of DevNet-0 and subsequent DevNet updates. It also delves into the progress of Balldefinite 6, debugging and gas accounting proposals, EIP status and stages, and the reorg window and client support. The discussion provides insights into the latest developments and proposals in the Ethereum ecosystem. The conversation covers the management of deep reorgs, the limitation of block size, and a proposal for the self-destruct feature. It delves into the trialogue with prior versions of each account and slot, the printing mechanism for rollback, and the handling of extremely long reorgs. It also discusses unwinding to 512 blocks in Aragon, rollback by batch in Bezu, and the handling of out of memory for deep logs. Additionally, it explores the removal of the burn feature of self-destruct and the behavior of self-destruct in a limited factor. The conversation methodically reviewed the self-destruct usage analysis and discussed the implications of EIP 8253 and EIP 7610. The self-destruct usage analysis provided insights into the increase in usage despite deprecation notices, while the discussion on EIPs 8253 and 7610 focused on the implications and feasibility of the proposed changes.TakeawaysSvalbard Interop ProgressDevNet Updates Management of deep reorgsLimiting block sizeProposal for self-destruct feature Self-destruct usage analysisEIP 8253 and EIP 7610 discussionChapters00:00 Svalbard Interop Progress and DevNet-012:25 Debugging and Gas Accounting36:02 Managing Deep Reorgs01:03:40 Self-Destruct Usage Analysis01:13:21 EIP 8253 and EIP 7610 Discussion

The episode begins with an introduction and the announcement of Nixo joining as co-lead of AllCoreDev. The conversation then transitions into DevNet updates and discussions around EIP 8037 testing concerns, highlighting issues with test failures and the impact of EIP 8037 on gas limits and costs. The conversation covered concerns and complexities related to EIP 1837, proposals for EIP 8163 and EIP 7979, and performance optimization for ZK-AVM use cases through engine API changes. The discussion also included considerations for mascot selection and the impact of EIP changes on DevNet 4.TakeawaysNixo joins as co-lead of AllCoreDevDevNet updates and issues with EIP 8037 testing EIP 1837 concerns and complexitiesPerformance optimization for ZK-AVM use casesDiscussion on engine API performance and potential changesChapters00:00 Introduction and Nixo's Co-Lead Announcement57:26 EIP 1837 Concerns and Complexities01:09:12 EIP Proposals and Mascot Selection for Glam-Sedam01:14:52 EIP 7979 Proposal and Discussion01:31:22 Engine API Performance Optimization for ZK-AVM Use Cases#Ethereum #ACDE #AllCoreDev

Agenda: https://github.com/ethereum/pm/issues/1990Watch Video Version: ACDC 177TakeawaysDevnet PlanningConsensus Layer ChangesPR Merging and Testing Consensus Layer ChangesValidator Deposit VulnerabilityState Growth EIP UpdateChapters00:00 Devnet Planning and PR Updates34:59 PR Merging and Testing51:14 Consensus Layer Changes and Queue Merging56:57 Validator Deposit Vulnerability01:24:04 State Growth EIP Update

This episode covers the innovative Ethereum Virtual Virtual Machine (EVVM) project, a comprehensive ecosystem aimed at enhancing scalability, privacy, and interoperability within Web3. Join us as we delve into how EVVM redefines infrastructure for developers, enterprises, and end-users alike.🌐 Useful LinksEVVM: https://www.evvm.org/EVVM Docs: https://www.evvm.info/docs/intro🎙️ FeaturingGuest Speaker: German Abal: https://twitter.com/ariutokintumiArturo: https://twitter.com/0xVatojistro: https://twitter.com/jistro👥 ECH Institute TeamHost: Pooja Ranjan – https://twitter.com/poojaranjan19Podcast Producer: Akash – https://twitter.com/lookupforskyCoordinator: Meenakshi Singh – https://twitter.com/Meenakshiy2k🕒 Chapters00:00 - Introduction01:40 - Welcome German, Arturo, and jistro (Kevin) to EPD 31.02:30 - Guest introductions and their journeys into the Ethereum ecosystem.06:20 - Deep dive: What problems does EVVM solve (Compliance, Privacy, Gas)?08:35 - How EVVM works12:10 - Institutional use cases13:45 - Futureproofing15:35 - Architecture17:15 - Privacy layers19:50 - UX abstraction22:00 - Demo: Deploying an EVVM instance via CLI.23:45 - Demo: ZK Vault deposits and split withdrawals.26:05 - Infra comparison: EVVM vs. Traditional L2s28:30 - Current progress: Deployments on Base, Arbitrum, Monad, and more.29:40 - Demo: X402 payment requirements for AI agents.32:55 - Use Case: Non-custodial limit orders and DeFi security.35:15 - The EVVM suite: Scaffold-EVVM, CLI deployer, and rewards.39:00 - Mainnet roadmap and security auditing process.42:40 - ZK Proofs for identity and regulatory acceptance.44:30 - Removing the gas blocker for end-user adoption.46:00 - Explaining "Fishers" and the incentive network.49:40 - Upgradability and migration paths for enterprises.52:45 - Vision54:55 - Rapid Fire Round:56:45 - The potential for high-concurrency on-chain gaming.1:00:15 - Closing🌐 Official Websites• ECH Institute – https://echinstitute.org/💸 Support ECH InstituteDonate: https://www.ethcatherders.com/donate📲 Follow ECH InstituteX/Twitter: https://twitter.com/ECHInstituteWarpcast: https://warpcast.com/ethcatherdersMedium: https://medium.com/ethereum-cat-herdersDiscord: https://discord.gg/H2eYpKCxxm#Ethereum #EVVM #BlockchainPrivacy #Web3 #ECHInstitute #EcosystemProjectDemo

The conversation covers Devnet updates and issues, engine API changes, and an account abstraction proposal. The Devnet updates include issues with gas accounting and execution spec changes. The engine API changes involve adjustments to block hash handling and optimization in the fog choice update. The account abstraction proposal introduces a new approach to account obstructions through NFTs, key rotation, and gas sponsorship. The conversation covered topics related to stream transactions, native account abstraction, scheme transactions, post-quantum solutions, design iteration, use case clarification, political weight, client preferences, history pruning targets and mechanisms, network health, data retention, and RPC method integration. The discussion emphasized the importance of native account abstraction in Ethereum, the challenges in communicating use cases, and the need for consensus on history pruning targets and mechanisms. The conversation also highlighted the considerations for network health, performance improvement, and client flexibility in defining history pruning targets.TakeawaysDevnet updates and issuesEngine API changesAccount Abstraction proposal Native account abstraction in EthereumHistory pruning targets and mechanismsChapters00:00 Devnet Updates and Issues13:21 Engine API Changes28:44 Account Abstraction Proposal43:21 Stream Transactions and CFI50:10 Post-Quantum Solutions and Crypto Agility55:23 Challenges in Communicating Use Cases01:00:28 History Pruning Targets and Divergence01:06:20 History Pruning and Data Retention01:11:54 History Pruning and Disk Footprint