lambdaclass / lambdaclass/lambda_ethereum_consensus
Call `eth_syncing` to set the state of the Engine API.
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
We want to know if the Engine API is online or offline.
For example, lighthouse has the upcheck function (https://github.com/sigp/lighthouse/blob/441fc1691b69f9edc4bbdc6665f3efab16265c9b/beacon_node/execution_layer/src/engines.rs#L248) that periodically calls the execution api to get the current state. There are four internal states: Synced, Offline, Syncing, AuthFailed, but are exposed only as Online & Offline.
Need to dig deeper to investigate what are the implication if the Execution client is offline
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the referenced Lighthouse engines.rs upcheck implementation and investigate the Engine API's eth_syncing behavior. Determine the implications of an offline execution client, then define and implement the project's online/offline state handling once the expected mapping is agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100