bcfde6e7df
## Issue Addressed NA ## Proposed Changes This PR will make Lighthouse return blocks with invalid payloads via the API with `execution_optimistic = true`. This seems a bit awkward, however I think it's better than returning a 404 or some other error. Let's consider the case where the only possible head is invalid (#3370 deals with this). In such a scenario all of the duties endpoints will start failing because the head is invalid. I think it would be better if the duties endpoints continue to work, because it's likely that even though the head is invalid the duties are still based upon valid blocks and we want the VC to have them cached. There's no risk to the VC here because we won't actually produce an attestation pointing to an invalid head. Ultimately, I don't think it's particularly important for us to distinguish between optimistic and invalid blocks on the API. Neither should be trusted and the only *real* reason that we track this is so we can try and fork around the invalid blocks. ## Additional Info - ~~Blocked on #3370~~ |
||
|---|---|---|
| .. | ||
| cached_tree_hash | ||
| fork_choice | ||
| int_to_bytes | ||
| merkle_proof | ||
| proto_array | ||
| safe_arith | ||
| serde_utils | ||
| ssz | ||
| ssz_derive | ||
| ssz_types | ||
| state_processing | ||
| swap_or_not_shuffle | ||
| tree_hash | ||
| tree_hash_derive | ||
| types | ||