You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Client software MAY skip an update of the forkchoice state and MUST NOT begin a payload build process if forkchoiceState.headBlockHash references a VALID ancestor of the head of canonical chain, i.e. the ancestor passed payload validation process and deemed VALID. In the case of such an event, client software MUST return {payloadStatus: {status: VALID, latestValidHash: forkchoiceState.headBlockHash, validationError: null}, payloadId: null}.
master
and #2423 have the same issueIf it already knows about the block:
nimbus-eth1/nimbus/beacon/api_handler/api_forkchoice.nim
Lines 154 to 163 in 0723464
then it returns and never processes the payload attributes to trigger payload generation later on in that function:
nimbus-eth1/nimbus/beacon/api_handler/api_forkchoice.nim
Lines 189 to 210 in 0723464
The text was updated successfully, but these errors were encountered: