From 4534f1e30bc55025c7ca5b871e4788173fdfdba5 Mon Sep 17 00:00:00 2001
From: Lion - dapplion <35266934+dapplion@users.noreply.github.com>
Date: Thu, 14 Sep 2023 18:47:25 +0200
Subject: [PATCH] Update EIP-7514: Update eip-7514 constant name

Merged by EIP-Bot.
---
 EIPS/eip-7514.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/EIPS/eip-7514.md b/EIPS/eip-7514.md
index f30b4a6627cfad..3a2eaad6213b6e 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` | 8 |
+| `MAX_PER_EPOCH_ACTIVATION_CHURN_LIMIT` | 8 |
 
 ### Execution layer
 
@@ -40,7 +40,8 @@ This requires no changes to the Execution Layer.
 
 ### Consensus layer
 
-- Modify `get_validator_churn_limit` function adding an upper bound `MAX_PER_EPOCH_CHURN_LIMIT`
+- Add `get_validator_activation_churn_limit` with upper bound `MAX_PER_EPOCH_ACTIVATION_CHURN_LIMIT`
+- Modify `process_registry_updates` to use bounded activation 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).