The meeting covered updates on Glamsterdam DevNet 4, discussions on target gas limit PRs, and the introduction of a new tool called Disruptor. The conversation also delved into EIP 7684 and EIP 8148, addressing the custom sweep threshold for validators and the return deposits for distinct credentials. The conversation covers a range of EIPs and their potential impact on stakers, validators, and node operators. It also discusses the proposal to change the timing of the ACDC call to accommodate participants from different time zones.

Takeaways

• Glamsterdam DevNet 4 issues and investigations
• Discussion on target gas limit PRs
• Introduction of Disruptor tool for reorgs and network forks
• EIP 7684 and EIP 8148 for validators and return deposits EIP 8148 is supported by solo stakers, small operators, and institutional stakers due to its predictable cash flow benefits.
• EIP 8148's configurable cap is seen as useful for institutional stakers to manage risk limits and for solo stakers to consolidate into zero X02 validators.
• EIP 8148's automatic sweep mechanism is preferred for seamless reward accounting and better user experience.
• EIP 8061's increase in exit and consolidation churn is already implemented and tested, making it a candidate for SFI.
• The proposal to change the timing of the ACDC call to accommodate participants from different time zones is being considered for the next ACDC call as a trial.
• The decision to change the timing of the ACDC call will be based on the turnout and engagement of participants in the next call.

Chapters

• 00:00 Glamsterdam DevNet 4 Update
• 13:02 Discussion on Target Gas Limit PRs
• 21:35 Introduction of Disruptor Tool
• 38:10 EIP 7684 - Custom Sweep Threshold for Validators
• 48:08 EIP 8148: Predictable Cash Flow and Configurable Cap
• 53:24 EIP 8148: Automatic Sweep Mechanism
• 59:14 EIP 8148: Support from Node Operators
• 01:08:22 EIP 8080: Exits Using the Consolidation Queue
• 01:15:28 EIP 7688: Forward Compatible Consensus Data Structures
• 01:21:25 ACDC Call Timing Change Proposal

In this episode, Pooja Ranjan interviews Kevin Jones, a leader at Edge and Node and creator of 1Claw - an innovative infrastructure platform designed to secure AI agents and manage secrets. They explore the critical vulnerabilities in AI workflows, how 1Claw addresses these risks, and the future of AI security in decentralized ecosystems.

🎬 Related Content
Presentation: https://docs.google.com/presentation/d/1ChCPYfQYuvA7OteUdo2MwgMaiNu7SGo2XW18ePB3tvs/edit?usp=drivesdk

🌐 Useful Links
1Claw: https://1claw.xyz/

🎙️ Featuring
Guest Speaker:
Kevin Jones: https://twitter.com/cryptomastery_

👥 ECH Institute Team
Host: Pooja Ranjan – https://twitter.com/poojaranjan19
Podcast Producer: Akash – https://twitter.com/lookupforsky
Coordinator: Meenakshi Singh – https://twitter.com/Meenakshiy2k

🕒 Chapters
00:00 – The "8 Seconds" Problem: How AI accelerated malicious attacks
01:17 – Intro: Pooja Ranjan welcomes Kevin Jones (Edge & Node / 1Claw)
02:15 – Kevin’s Journey: From photography to Web2 infrastructure & Blockchain
03:50 – The "Aha Moment": API keys leaking into AI chat history
05:15 – Deep Dive: Why developers are accidentally exposing .env files
06:50 – Technical Solution: Using HSMs and Trusted Execution Environments (TEE)
09:55 – The LLM Proxy: Automated redaction and protecting against prompt injection
11:20 – Signing transactions without holding keys: The Intents API
13:42 – Developer Tooling: SDKs, CLIs, and open-source MCP tools
15:00 – Ecosystem Integrations: Cursor, Claude, CrewAI, and NVIDIA Nemo
17:12 – 1Claw Platform Demo: Registering an agent and creating secure vaults
23:30 – Supported Blockchains: Ethereum, Bitcoin, Solana, and more
27:25 – Human vs. Agent API keys: Managing access and audit logs
30:50 – EIP-712 Security: Restricting contract interactions for AI agents
35:05 – Real-World Use Cases: Secure Telegram Bots and BankerBots
37:30 – OIDC Federation: Hooking up agents directly to Claude API
42:02 – Rapid Fire Round: Biggest developer mistakes and Claude vs. GPT
45:20 – Final Summary: How to secure your agentic future

🌐 Official Websites
• ECH Institute – https://echinstitute.org/

💸 Support ECH Institute
Donate: https://www.echinstitute.org/donate

📲 Follow ECH Institute
X/Twitter: https://twitter.com/ECHInstitute
Warpcast: https://warpcast.com/ethcatherders
Medium: https://medium.com/ethereum-cat-herders
Discord: https://discord.gg/H2eYpKCxxm

#1Claw #Cybersecurity #ArtificialIntelligence #AI #Blockchain #Web3

The conversation covers updates on the Glam Amsterdam DevNet 4 launch, delegate inclusion on field calls, an update on EIP 7904, EAP 8188 discussing state tiering, and EAP 8182 proposing private transfers to Ethereum. The conversation covers innovative authentication methods, ZK proof and hardware wallets, credential proof separation, risk mitigation, synchronous composability, security and soundness mitigation, gas costs, supply side work, deactivation of self-destruct, and client feedback on execution API cases.

Takeaways

• Glam Amsterdam DevNet 4 launch updates
• Delegate inclusion on field calls
• Update on EIP 7904
• EAP 8188: State tiering
• EAP 8182: Private transfers to Ethereum Innovative authentication methods allow users to bring their own authentication, ZK proofs enable hardware wallet authorization, and credential proof separation ensures synchronous composability.
• Deactivation of self-destruct functionality requires careful consideration of potential impact on existing contracts and use cases.

Chapters

• 00:00 Glam Amsterdam DevNet 4 Launch
• 18:42 Update on 7904
• 37:30 EAP 8182: Private Transfers to Ethereum
• 43:15 Credential Proof Separation
• 57:17 Deactivation of Self-Destruct
• 01:11:23 Client Feedback on Execution API Cases

In this insightful interview, Eli Ben-Sasson, co-founder of Starkware, shares his journey from academia to blockchain innovation, discusses the significance of ZK-Starks in blockchain scalability and security, and explores the urgent need for quantum-resistant cryptography. Discover how these technologies are shaping the future of digital trust and privacy.

Zero Knowledge, Infinite Trust book isn't just about math; it’s a story about people, freedom, and the personal journeys that shaped the blockchain revolution.

🌐 Useful Links
https://blockchainthebook.com/
https://starkware.co/
https://www.starknet.io/

Get a special discount on 'Zero Knowledge, Infinite Trust' at https://www.blockchainthebook.com/show

🎙️ Featuring
Guest Speaker:
Eli Ben-Sasson: https://twitter.com/EliBenSasson

👥 ECH Institute Team
Host: Pooja Ranjan – https://twitter.com/poojaranjan19
Podcast Producer: Akash – https://twitter.com/lookupforsky

🕒 Chapters
00:00 – Preview
01:13 – Introduction to The Code Confession
01:34 – Introducing Eli Ben-Sasson
02:10 – The timing of the new book release and technical announcements.
03:38 – Eli’s transition from pure mathematics to Bitcoin and blockchain.
05:12 – Early interactions with OG Bitcoin developers like Greg Maxwell.
06:26 – The "red pill" moment
07:07 – The Shenzhen fish market story
10:07 – Understanding the "Quantum Iceberg" and the threat to current cryptography.
13:05 – Solutions for a post-quantum world
15:15 – Recent breakthroughs
18:12 – The urgency for Bitcoin governance to act on quantum resistance.
19:10 – Explaining STARKs vs. SNARKs
22:21 – The origins of the original STARK white paper and Eli’s deep conviction.
24:42 – The future of Ethereum scalability and Starknet’s central role.
26:21 – Unpacking the paradox
27:35 – About the book
29:28 – The experience of co-writing the book with Nathan Jeffay.
31:18 – Recommendations: Which chapters to read (and which to skip).
32:40 – Rapid-fire questions

🌐 Official Websites
• ECH Institute – https://echinstitute.org/

💸 Support ECH Institute
Donate: https://www.echinstitute.org/donate

📲 Follow ECH Institute
X/Twitter: https://twitter.com/ECHInstitute
Warpcast: https://warpcast.com/ethcatherders
Medium: https://medium.com/ethereum-cat-herders
Discord: https://discord.gg/H2eYpKCxxm

#ZeroKnowledge #ZKProofs #BlockchainTechnology #Cryptography #DigitalFuture

The conversation covers the agenda items for DevNet 4, including EIPs 70, 71, and 72, as well as the impact of the Engine API change on gas limit. It also discusses the limitation of deposit transactions on the EIA side, benchmarking and testing with Prism and Teku, and potential solutions for an overflow issue. The conversation covers the introduction of optional proofs for execution, collaboration with the broader community, sub-linear and stateless validation, opt-in proof generating and verifying modes, infrastructure and observability improvements, and standardizing the input for guest program execution. The discussion is divided into three main chapters: Introduction to Optional Proofs, Execution Proof Engine and API, and Execution Layer Specification.

Takeaways

• DevNet 4 includes EIPs 70, 71, and 72
• Discussion on Engine API change and its impact on gas limit
• Limiting the number of deposit transactions on the EIA side
• Benchmarking and testing with Prism and Teku
• Overflow issue and potential solutions Optional proofs for execution
• Collaboration with the broader community
• Sub-linear and stateless validation
• Opt-in proof generating and verifying modes
• Infrastructure and observability improvements
• Standardizing the input for guest program execution

Chapters

• 00:00 DevNet 4 Agenda Items
• 13:21 Engine API Change and Gas Limit
• 39:22 Deposit Transactions Limit
• 45:03 Overflow Issue and Solutions
• 54:54 Execution Proof Engine and API
• 01:23:15 Execution Layer Specification

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.

Takeaways

• Svalbard Interop Progress
• DevNet Updates Management of deep reorgs
• Limiting block size
• Proposal for self-destruct feature Self-destruct usage analysis
• EIP 8253 and EIP 7610 discussion

Chapters

• 00:00 Svalbard Interop Progress and DevNet-0
• 12:25 Debugging and Gas Accounting
• 36:02 Managing Deep Reorgs
• 01:03:40 Self-Destruct Usage Analysis
• 01: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.

Takeaways

• Nixo joins as co-lead of AllCoreDev
• DevNet updates and issues with EIP 8037 testing EIP 1837 concerns and complexities
• Performance optimization for ZK-AVM use cases
• Discussion on engine API performance and potential changes

Chapters

• 00:00 Introduction and Nixo's Co-Lead Announcement
• 57:26 EIP 1837 Concerns and Complexities
• 01:09:12 EIP Proposals and Mascot Selection for Glam-Sedam
• 01:14:52 EIP 7979 Proposal and Discussion
• 01:31:22 Engine API Performance Optimization for ZK-AVM Use Cases
  
  #Ethereum #ACDE #AllCoreDev

Agenda: https://github.com/ethereum/pm/issues/1990
Watch Video Version: ACDC 177

Takeaways

• Devnet Planning
• Consensus Layer Changes
• PR Merging and Testing Consensus Layer Changes
• Validator Deposit Vulnerability
• State Growth EIP Update

Chapters

• 00:00 Devnet Planning and PR Updates
• 34:59 PR Merging and Testing
• 51:14 Consensus Layer Changes and Queue Merging
• 56:57 Validator Deposit Vulnerability
• 01: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 Links
EVVM: https://www.evvm.org/
EVVM Docs: https://www.evvm.info/docs/intro

🎙️ Featuring
Guest Speaker:
German Abal: https://twitter.com/ariutokintumi
Arturo: https://twitter.com/0xVato
jistro: https://twitter.com/jistro

👥 ECH Institute Team
Host: Pooja Ranjan – https://twitter.com/poojaranjan19
Podcast Producer: Akash – https://twitter.com/lookupforsky
Coordinator: Meenakshi Singh – https://twitter.com/Meenakshiy2k

🕒 Chapters
00:00 - Introduction
01: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 works
12:10 - Institutional use cases
13:45 - Futureproofing
15:35 - Architecture
17:15 - Privacy layers
19:50 - UX abstraction
22:00 - Demo: Deploying an EVVM instance via CLI.
23:45 - Demo: ZK Vault deposits and split withdrawals.
26:05 - Infra comparison: EVVM vs. Traditional L2s
28: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 - Vision
54: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 Institute
Donate: https://www.ethcatherders.com/donate

📲 Follow ECH Institute
X/Twitter: https://twitter.com/ECHInstitute
Warpcast: https://warpcast.com/ethcatherders
Medium: https://medium.com/ethereum-cat-herders
Discord: 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.

Takeaways

• Devnet updates and issues
• Engine API changes
• Account Abstraction proposal Native account abstraction in Ethereum
• History pruning targets and mechanisms

Chapters

• 00:00 Devnet Updates and Issues
• 13:21 Engine API Changes
• 28:44 Account Abstraction Proposal
• 43:21 Stream Transactions and CFI
• 50:10 Post-Quantum Solutions and Crypto Agility
• 55:23 Challenges in Communicating Use Cases
• 01:00:28 History Pruning Targets and Divergence
• 01:06:20 History Pruning and Data Retention
• 01:11:54 History Pruning and Disk Footprint