ChainSafe / ChainSafe/lodestar

Improve execution engine error logging

Open
#7,812 0 comments 0 reactions 0 assignees View on GitHub
meta-investigate scope-logging
Dominant language
TypeScript
Stars
1.4k
Forks
483
Avg merge
1d 16h
Merged PRs (30d)
150

Description

It seems that we don't emit any error log if EL is offline a lot of the time, eg. after start, we just have a log that states it's offline but not what exact error caused this.

Before Electra, we had the Eth1Provider that at least emitted a error log but now this is no longer the case due to EIP-6110 since we disabled Eth1 data polling.

Contributor guide

Open the contributing guide

Research direction

Start by tracing the execution engine's offline handling and compare it with the former Eth1Provider error logging path. Read the EIP-6110-related changes that disabled Eth1 data polling, then verify that the underlying execution-layer error is logged when the EL is offline, including after startup.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend, blockchain
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.