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

Redundant attester duty fetch on node's first startup epoch #1714

Open
olegshmuelov opened this issue Sep 8, 2024 · 0 comments · May be fixed by #1725
Open

Redundant attester duty fetch on node's first startup epoch #1714

olegshmuelov opened this issue Sep 8, 2024 · 0 comments · May be fixed by #1725
Assignees
Labels
alan bug Something isn't working

Comments

@olegshmuelov
Copy link
Contributor

Describe the bug
When a node is started during the first half of an epoch, it redundantly fetches attester duties for the next epoch in slots 16 and 17. This causes unnecessary duty fetches earlier than expected.
could be the same is happening for sync committee duties.

To Reproduce
Start the node on slot position 1-15.
Duties for the next will be fetched on on slot position 16 and slot position 17

Expected behavior
Duties should be fetched only once on slot position #17

@olegshmuelov olegshmuelov added bug Something isn't working alan labels Sep 8, 2024
@olegshmuelov olegshmuelov pinned this issue Sep 9, 2024
@olegshmuelov olegshmuelov unpinned this issue Sep 9, 2024
@olegshmuelov olegshmuelov self-assigned this Sep 12, 2024
olegshmuelov added a commit that referenced this issue Sep 15, 2024
@olegshmuelov olegshmuelov linked a pull request Sep 15, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
alan bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant