From b7deef16293916a0fa03c00544aac0b5ea43540d Mon Sep 17 00:00:00 2001 From: Mikhail Kalinin Date: Thu, 23 Sep 2021 13:50:46 +0600 Subject: [PATCH] Clarity which state should be used in prepare_payload in a better way --- specs/merge/validator.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/specs/merge/validator.md b/specs/merge/validator.md index 4500d610c..dc67997c7 100644 --- a/specs/merge/validator.md +++ b/specs/merge/validator.md @@ -83,10 +83,10 @@ All validator responsibilities remain unchanged other than those noted below. Na ##### ExecutionPayload -To obtain an execution payload, the proposer of a block must take the following actions: +To obtain an execution payload, a block proposer bulding a block on top of a `state` must take the following actions: 1. Set `payload_id = prepare_execution_payload(state, pow_chain, fee_recipient, execution_engine)`, where: - * `state` is the state for which `is_proposer(state, validator_index)` returns `True` + * `state` is the state object after applying `process_slots(state, slot)` transition to the resulting state of the parent block processing * `pow_chain` is a list that abstractly represents all blocks in the PoW chain * `fee_recipient` is the value suggested to be used for the `coinbase` field of the execution payload