fix: sets op-node sequencer/verifier confs to 2/1 #141
Conversation
This file contains 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
zhwrd
force-pushed
the
zhwrd/op-node-confs-0
branch
from
38e8604 to
a9814be
Compare
zhwrd
changed the title
zhwrd
force-pushed
the
zhwrd/op-node-confs-0
branch
from
a9814be to
3ed2c87
Compare
mslipper
approved these changes
Jan 23, 2025
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.
l1.trustrpcbut now in some cases op-node times out waiting for enough confs to read the systemconfig (in particular when using pectra l1 geth test image?)