Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Review block time reporting #5943

Open
dapplion opened this issue Sep 7, 2023 · 2 comments
Open

Review block time reporting #5943

dapplion opened this issue Sep 7, 2023 · 2 comments
Labels
meta-discussion Indicates a topic that requires input from various developers. meta-feature-request Issues to track feature requests. prio-high Resolve issues as soon as possible. scope-performance Performance issue and ideas to improve performance.

Comments

@dapplion
Copy link
Contributor

dapplion commented Sep 7, 2023 •
edited
Loading

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

More references:

Untitled

Solution description

/

Additional context

No response
@dapplion dapplion added the meta-feature-request Issues to track feature requests. label Sep 7, 2023
@philknows philknows mentioned this issue Sep 12, 2023
Closed
15 tasks
@philknows
Copy link
Member

Added to quarterly goals to ensure we follow up on this.

@philknows philknows added prio-high Resolve issues as soon as possible. scope-performance Performance issue and ideas to improve performance. labels Sep 12, 2023
@wemeetagain
Copy link
Member

this issue is about coming to consensus on exactly when the event should be emitted. (recieved on gossip, processed, imported, etc)

@philknows philknows added the meta-discussion Indicates a topic that requires input from various developers. label Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
meta-discussion Indicates a topic that requires input from various developers. meta-feature-request Issues to track feature requests. prio-high Resolve issues as soon as possible. scope-performance Performance issue and ideas to improve performance.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@wemeetagain @dapplion @philknows