Skip to content

Conversation

@hopinheimer
Copy link
Member

addresses #7820

I haven't done benches for the change in kurtosis but post results soon

@hopinheimer hopinheimer self-assigned this Aug 18, 2025
@hopinheimer hopinheimer added the val-client Relates to the validator client binary label Aug 18, 2025
@jimmygchen jimmygchen added the waiting-on-author The reviewer has suggested changes and awaits thier implementation. label Sep 10, 2025
@hopinheimer hopinheimer added ready-for-review The code is ready for review waiting-on-author The reviewer has suggested changes and awaits thier implementation. and removed waiting-on-author The reviewer has suggested changes and awaits thier implementation. ready-for-review The code is ready for review labels Sep 19, 2025
@hopinheimer hopinheimer removed the waiting-on-author The reviewer has suggested changes and awaits thier implementation. label Sep 20, 2025
@hopinheimer hopinheimer added the ready-for-review The code is ready for review label Sep 20, 2025
@michaelsproul michaelsproul added the v8.1.0 Post-Fulu release label Oct 15, 2025
@hopinheimer hopinheimer added ready-for-review The code is ready for review and removed waiting-on-author The reviewer has suggested changes and awaits thier implementation. labels Dec 17, 2025
@mergify
Copy link

mergify bot commented Jan 15, 2026

Some required checks have failed. Could you please take a look @hopinheimer? 🙏

@mergify mergify bot added waiting-on-author The reviewer has suggested changes and awaits thier implementation. and removed ready-for-review The code is ready for review labels Jan 15, 2026
let mut last_slot = self.latest_attested_slot.lock().await;

if current_slot <= *last_slot {
debug!(?current_slot, "Attestation already initiated for the slot");
Copy link
Member

Choose a reason for hiding this comment

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

This log is a bit noisy, it's happening even on my VC with only a single validator, and at slots my validator is not even attesting.

I think the flow is:

  • Head event arrives
  • Trigger attestation service
  • Nothing to do (not an attester), update latest slot
  • Go round the loop again
  • Still the same slot, so wait for slot + 1/3
  • 1/3 of slot arrives, we've already set last_slot -> log message

Maybe we should add a sleep at the end of this loop until the next slot so that we don't wrap round like this

Copy link
Member

Choose a reason for hiding this comment

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

Maybe the sleep should be until the start of the original slot + 1 actually, just in case the attestation process takes a long time. We don't want "next slot" to actually be slot + 2 by the time this calculation is done

@hopinheimer hopinheimer added ready-for-review The code is ready for review and removed waiting-on-author The reviewer has suggested changes and awaits thier implementation. labels Jan 19, 2026
@michaelsproul michaelsproul mentioned this pull request Jan 20, 2026
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-for-review The code is ready for review v8.1.0 Post-Fulu release val-client Relates to the validator client binary

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants