Etan Kissling a84ab5d47f validate `fork_version` as light client (#3459) ... The spec does not provide code for validating the `fork_version` field of `LightClientUpdate`. However, we can use our own logic for additional validation of that field. The spec's python test suite sets up states that do not follow the fork schedule (e.g., that use Altair fork version before Altair fork epoch), which complicates upstreaming this as code.		2022-03-04 17:09:33 +01:00
..
all_altair_fixtures.nim	add Bellatrix fork and transition tests; "Ethereum Foundation" -> EF (#3242)	2022-01-05 09:42:56 +01:00
test_fixture_fork.nim	fix Altair fork tests in minimal preset (#3163)	2021-12-06 05:56:46 +00:00
test_fixture_merkle_single_proof.nim	var => let in specs/ and tests/ (#3425)	2022-02-20 20:13:06 +00:00
test_fixture_operations.nim	var => let in specs/ and tests/ (#3425)	2022-02-20 20:13:06 +00:00
test_fixture_rewards.nim	[ncli_db] bugfix: take into account finalization delay in reward calc post Altair	2022-01-28 12:03:23 +02:00
test_fixture_sanity_blocks.nim	move `state_transition` to `Result` (#3284)	2022-01-17 12:19:58 +01:00
test_fixture_sanity_slots.nim	move `state_transition` to `Result` (#3284)	2022-01-17 12:19:58 +01:00
test_fixture_ssz_consensus_objects.nim	var => let in specs/ and tests/ (#3425)	2022-02-20 20:13:06 +00:00
test_fixture_state_transition_epoch.nim	var => let in specs/ and tests/ (#3425)	2022-02-20 20:13:06 +00:00
test_fixture_sync_protocol.nim	validate `fork_version` as light client (#3459)	2022-03-04 17:09:33 +01:00
test_fixture_transition.nim	var => let in specs/ and tests/ (#3425)	2022-02-20 20:13:06 +00:00