mirror of
https://github.com/ethereum/consensus-specs.git
synced 2026-02-16 00:45:43 -05:00
c4dbd241ac
`LightClientUpdate` structures currently use different merkle proof root depending on the presence of `finalized_header`. By always rooting it in the same state (the `attested_header.state_root`), logic gets simpler. Caveats: - In periods of extended non-finality, `update.finalized_header` may now be outdated by several sync committee periods. The old implementation rejected such updates as the `next_sync_committee` in them was stale, but the new implementation can properly handle this case. - The `next_sync_committee` can no longer be considered finalized based on `is_finality_update`. Instead, waiting until `finalized_header` is in the `attested_header`'s sync committee period is now necessary. - Because `update.finalized_header > store.finalized_header` no longer holds (for updates with finality), an `is_better_update` helper is added to improve `best_valid_update` tracking (in the past, finalized updates with supermajority participation would always directly apply) This PR builds on prior work from: - @hwwhww at https://github.com/ethereum/consensus-specs/pull/2829
7 lines
228 B
Markdown
7 lines
228 B
Markdown
# Light client sync protocol tests
|
|
|
|
This series of tests provides reference test vectors for the light client sync protocol spec.
|
|
|
|
Handlers:
|
|
- `update_ranking`: see [`LightClientUpdate` ranking test format](./update_ranking.md)
|