op-node,op-program: source rollup-configs from superchain-registry

[protolambda]

Description

To make OP-Stack chain configurations available across OP-Stack client implementations, we are experimenting with a "superchain-registry": one place that hosts all superchain configurations, which can then be embedded into the software for convenience & OP-Stack wide rollout of config changes.

This depends on the op-geth superchain-registry integration

This will enable op-node users to pick any chain from the registered Superchains as chain to run the op-node with: no more manual rollup.json required. This simplifies the configuration-management: network upgrades can be specified in superchain-wide configuration.

rollup.json might change, but we plan to keep supporting manual configuration, for testing / bootstrap / customization purposes, the OP-Stack is open after all.

The op-program is not in production yet, and thus gets full access to the superchain-registry data.
The op-node is in production, and while the superchain-registry is experimental, does not expose the full selection of chains.

To access a configuration from the superchain-registry, add --beta.extra-networks to your selection of op-node flags, and then use --network to select a chain like normal.

The default-network configurations are tested to match the expected configurations, to ensure the op-node does not behave differently, even with the superchain-registry dependency.

Metadata

Fix CLI-4207

[changeset-bot]

⚠️ No Changeset found

Latest commit: a5015db

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[mergify]

Hey @protolambda! This PR has merge conflicts. Please fix them before continuing review.

[mergify]

Hey @protolambda! This PR has merge conflicts. Please fix them before continuing review.

[trianglesphere]

The chains test does give me high confidence that this isn't breaking anything & I verified that the chain configs in the test are the same as the chain configs on develop.

I'm having a hard time reviewing this because so much is pulled in from the superchain-registry repo & there is a lot of magic in terms of how stuff is expected to be rather than simple data.

[trianglesphere]

LGTM

[mergify]

This PR has been added to the merge queue, and will be merged soon.

[mergify]

This PR is next in line to be merged, and will be merged as soon as checks pass.

[mergify]

This PR is next in line to be merged, and will be merged as soon as checks pass.