Operation-level Concurrent Transaction Execution for Ethereum
summary
Proposes executing EVM transactions at the instruction level so only conflicting operations get re-run instead of whole transactions, implements it on go-ethereum with ~4K lines of code change and an operation-level log that records opcode inputs and outputs, replays 5 million blocks to compare against geth and reports 4.28x speedup (up to ~7x with prefetching), adds about 5% memory overhead, and validates correctness by bitwise state comparison across blocks.
AI-written summary · about
chapters (8)
- 0:00Parallel transaction execution
- 2:14Why parallel execution is needed
- 6:10Transaction-level concurrency limits
- 8:22Operation-level concurrency
- 15:34Operation knocks and re-execution
- 16:41Correctness and performance gains
- 19:58Use cases and future steps
- 21:46Q&A
related talks
18mVegeta: Enabling Parallel Smart Contract Execution in Leaderless Blockchains
14mAn Off-The-Chain Execution Environment for Scalable Testing and Profiling...
19mArcology - Parallel Execution - Unlimited Throughput
12mOptimistic Concurrency Control for Real-world Go Programs
21mComputation Layer: The Tricky Question of EVM Compatibility
27mOpen Transactional Actions: Interacting with non-transactional resources in S...
17mIs Ethereum Realtime Ready
13mEVVM Transactions & Functions for Beginners