[Feature] Add Check for Booting in Historic Mode. #43

New Issue

2022-05-19T12:32:16Z

abdulrabbani00 commented

2022-05-19 12:32:16 +00:00

(Migrated from github.com)

Overview
- Request
Potential Solution
- Alternative Solutions
Additional Context

Table of contents generated with markdown-toc

Overview

Requester: @abdulrabbani00
Epic Link: https://github.com/vulcanize/ipld-ethcl-indexer/issues/42

Request

We need to ensure that prior to starting historical processing we know which blocks the beacon server has. This is actually the first time in the code base where the ipld-ethcl-indexer application needs to differentiate logic for different beacon nodes.

For Lighthouse,

We will check the /lighthouse/database/info endpoint.
We need to ensure that anchor: null
We can capture the head_slot from /eth/v1/node/syncing. The head_slot indicates the latest slot we have, and indicates that we have every slot prior.
This number slot will be captured in the BeaconClient struct and will lazily be updated.

Potential Solution

Query the endpoint and run basic checks.

Alternative Solutions

Additional Context

- [Overview](#overview) - [Request](#request) - [Potential Solution](#potential-solution) - [Alternative Solutions](#alternative-solutions) - [Additional Context](#additional-context) <small><i><a href='http://ecotrust-canada.github.io/markdown-toc/'>Table of contents generated with markdown-toc</a></i></small> # Overview - **Requester**: @abdulrabbani00 - **Epic Link**: https://github.com/vulcanize/ipld-ethcl-indexer/issues/42 ## Request  We need to ensure that prior to starting historical processing we know which blocks the beacon server has. This is actually the first time in the code base where the `ipld-ethcl-indexer` application needs to differentiate logic for different beacon nodes. For Lighthouse, * We will check the `/lighthouse/database/info` endpoint. * We need to ensure that `anchor: null` * We can capture the `head_slot` from `/eth/v1/node/syncing`. The `head_slot` indicates the latest slot we have, and indicates that we have every slot prior. * This number slot will be captured in the `BeaconClient` struct and will lazily be updated. # Potential Solution  Query the endpoint and run basic checks. ## Alternative Solutions  # Additional Context

Sign in to join this conversation.

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/ipld-eth-beacon-indexer#43