SkelOT: Reusing AOT Compilation Across EVM Contract Families
SkelOT reuses one native AOT artifact per EVM contract family, cutting Base compile units by 47.5%.
Ahead-of-time EVM compilers such as revmc, evmone, and DTVM reuse artifacts only by code hash, even though factory, proxy, and template deployments share instruction structure and differ mainly in constants. Across Base, Ethereum, BSC, and Arbitrum, 23.1-47.6% of unique compilable bytecodes mapped to shared family skeletons in 10K-block windows. SkelOT, built on revmc and LLVM, compiles one native artifact per family and loads variant constants from a per-contract table. On a 10K-block Base corpus of 3.52 million transactions it cut compilation units 47.5%, artifact footprint 57.4%, and compile time 2.19x, with a 1.31x median per-contract speedup and byte-identical execution.
- 23.1-47.6% of bytecodes share family skeletons on four EVM chains.
- SkelOT cut Base compilation units 47.5% and artifact footprint 57.4%.
- Compile time fell 2.19x with byte-identical results versus per-hash AOT.
- Median runtime speedup was 1.31x across family members.
From the original article
1 min read at arxiv.orgAhead-of-time (AOT) compilers (e. g. , revmc, evmone, and DTVM) for the Ethereum Virtual Machine (EVM) reuse compilation artifacts at contract-code-hash granularity.
By Sipeng Xie · arxiv.org
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.