Review block time reporting

Open

#5,943 opened on Sep 7, 2023 2 comments 0 reactions 0 assignees View on GitHub

meta-discussion meta-feature-request prio-high scope-performance

Dominant language: TypeScript
Stars: 1.4k
Forks: 483
Avg merge: 1d 16h
Merged PRs (30d): 150

Description

### Problem description

Codex performed a big blocks experiment and got divergent results from each implementation. We should
- Check with codex to learn what signal are they using: sse, logs, etc
- Get to consensus with clients on when are those signals emitted (recieved on gossip, processed, imported)

Background: https://www.youtube.com/live/zODMnGxQBG0?si=PHBmbeCsvFyPq1Ye

![image](https://github.com/ChainSafe/lodestar/assets/35266934/f4eb05ad-2f3b-463e-87c5-0d0909330b12)

More references:
- PM issue with summary https://github.com/ethereum/pm/issues/854#issuecomment-1709670938
- Notebook with charts on block arrival time https://colab.research.google.com/drive/1GrI6JaPZCTCmnW30YYXPs-MjA866jjXC

![Untitled](https://github.com/ChainSafe/lodestar/assets/35266934/63270e41-5d1e-48eb-b270-f5ee058c0201)

### Solution description

### Additional context

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Review block time reporting

Description

Contributor guide

Assessment

Get new issues in your inbox