-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Add back BLS changes from orphaned blocks #11822
Conversation
// It also filters out the attestations that is one epoch older as a defense so invalid attestations don't flow into the attestation pool. | ||
func (s *Service) saveOrphanedAtts(ctx context.Context, orphanedRoot [32]byte, newHeadRoot [32]byte) error { | ||
func (s *Service) saveOrphanedOperations(ctx context.Context, orphanedRoot [32]byte, newHeadRoot [32]byte) error { |
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.
Tbf this doesn't save all the operations, we should move slashing and exit to here in subsequent PR
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.
Yep, was working on it when vacations started :)
return errors.Wrap(err, "could not get BLSToExecutionChanges") | ||
} | ||
for _, c := range changes { | ||
s.cfg.BLSToExecPool.InsertBLSToExecChange(c) |
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.
What happens if the current branch already has these bls changes included ? Do we rely on our block packing to filter them out ?
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.
Insertion is a noop in this case
In case of a reorg, add back the BLS changes in the orphaned blocks.