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

Fix restriction that only 300 validators can be processed for sync committee duties #31

Merged
merged 9 commits into from
Mar 14, 2023

Conversation

TobiWo
Copy link
Owner

@TobiWo TobiWo commented Mar 2, 2023

Summary

This PR fixes the restriction that only up to 300 validators could be fetched for attestation and sync committee duties. This was due to how much data you can send with the request to the beacon client.

However, to not pollute the screen with unnecessary attestation logs (e.g. for professional node operators) there is limit of 100 validators for which it is possible to log attestation duties. This behavior will be changed in a subsequent PR were new cli flags will be added (see this issue) and the remaining parameters will be reworked in general.

Further changes

  • Small refactoring of validator parser

Closes #16

@TobiWo TobiWo added the enhancement New feature or request label Mar 2, 2023
@TobiWo TobiWo changed the title Fix restriction that only 300 validators can be processed for sync committee duties Draft: Fix restriction that only 300 validators can be processed for sync committee duties Mar 2, 2023
@TobiWo TobiWo changed the title Draft: Fix restriction that only 300 validators can be processed for sync committee duties Fix restriction that only 300 validators can be processed for sync committee duties Mar 2, 2023
@TobiWo TobiWo marked this pull request as draft March 2, 2023 14:09
@TobiWo TobiWo force-pushed the feature/fix-300-validator-restriction branch 2 times, most recently from e7f88fa to fea3cde Compare March 5, 2023 12:09
* Add new constants for validator parsing
* Adapt validator count message constants
* Add new program related constants for fetching and parsing validators
* Delete unnecessary separate fetch function
* Refactor validator count function
@TobiWo TobiWo force-pushed the feature/fix-300-validator-restriction branch from fea3cde to 65990ed Compare March 5, 2023 12:33
@TobiWo TobiWo force-pushed the feature/fix-300-validator-restriction branch from 65990ed to 67d9b32 Compare March 5, 2023 12:52
@TobiWo TobiWo marked this pull request as ready for review March 5, 2023 13:02
@TobiWo TobiWo requested a review from LuisNaldo7 March 5, 2023 13:02
LuisNaldo7
LuisNaldo7 previously approved these changes Mar 10, 2023
* Add update for consensus client compatibility
* Updates todos
* Update ToC
@TobiWo TobiWo merged commit 44583d9 into main Mar 14, 2023
@TobiWo TobiWo deleted the feature/fix-300-validator-restriction branch March 14, 2023 07:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fix skipping duties check for attestation and sync committee duties if moren than 300 validators are supplied
2 participants