fix: backport #21673 — prevent HA peer proposals from blocking equivocation in duplicate proposal test#21693
Open
AztecBot wants to merge 6 commits intobackport-to-v4-next-stagingfrom
Open
Conversation
…n in duplicate proposal test (#21673) - WITH CONFLICTS
ae4789b to
f6ccf4e
Compare
spalladino
approved these changes
Mar 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Backport of #21673 to v4-next.
Adds
dontStartSequencer: trueandskipPushProposedBlocksToArchiver: trueto the malicious nodes in theduplicate_proposal_slashe2e test. This prevents HA peer proposals from being added to the archiver, so both malicious nodes build their own blocks instead of one yielding to the other.Note: v4-next also needed
dontStartSequencer: true(from PR #21603) which was already onnextwhen the original PR was merged, so this backport includes both properties.Conflict Resolution
The cherry-pick conflicted because v4-next lacked the
dontStartSequencer: trueline added by PR #21603. Resolution was to accept both new properties (dontStartSequencerandskipPushProposedBlocksToArchiver).Commits
Test plan
duplicate_proposal_slashe2e test should pass with these changes