lighthouse/beacon_node/execution_layer/src
Paul Hauner cac3a66be4 Permit a null LVH from an INVALID response to newPayload (#4037)
## Issue Addressed

NA

## Proposed Changes

As discovered in #4034, Lighthouse is not accepting `latest_valid_hash == None` in an `INVALID` response to `newPayload`. The `null`/`None` response *was* illegal at one point, however it was added in https://github.com/ethereum/execution-apis/pull/254.

This PR brings Lighthouse in line with the standard and should fix the root cause of what #4034 patched around.

## Additional Info

NA
2023-03-03 04:12:50 +00:00
..
engine_api Clean capella (#4019) 2023-03-01 03:19:02 +00:00
test_utils Clean capella (#4019) 2023-03-01 03:19:02 +00:00
block_hash.rs Verify blockHash with withdrawals 2023-01-13 12:46:54 +11:00
engine_api.rs Clean capella (#4019) 2023-03-01 03:19:02 +00:00
engines.rs Suggestions for Capella execution_layer (#3983) 2023-02-17 11:58:33 +11:00
keccak.rs Verify execution block hashes during finalized sync (#3794) 2023-01-09 03:11:59 +00:00
lib.rs Clean capella (#4019) 2023-03-01 03:19:02 +00:00
metrics.rs Verify execution block hashes during finalized sync (#3794) 2023-01-09 03:11:59 +00:00
payload_cache.rs Builder Specs v0.2.0 (#3134) 2022-07-30 00:22:37 +00:00
payload_status.rs Permit a null LVH from an INVALID response to newPayload (#4037) 2023-03-03 04:12:50 +00:00