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.

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

Specify 'valid' condition for block SSE event #404

Merged
merged 4 commits into from
Jan 17, 2024
Merged

Conversation

dapplion
Copy link
Collaborator

@dapplion dapplion commented Jan 9, 2024

From discussion in #349, specify to emit the block event only for blocks successfully imported on fork-choice. This condition includes: valid state transition (super-set of gossip rules) + valid/syncing execution + DA checks

@mcdee
Copy link
Contributor

mcdee commented Jan 9, 2024

I'm unsure of the point of the block event with this change. Won't it be emitted at basically the same time as the head event?

(The only time we wouldn't have overlap would be if the imported block wasn't made head, but not sure of the use case in that situation, either.)

@dapplion
Copy link
Collaborator Author

Won't it be emitted at basically the same time as the head event?

Not necessarily, not all newly imported blocks become head and re-orgs cause previously imported blocks to become head. The head event is very relevant on its own and orthogonal to the block event.

The rules of this PR align with what Lodestar and Lighthouse are doing right now. I haven't look into other implementations but I suspect it will be similar.

@rkapka
Copy link
Collaborator

rkapka commented Jan 15, 2024

Prysm does the same

@rolfyone
Copy link
Collaborator

I'm happy to clarify that wording, I guess my one caveat remains this is still not a great way of measuring anything time sensitive given these messages may be the lowest priority to action on a node, and the latency from that prioritisation etc...

Within the scope of whats proposed, I think this is a good clarification.

Copy link
Collaborator

@rolfyone rolfyone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@rolfyone
Copy link
Collaborator

@michaelsproul feedback?

Copy link
Collaborator

@michaelsproul michaelsproul left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@rolfyone rolfyone merged commit c458197 into master Jan 17, 2024
5 checks passed
@rolfyone rolfyone deleted the dapplion-patch-5 branch January 17, 2024 23:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants