-
Notifications
You must be signed in to change notification settings - Fork 784
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
Drop address_change_broadcast #5287
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.
Deleted code is music to my ears
@Mergifyio queue |
🛑 The pull request has been removed from the queue
|
@Mergifyio dequeue |
✅ The pull request has been removed from the queue
|
@Mergifyio requeue |
✅ This pull request will be re-embarked automaticallyThe followup |
🛑 The pull request has been removed from the queue
|
@Mergifyio requeue |
✅ This pull request will be re-embarked automaticallyThe followup |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at 7b65d38 |
* Drop address_change_broadcast
Issue Addressed
address_change_broadcast
was a mechanism to broadcast address changes of compromised stakers immediately after the fork. It served its purpose, now it can go. It's unlikely that this code will be useful to any future network. Networks that inherit beacon chain code have already forked into capella or will genesis post capella. This code is not necessary for backfill sync or any historical task.Proposed Changes
Drop address_change_broadcast