status-im
/
eth2.0-specs
mirror of https://github.com/status-im/eth2.0-specs.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Clarity which state should be used in prepare_payload in a better way

This commit is contained in:
Mikhail Kalinin 2021-09-23 13:50:46 +06:00
parent 7ef938da77
commit b7deef1629
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
specs/merge/validator.md
View File

@ -83,10 +83,10 @@ All validator responsibilities remain unchanged other than those noted below. Na
##### ExecutionPayload ##### 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: 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 * `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 * `fee_recipient` is the value suggested to be used for the `coinbase` field of the execution payload