Replace OP Superchain feature with generic Multichain explorer#3299
Replace OP Superchain feature with generic Multichain explorer#3299
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. To trigger a review, include You can disable this status message by setting the Use the checkbox below for a quick retry:
Tip Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs). Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Description and Related Issue(s)
This PR replaces the OP Superchain–specific feature with a generic Multichain explorer feature. The feature still uses the same multichain aggregator and stats APIs and the same env vars; only naming and surface area are generalized so it can support any multichain cluster, not only the former OP Superchain interop cluster.
Proposed Changes
opSuperchainwith a newmultichainfeature inconfigs/app/features/(same logic and env vars:NEXT_PUBLIC_MULTICHAIN_ENABLED,NEXT_PUBLIC_MULTICHAIN_CLUSTER).ui/optimismSuperchain/usage, feature keyopSuperchain→multichainin nav, pages, guards, etc.)..env.multichain_dev,.env.multichain_prod) and updated deploy/validator configs and preset-sync tooling to use the new naming.docs/ENVS.mdor env variable names; existing Multichain explorer env vars remain as documented.Breaking or Incompatible Changes
None. The same environment variables (
NEXT_PUBLIC_MULTICHAIN_ENABLED,NEXT_PUBLIC_MULTICHAIN_CLUSTER) are used. Deployments that relied on theopSuperchainfeature flag/key need to switch to themultichainfeature (or equivalent config) where that key is referenced.Additional Information
N/A
Checklist for PR author
Made with Cursor