lighthouse/lcli
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
..
src Implement checkpoint sync (#2244) 2021-09-22 00:37:28 +00:00
.gitignore Move lcli out of the tests dir 2019-09-12 12:28:31 -04:00
Cargo.toml Implement checkpoint sync (#2244) 2021-09-22 00:37:28 +00:00
Dockerfile Add lcli Dockerfile and auto-build to CI (#2469) 2021-07-21 03:24:23 +00:00
README.md Refactor docs into mdbook (#547) 2019-10-02 11:04:56 +10:00

lcli

A command-line debugging tool, inspired by zcli.

Allows for replaying state transitions from SSZ files to assist in fault-finding.

Usage

$ cargo run --release -- --help