eth2.0-specs/tests/core/pyspec/eth2spec
Etan Kissling c4dbd241ac
Root `next_sync_committee` in `attested_header`
`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
2022-07-01 14:49:24 -07:00
..
config Add `CONFIG_NAME` to configs 2021-12-29 13:02:36 +01:00
debug fix spacing for linter 2021-06-24 09:24:58 -07:00
gen_helpers Apply PR feedback from @ralexstokes 2021-10-07 16:04:06 +08:00
test Root `next_sync_committee` in `attested_header` 2022-07-01 14:49:24 -07:00
utils PR feedback from @ralexstokes and add single pubkey aggregate tests 2021-08-05 12:09:30 +08:00
VERSION.txt bump version.txt 2022-05-23 05:23:16 -06:00
__init__.py more explicit about version file location 2020-02-08 23:59:08 +01:00