Fireside Chat
summary
Tooling now shortens MVP timelines with web3.js and Foundry but tutorials and ZK tooling (Circom verification, Solidity-to-ZK libs) lag; proposal-level specifics include using an n−1 fork criterion to speed upgrades, targeting two forks a year, and raise minimum blob fee to align L1/L2 incentives so L1 captures a steady share of rollup revenue. Native rollups are defined as L1 providing the state transition function; practical gaps called out: wallet recovery standards, oracle/REST interoperability, and pragmatic compiler or library changes for safer upgrades.
AI-written summary · about
chapters (24)
- 0:00Introduction and Pragma Taipei reflections
- 1:19Evolution of Ethereum developer tooling
- 3:34Potential for Solidity-focused LLMs
- 4:10Emerging application trends in web3
- 6:25Discussion on platform lock-in and walled gardens
- 8:40Incentivizing open development practices
- 10:12Wallet standards and recovery mechanisms
- 12:24Ethereum Foundation's role in wallet development
- 15:24Emerging layers in Ethereum's tech stack
- 20:28Modernizing Solidity and smart contract patterns
- 23:22ZK integration and VM improvements
- 24:22Oracle functionality and external data access
- 26:45Developer experience with REST APIs
- 28:01Missing developer tools in Ethereum ecosystem
- 29:46Multi-VM support on L2s
- 31:35Reflections on EWASM and RISC-V potential
- 34:14Speeding up Ethereum upgrades
- 36:19Fork frequency and coordination challenges
- 37:25Prioritizing protocol improvements
- 39:36Native vs based rollups explained
- 43:03Blob pricing economics
- 46:14Improving governance signaling
- 49:22Protocol change reversibility
- 50:57Ethereum Foundation's evolving role
