From cd246260354e098353061d5e7d3bc4d969ecdf81 Mon Sep 17 00:00:00 2001 From: syjn99 Date: Mon, 12 Aug 2024 13:05:26 +0900 Subject: [PATCH] Update EIP-7732: fix typos --- EIPS/eip-7732.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/EIPS/eip-7732.md b/EIPS/eip-7732.md index 21f03422cec7c0..57c966bc095dcc 100644 --- a/EIPS/eip-7732.md +++ b/EIPS/eip-7732.md @@ -120,7 +120,7 @@ The `BeaconState` container is modified with the addition of: - `latest_block_hash`, of type `Hash32`, to track the blockhash of the last execution payload in the blockchain. - `latest_full_slot`, of type `Slot`, to track the latest slot in which an execution payload was included. -- `latest_widthdrawals_root` of type `Root` to track the hash tree root of the latests withdrawals deducted in the beacon chain when processing a `SignedBeaconBlock`. +- `latest_withdrawals_root` of type `Root` to track the hash tree root of the latest withdrawals deducted in the beacon chain when processing a `SignedBeaconBlock`. The `BeaconBlockBody` is modified with the addition of: @@ -133,7 +133,7 @@ State transition logic is modified by: - A new beacon state getter `get_ptc` returns the PTC members for a given slot. - `get_attesting_indices` is modified to not return the beacon committee members that are included in the PTC. -- `process_withdrawals` is modified as follows. Withdrawals are obtained directly from the beacon state instead of the execution payload. They are deducted from the beacon chain. The beacon state `latest_widthdrawals_root` is updated with the HTR of this list. The next execution payload MUST include withdrawals matching the `state.latest_withdrawals_root`. +- `process_withdrawals` is modified as follows. Withdrawals are obtained directly from the beacon state instead of the execution payload. They are deducted from the beacon chain. The beacon state `latest_withdrawals_root` is updated with the HTR of this list. The next execution payload MUST include withdrawals matching the `state.latest_withdrawals_root`. - `process_execution_payload` is removed from `process_block`. Instead a new function `process_execution_payload_header` is included, this function validates the `SignedExecutionPayloadHeader` included in the `BeaconBlockBody` and transfers the payment from the builder's balance to the proposer. - `process_deposit_request` is removed from `process_operations` and deferred until `process_execution_payload`. - `process_withdrawal_request` is removed from `process_operations` and deferred until `process_execution_payload`. @@ -232,7 +232,7 @@ When a builder reveals an expected payload and the PTC achieved consensus that i Similarly, when a builder reveals a *payload withheld* message and the PTC achieved consensus by having at least `PAYLOAD_TIMELY_THRESHOLD` votes for `PAYLOAD_WITHHELD`, then the parent consensus block receives a boost equivalent to 40% of the beacon committee. Given the `(Block, Slot)` nature of fork choice voting, this boost counts **against** the consensus block containing the builder's commitment. -Both these boosts are present to guarantee the Builder's reveal and withhold safety under the parameters described in the [Secutiry Considerations](#security-considerations) section. +Both these boosts are present to guarantee the Builder's reveal and withhold safety under the parameters described in the [Security Considerations](#security-considerations) section. ### PTC equivocations