Skill Guide

EVM internals, opcodes, and gas optimization analysis

Deep analysis of the Ethereum Virtual Machine's execution model, instruction set, and transaction cost mechanisms to write secure, performant, and economically efficient smart contracts.

Directly reduces operational costs (gas fees) for protocols and users while enhancing contract security and enabling novel designs like assembly-level optimizations. This skill translates to measurable cost savings and competitive advantages in DeFi and on-chain applications.

1 Careers

1 Categories

8.8 Avg Demand

25% Avg AI Risk

How to Learn EVM internals, opcodes, and gas optimization analysis

1. Solidity fundamentals and its compilation to bytecode. 2. The EVM stack machine model (stack, memory, storage). 3. Gas pricing of basic opcodes (SSTORE, SLOAD, CALL).

1. Comparative analysis of different Solidity compiler versions (0.8.x vs. 0.8.y) on bytecode output. 2. Profiling and optimizing real contracts using EVM trace tools (Tenderly, Foundry traces). 3. Common pitfalls: storage patterns, loop inefficiencies, and mispriced external calls.

1. Crafting inline assembly (Yul) for gas-critical loops and memory operations. 2. Designing contracts around EIPs (e.g., EIP-2929 cold/warm access). 3. Architecting upgradeable proxy patterns with minimal delegatecall overhead.

Practice Projects

Beginner

Project

Gas Profiling of a Standard ERC-20 Transfer

Scenario

You have a basic ERC-20 token contract. The team wants to reduce the gas cost of the `transfer` function by at least 5%.

How to Execute

1. Deploy the contract to a local fork (Anvil/Foundry). 2. Execute a `transfer` and use `debug_traceTransaction` to get the full opcode trace. 3. Analyze the trace for costly opcodes (e.g., SSTORE to non-zero). 4. Propose and test one optimization (e.g., changing a boolean flag to a packed uint8).

Intermediate

Project

Optimizing a Loop-Heavy On-Chain Data Structure

Scenario

A contract uses an array and a loop to check for duplicates. This is becoming prohibitively expensive as the array grows.

How to Execute

1. Identify the loop's gas complexity (O(n)). 2. Replace the array loop with a mapping (O(1) lookup) by changing the data structure. 3. Use Foundry's gas snapshots to measure before and after. 4. Document the storage layout impact and migration path if needed.

Advanced

Project

Minimal Proxy (EIP-1167) Factory with Custom Initialization

Scenario

Design a factory to deploy thousands of minimal proxy clones of a template contract, each with unique initial state, minimizing deployment and initialization gas.

How to Execute

1. Study EIP-1167 bytecode and the standard `createClone` function. 2. Write a custom factory that uses assembly to write the clone's initialization calldata directly into memory before the `CREATE` opcode. 3. Compare gas costs against a naive two-step deploy+initialize approach. 4. Audit the assembly for correctness and reentrancy risks.

Tools & Frameworks

Development & Profiling Frameworks

Foundry (Forge, Anvil, Cast)Hardhat with hardhat-gas-reporterTenderly Virtual TestNets

Used for writing, testing, and profiling smart contracts. Foundry's trace and snapshot tools are particularly potent for granular EVM analysis. Tenderly provides intuitive visual debugging of transactions.

Disassembly & Analysis Tools

EVM Disassembler (ethervm.io)evmdissolc --asm and --opcodes flags

Used to manually inspect and understand the raw bytecode and opcode sequences generated by the Solidity compiler, which is essential for low-level optimization.

Reference & Specifications

Ethereum Yellow Paper (Appendix G: Virtual Machine)EVM Opcodes Reference (evm.codes)EIP-2929 (Gas cost increases for state access)

The definitive sources for understanding opcode semantics, gas costs, and protocol-level rules that govern the EVM's behavior.

Interview Questions

Answer Strategy

Test knowledge of post-Berlin gas repricing and state access optimization. The candidate should define the cost difference (100 gas vs. 2100 gas), explain the 'accessed_addresses' and 'accessed_storage_keys' lists, and propose designs like using proxy patterns where implementation logic is shared, or batching state updates to keep frequently accessed slots in the same transaction context.

Answer Strategy

Tests practical assembly optimization and security awareness. The answer strategy should focus on the high cost of memory expansion and the optimization of caching the memory pointer in a local variable (stack) rather than recalculating it. The pitfall is the risk of pointer mismanagement leading to memory corruption. Sample: 'Optimization is caching the free memory pointer in a local variable to avoid repeated MLOAD. Pitfall: if not managed correctly, it can overwrite the free memory pointer, corrupting ABI-encoded data.'