Abstract
EIP-1559 introduces block elasticity—a mechanism allowing blocks to temporarily expand beyond their target size during demand spikes. Ethereum uses a 2x multiplier, but Ethereum Classic's smaller target gas limit (8M vs 30M) creates an opportunity to adopt a higher multiplier (4x, 16x, or 32x) to enable equivalent maximum transaction sizes. This research determines the highest safe elasticity multiplier for ETC given real-world hardware capabilities and network conditions.
Research Objectives
- What is the maximum safe elasticity multiplier for Ethereum Classic?
- What maximum transaction size does each multiplier enable, and how does this compare to Ethereum?
- What are the network stability implications of each multiplier option?
- What minimum hardware requirements does each multiplier impose on node operators?
Background
EIP-1559 Block Elasticity
EIP-1559 introduced variable block sizes where:
- Gas Target: The equilibrium level where basefee remains stable
- Gas Limit: Maximum capacity per block =
gas_target × elasticity_multiplier - Elasticity Multiplier: How much blocks can expand beyond target (Ethereum uses 2x)
With Ethereum's current 60M gas limit and 2x multiplier, the gas target is 30M. Since individual transactions can consume up to the full block gas limit, this enables large contract deployments and L2 state validation operations.
ETC's Opportunity
ETC's 8M gas target with a 2x multiplier would only allow 16M gas maximum transactions. By increasing the elasticity multiplier:
| Multiplier | Max Block Gas | Max TX Size | Comparison to ETH |
|---|---|---|---|
| 2x | 16M | 16M | 27% of ETH |
| 4x | 32M | 32M | 53% of ETH |
| 8x | 64M | 64M | 107% of ETH |
| 16x | 128M | 128M | 213% of ETH |
| 32x | 256M | 256M | 427% of ETH |
Prior Work
- EIP-1559 Specification
- Ethereum Gas Limit Increase Analysis
- Ethereum network performance studies during high-gas blocks
Methodology
Approach
- Theoretical Analysis: Calculate hardware requirements for processing blocks at each multiplier
- Client Benchmarking: Measure actual performance of Core-Geth and Besu (see Client Benchmarking)
- Network Simulation: Model block propagation delays at various sizes
- Historical Validation: Analyze ETC network behavior during historical high-gas periods
Tools & Resources
- Core-Geth and Besu test environments
- ETC mainnet archive nodes for historical data
- Network simulation framework
- Hardware test rigs at various specification levels
Assumptions & Constraints
- Node operators should not require hardware upgrades beyond current recommendations
- Block propagation must remain fast enough to maintain current uncle rates
- The multiplier must be safe under adversarial conditions (sustained max-size blocks)
Research Plan
Phase 1: Theoretical Bounds
- Calculate memory requirements for processing max-size blocks at each multiplier
- Estimate CPU cycles required for EVM execution at each gas level
- Model network bandwidth requirements for block propagation
- Document theoretical upper bound for safe operation
Phase 2: Empirical Benchmarking
- Coordinate with Client Benchmarking research
- Generate synthetic max-size blocks at each multiplier level
- Measure block processing time on reference hardware
- Test block propagation in controlled network environment
Phase 3: Network Analysis
- Coordinate with Network Analysis research
- Analyze historical ETC uncle rates vs block gas used
- Model expected uncle rate increase at each multiplier
- Identify network topology constraints
Phase 4: Recommendation
- Synthesize findings from all phases
- Propose recommended multiplier with supporting evidence
- Document fallback options and risk factors
- Prepare specification text for ECIP-1120
Expected Outcomes
- Recommended Elasticity Multiplier: A specific value (likely 4x, 8x, or 16x) with full justification
- Hardware Requirements Document: Minimum specifications for node operators at chosen multiplier
- Risk Assessment: Analysis of edge cases and potential failure modes
- Specification Parameters: Final values for
ELASTICITY_MULTIPLIERandMAX_GAS_LIMIT
Success Criteria
- Multiplier enables max transaction size ≥ Ethereum's 60M gas
- Block processing time remains under 1 second on mid-range hardware
- Projected uncle rate increase is < 0.5% under normal conditions
- No degradation of network stability under stress testing
- Consensus among client developers on safety of chosen value
Dependencies
- Client Performance Benchmarking - Empirical performance data
- Network Analysis - Network topology and propagation data
- Core-Geth and Besu development teams - Client-specific constraints
Current Status
Status: TODO
Progress Log
- 2025-11-27: Initial research plan drafted
- Pending: Begin Phase 1 theoretical analysis