Skip to content

feat(op): pull chain config from superchain-registry github#19914

Closed
0xPenryn wants to merge 1 commit intoparadigmxyz:mainfrom
0xPenryn:pull-scr
Closed

feat(op): pull chain config from superchain-registry github#19914
0xPenryn wants to merge 1 commit intoparadigmxyz:mainfrom
0xPenryn:pull-scr

Conversation

@0xPenryn
Copy link
Copy Markdown

Updates the reth-optimism-chainspec crate, adding functionality to pull the latest chain configuration directly from the superchain registry. If the superchain registry is unreachable, it will fall back to the local chain configurations and follow the existing behavior.

This means that op-reth doesn't need to cut a new release to reflect updates to the superchain registry; rather, the node operator simply needs to restart op-reth and it will pull the latest config.

@emhane
Copy link
Copy Markdown
Collaborator

emhane commented Nov 24, 2025

is it really needed to wait for new release to pull the latest registry now? isn't it just a matter of replacing the json file on the specific path manually? agree though that it's cooler if this is done automatically.

@emhane emhane added the A-op-reth Related to Optimism and op-reth label Nov 24, 2025
@0xPenryn
Copy link
Copy Markdown
Author

0xPenryn commented Dec 2, 2025

is it really needed to wait for new release to pull the latest registry now? isn't it just a matter of replacing the json file on the specific path manually? agree though that it's cooler if this is done automatically.

Locally updating the files generated from the Superchain Registry is possible if you're building op-reth from source, but there are released binaries and Docker images for a reason. Besides, that solution is even more complex than just passing the genesis.json file in the --chain flag.

Most World Chain node operators use Docker images to run their nodes, and requiring them to pull an updated genesis file and pass that into the Docker image is exactly the friction that the Superchain Registry integration is designed to prevent. I'm simply trying to reduce that friction even further, and also remove the need for chain operators like us to ask for new releases just so the --chain worldchain flag works as intended.

Before this PR:

  1. Submit + merge PR to Superchain Registry
  2. Submit + merge PR to Reth pulling latest Superchain Registry
  3. Wait for Reth release
  4. Tell node operators to update to new version of op-reth

After this PR:

  1. Submit + merge PR to Superchain Registry
  2. Tell node operators to restart op-reth

@mattsse
Copy link
Copy Markdown
Collaborator

mattsse commented Feb 6, 2026

Closing this PR as op-reth has been moved to its own repository. See #21532 and the updated README for the new location. If this is still relevant, please re-open in the new op-reth repository. 🙏

@mattsse mattsse closed this Feb 6, 2026
@github-project-automation github-project-automation bot moved this from Backlog to Done in Reth Tracker Feb 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-op-reth Related to Optimism and op-reth

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants