Update op reth v1.9.3 #659
Open
Conversation
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
Clarifies required Docker/Compose versions and adds official install links to prevent 'docker compose' not found issues.
This change updates the OP_RETH_COMMIT and OP_RETH_TAG variables to point to release v1.9.3. The v1.9.3 release is an OpStack patch that fixes rollup‑boost by adding the Jovian fields to the payload ID and includes updated superchain‑registry timestamps. Updating these variables ensures the Base node stays compatible with upcoming Jovian hard fork changes and improves overall stability.
Collaborator
🟡 Heimdall Review Status
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This change updates the OP_RETH_COMMIT and OP_RETH_TAG variables to point to release v1.9.3. The v1.9.3 release is an OpStack patch that fixes rollup‑boost by adding the Jovian fields to the payload ID and includes updated superchain‑registry timestamps. Updating these variables ensures the Base node stays compatible with upcoming Jovian hard fork changes and improves overall stability.