diff --git a/EIPS/eip-7514.md b/EIPS/eip-7514.md index 01a0206107d54..f30b4a6627cfa 100644 --- a/EIPS/eip-7514.md +++ b/EIPS/eip-7514.md @@ -32,7 +32,7 @@ This EIP does not attempt to do this, but to allow more time for the community t | Name | Value | | ---- | ----- | -| `MAX_PER_EPOCH_CHURN_LIMIT` | 12 | +| `MAX_PER_EPOCH_CHURN_LIMIT` | 8 | ### Execution layer @@ -42,6 +42,8 @@ This requires no changes to the Execution Layer. - Modify `get_validator_churn_limit` function adding an upper bound `MAX_PER_EPOCH_CHURN_LIMIT` +The full specification of the proposed change can be found in [`/_features/eip7514/beacon-chain.md`](https://github.com/ethereum/consensus-specs/blob/a56c4d026ff4fd39cbd77b7b8545eae719613018/specs/_features/eip7514/beacon_chain.md). + ## Rationale ### `MAX_PER_EPOCH_CHURN_LIMIT` value @@ -70,29 +72,7 @@ Depending on the specific constant selection the churn can _decrease_ at the act | 6 | Dec 01, 2024 | Oct 26, 2026 | Sep 20, 2028 | | 4 | Apr 02, 2025 | Feb 07, 2028 | Dec 15, 2030 | -#### `MAX_PER_EPOCH_CHURN_LIMIT` activation date: Jul 01, 2024 - -| Max Churn Limit | 50% ETH staked | 75% ETH staked | 100% ETH staked | -|------------------:|:-----------------|:-----------------|:------------------| -| inf | reached | Sep 25, 2024 | Dec 18, 2024 | -| 16 | reached | Jan 14, 2025 | Oct 02, 2025 | -| 12 | reached | Mar 21, 2025 | Mar 04, 2026 | -| 8 | reached | Jul 31, 2025 | Jan 03, 2027 | -| 6 | reached | Dec 10, 2025 | Nov 05, 2027 | -| 4 | reached | Aug 31, 2026 | Jul 08, 2029 | - -#### `MAX_PER_EPOCH_CHURN_LIMIT` activation date: Oct 01, 2024 - -| Max Churn Limit | 50% ETH staked | 75% ETH staked | 100% ETH staked | -|------------------:|:-----------------|:-----------------|:------------------| -| inf | reached | reached | Dec 18, 2024 | -| 16 | reached | reached | Jun 03, 2025 | -| 12 | reached | reached | Aug 23, 2025 | -| 8 | reached | reached | Feb 03, 2026 | -| 6 | reached | reached | Jul 16, 2026 | -| 4 | reached | reached | Jun 08, 2027 | - -Assuming that the earliest the next fork can happen is at the start of 2024 Q3, a value of 12 provides a significant reduction in projected size without causing a big drop in churn at a projected Dencun fork date. +Assuming that the earliest the next fork can happen is at the start of 2024 Q3, a value of 8 provides a significant reduction in projected size without causing a big drop in churn at a projected Dencun fork date. A value of 8 prevents reaching a level of 50% ETH staked for at least 1 full year even with a delayed dencun fork. ## Backwards Compatibility