Refactor Sync Committee Logic and Add Unsafe Signer Verification #532
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
This pull request introduces the following changes:
Refactoring of Sync Committee Logic:
log_finality_update
andlog_optimistic_update
functions to correctly calculate thesize
of the sync committee and theparticipation
ratio. This ensures that the calculations are based on the correct sync committee size, improving the accuracy of the finality updates.Addition of Unsafe Signer Verification:
verify_unsafe_singer
in theOpStackClientBuilder
struct. This optional boolean field allows for the configuration of unsafe signer verification, enhancing the flexibility and security of the client builder.These changes aim to improve the overall functionality and security of the consensus mechanism. Please review the modifications and provide feedback.