Superchain
The Superchain Registry

The Superchain Registry

The Superchain Registry (opens in a new tab) serves as the source of truth for who's in the Superchain Ecosystem and what modifications they've made. The Superchain Registry introduces:

  • A step-by-step process new chains can follow to join the Registry
  • Validation checks to ensure standard chains comply with the Standard Rollup Charter and non-standard chains pass baseline validation before joining the Superchain Registry
  • A Superchain Registry repository that shows who's in the registry and the chain's configuration. Chains with superchain_level = 2 have proven that they follow the Standard Rollup Charter, and can be classified as a Standard Rollup.

The Standard Rollup

An OP Stack Standard Rollup follows the Standard Rollup Charter.

This configuration targets the Optimism Collective's highest bar for security, uptime, and decentralization.

You can find more details in the Standard Rollup Charter documentation.

We strongly recommend using the op-deployer to deploy L1 contracts and generate the L2 genesis file that meets the configuration requirements outlined in the Standard Rollup Charter.

Joining the Registry

All Superchain Ecosystem members are welcome to join the Superchain Registry, regardless of whether they adhere to the standard rollup charter or not. To join the Registry, follow the steps in this guide (opens in a new tab) to submit a pull request and join the Superchain Ecosystem. This guide will help you set up your chain, create your environment, and run all the validation checks needed to ensure your chain is ready to join the Registry.

Hard fork activation inheritance behavior

After being included into the Superchain Registry, subsequent releases of the op-node and op-geth will contain the chain's genesis and rollup configurations baked in. You can use then use the --network (op-node) and --op-network (op-geth) flags to start up your node with this information. Using these flags means that the node will automatically inherit the hard fork activation times from the Superchain Registry, so you don't need to manually set them in your node configuration.

Additionally, chains can opt into the hard fork activation inheritance behavior by specifying the superchain_time in the chain's TOML file to start inheriting Superchain wide activation timestamps. Networks who have utilize this mechanism will activate network hard forks specified in the superchain.toml files: Sepolia superchain.toml (opens in a new tab) and Mainnet superchain.toml (opens in a new tab).