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

Drop address_change_broadcast #5287

Merged
merged 1 commit into from
Feb 29, 2024

Conversation

dapplion
Copy link
Collaborator

@dapplion dapplion commented Feb 24, 2024

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

@dapplion dapplion added the ready-for-review The code is ready for review label Feb 24, 2024
Copy link
Member

@michaelsproul michaelsproul left a 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

@michaelsproul michaelsproul added ready-for-merge This PR is ready to merge. and removed ready-for-review The code is ready for review labels Feb 25, 2024
@michaelsproul
Copy link
Member

@Mergifyio queue

Copy link

mergify bot commented Feb 25, 2024

queue

🛑 The pull request has been removed from the queue default

Pull request #5287 has been dequeued by a dequeue command.

You can take a look at Queue: Embarked in merge queue check runs for more details.

In case of a failure due to a flaky test, you should first retrigger the CI.
Then, re-embark the pull request into the merge queue by posting the comment
@mergifyio refresh on the pull request.

@michaelsproul
Copy link
Member

@Mergifyio dequeue

Copy link

mergify bot commented Feb 26, 2024

dequeue

✅ The pull request has been removed from the queue default

@michaelsproul
Copy link
Member

@Mergifyio requeue

Copy link

mergify bot commented Feb 26, 2024

requeue

✅ This pull request will be re-embarked automatically

The followup queue command will be automatically executed to re-embark the pull request

Copy link

mergify bot commented Feb 26, 2024

queue

🛑 The pull request has been removed from the queue default

The queue conditions cannot be satisfied due to failing checks.

You can take a look at Queue: Embarked in merge queue check runs for more details.

In case of a failure due to a flaky test, you should first retrigger the CI.
Then, re-embark the pull request into the merge queue by posting the comment
@mergifyio refresh on the pull request.

@michaelsproul
Copy link
Member

@Mergifyio requeue

Copy link

mergify bot commented Feb 28, 2024

requeue

✅ This pull request will be re-embarked automatically

The followup queue command will be automatically executed to re-embark the pull request

Copy link

mergify bot commented Feb 28, 2024

queue

✅ The pull request has been merged automatically

The pull request has been merged automatically at 7b65d38

mergify bot added a commit that referenced this pull request Feb 28, 2024
mergify bot added a commit that referenced this pull request Feb 29, 2024
@mergify mergify bot merged commit 7b65d38 into sigp:unstable Feb 29, 2024
28 of 29 checks passed
pawanjay176 pushed a commit to pawanjay176/lighthouse that referenced this pull request Mar 5, 2024
* Drop address_change_broadcast
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-for-merge This PR is ready to merge.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants