Michael Sproul 9667dc2f03 Implement checkpoint sync (#2244) ... ## Issue Addressed Closes #1891 Closes #1784 ## Proposed Changes Implement checkpoint sync for Lighthouse, enabling it to start from a weak subjectivity checkpoint. ## Additional Info - [x] Return unavailable status for out-of-range blocks requested by peers (#2561) - [x] Implement sync daemon for fetching historical blocks (#2561) - [x] Verify chain hashes (either in `historical_blocks.rs` or the calling module) - [x] Consistency check for initial block + state - [x] Fetch the initial state and block from a beacon node HTTP endpoint - [x] Don't crash fetching beacon states by slot from the API - [x] Background service for state reconstruction, triggered by CLI flag or API call. Considered out of scope for this PR: - Drop the requirement to provide the `--checkpoint-block` (this would require some pretty heavy refactoring of block verification) Co-authored-by: Diva M <divma@protonmail.com>		2021-09-22 00:37:28 +00:00
..
environment	Update sloggers to v2.0.2 (#2588)	2021-09-14 06:48:26 +00:00
src	Shutdown gracefully on panic (#2596)	2021-09-15 00:01:18 +00:00
tests	Implement checkpoint sync (#2244)	2021-09-22 00:37:28 +00:00
Cargo.toml	Update sloggers to v2.0.2 (#2588)	2021-09-14 06:48:26 +00:00