EIP-6811 Ethereum on the Moon: Ten-Minute Blocks (To The Moon—10 Minute Blocks)
No call decision · Consensus & staking · EIP status Stagnant · created 2023-04-01
A proposal to extend the block interval from 12 seconds to 600 seconds so that Ethereum validation can work on the Moon and other extraterrestrial bodies, raising validator rewards and the gas limit by 50x, and changing the number of blocks per epoch from 4 to 2.
Why it is needed
A validator located on the lunar surface experiences a communication delay of about 1.25 seconds due to the speed of light. At the current 12-second block interval, this delay alone makes it hard for that validator to stay synchronized with block production timing, putting it at risk of gradually entering a leaking state and eventually being ejected from the Earth chain. Furthermore, if more than one-third of validators relocate to the Moon or other distant locations, they could end up following their own fork separate from the Earth chain, ejecting the Earth chain and finalizing their own chain independently. This proposal argues for lengthening the block interval itself to prevent this situation.
What changes
Today
- Current block interval: 12 seconds
- Current validator reward level
- Current blocks per epoch: 4
- Current block gas limit value
After EIP-6811
- Extend block interval to 600 seconds (10 minutes)
- Raise validator rewards by 50x
- Reduce blocks per epoch to 2
- Raise block gas limit by 50x
Who is affected
- Validators verifying from off-Earth locations such as the Moon: The roughly 1.25-second communication delay caused by the speed of light risked sync failure and ejection under the existing 12-second block interval, but lengthening the block interval reduces this risk.
- Wallet & app developers: Applications that expected transactions to be included within a short window can no longer rely on that assumption and must move to what the proposal calls 'planetary rollups.'
- L2s and rollups: The problem of synchronizing rollups across different celestial bodies is left outside the scope of this proposal, remaining a separate challenge to be solved.
- All validators: Because rewards and the gas limit both increase by the same 50x factor, the reward received per unit time and the overall scale of throughput are preserved.
In depth
Changing the block interval from 12 seconds to 600 seconds
The specification requires changing the time between blocks from 12 seconds to 600 seconds (10 minutes). The Motivation section explains that a validator on the lunar surface experiences a communication delay of about 1.25 seconds due to the speed of light, and at the existing 12-second interval this delay causes sync problems that can put the validator into a leaking state and lead to ejection from the Earth chain. It further adds that if more than one-third of validators move to the Moon or similar locations, there is a risk they follow their own fork, eject the Earth chain, and finalize their own chain.
Raising validator rewards and the gas limit by 50x
The specification requires raising the validator reward per block by 50x. The Rationale section explains that because the block interval has increased by 50x (from 12 seconds to 600 seconds), rewards are increased by the same factor to keep the total reward per unit time unchanged. For the same reason, the block gas limit is also raised by 50x, adjusting the amount of computation that can be processed per block to match the longer block interval.
Reducing blocks per epoch from 4 to 2
The specification requires reducing the number of blocks per epoch from 4 to 2. The Rationale section explains that this adjustment is meant to achieve finality within a reasonable amount of time.
Backwards compatibility and 'planetary rollups'
The Backwards Compatibility section points out that many applications expect mainnet transactions to be included within a short window, and that this will no longer hold once this proposal is adopted. It suggests that such applications should transition to 'planetary rollups,' while explicitly stating that synchronizing rollups across different celestial bodies is outside the scope of this proposal.
Security review and testing are empty
The Security Considerations section consists of a single sentence, 'Definitely needs discussion,' with no concrete security analysis provided. The Test Cases section is likewise empty, marked only as 'TODO.'
Current status
This EIP was created on April 1, 2023, and its current status is Stagnant. The author is Pandapip1, and the copyright has been waived under CC0. Call records show no decision to include this proposal in a fork.