Decoding the EVM A New Debugging Format for Smart Contracts
summary
Proposal for a standardized debugging format called Ethdebug that outputs compiler debug symbols so debuggers can map EVM bytecode back to high‑level types, variables and call boundaries; notes prior effort cost about $2 million to get only a decent debugger; identifies EVM-specific challenges like storage layout and strings shorter than a word having different encodings; working group produces JSON schemas, handles optimizer‑caused bytecode reuse, runs biweekly meetings and an immediate workshop to iterate the format.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 0:29Summary
- 2:37Debugging
- 5:09Debugging Data Format
- 8:55EVM Format Working Group
- 12:39Workshop
related talks
22mHow Decompilation Uncovers Smart Contract Vulnerabilities
15mIntelliJ Solidity Debugger
21mHitchhiker’s Guide to the EVM
23mGenerating EVM Bytecode from Yul in the new via IR Pipeline
46mWebAssembly (Digging a bit deeper)
30mConstructing A Dynamic CFG For EVM Based Smart Contracts
20mAugmenting EVMs with FHE to Enable New Use Cases
24mWhat’s in a VM? The Execution Engines Powering Web3’s Future