Fireside Chat
summary
Flow launches the Crescendo upgrade about a month ago and ships EVM compatibility by running the Ethereum VM as a pre‑compile EVM inside Cadence, not transpilation, using Flow’s native state tree for faster throughput. Network hits sub‑1s block time and ~7s finality with 500–1,000 TPS on Cadence, and the EVM path exposes VRF randomness and atomic multi‑call transactions (Cadence can bundle several EVM ops into one abortable script). Adoption reaction is positive from bridges, EVM apps, and Cadence devs.
AI-written summary · about
chapters (25)
- 0:00Introduction: Dieter Shirley & Flow's Major Upgrade
- 0:41Celebrating ETHGlobal's Impact & History
- 1:58Exploring Trade-offs in Blockchain Development
- 2:25Flow's Major Crescendo Network Upgrade
- 3:18How Flow Built an Early Data Availability Layer
- 3:55Flow's Improved Speed & Scalability Metrics
- 4:23Cadence 1.0: The Next-gen Smart Contract Language
- 4:52Introducing EVM Equivalence on Flow Blockchain
- 6:30Why Flow Adopted EVM Despite Cadence Advantages
- 8:06Technical Approach: Running EVM Inside Cadence
- 9:49How Flow EVM Uses Efficient Native State Storage
- 10:27Impact on Cross-chain Infrastructure Providers
- 10:57New Opportunities for EVM-first Developers
- 11:27Enhancing Solidity with Cadence Extensions
- 12:34Advanced Features Exclusive to Cadence vs. Solidity
- 13:38Example: Atomic Multi-call Transactions in Cadence
- 15:06Benefits for Native Cadence Developers from EVM
- 16:38How Flow Attracts Mainstream Crypto Adoption
- 17:40Advice on Building Consumer-friendly Blockchain Apps
- 20:03Balancing User Friction & Motivating Features
- 20:42Flow EVM: Implications for Ethereum Ecosystem
- 22:23The Superior Developer Experience of Cadence
- 22:56Flow Foundation's Long-term Vision & North Star
- 24:35Decentralization as Core Promise of Flow Blockchain
- 25:45Conclusion: Building Sustainable Apps on Flow
