-
Notifications
You must be signed in to change notification settings - Fork 810
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
[Merged by Bors] - Push naive attestations into op pool #1466
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me.
I'm under the impression a few of us have tested this on the public testnet. Given this assumption, I think we're good to go
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Michael-approved
Yep, I've been running it on our internal testnet and also on Medalla. bors r+ |
## Issue Addressed NA ## Proposed Changes - When producing a block, go and ensure every attestation in the naive aggregation pool is included in the operation pool. This should help us increase the number of useful attestations in a block. - Lift the `RwLock`s inside `NaiveAggregationPool` up into a single high-level lock. There were race conditions in the existing setup and it was hard to reason about. ## Additional Info NA
Pull request successfully merged into master. Build succeeded: |
Issue Addressed
NA
Proposed Changes
RwLock
s insideNaiveAggregationPool
up into a single high-level lock. There were race conditions in the existing setup and it was hard to reason about.Additional Info
NA