superchain-registry Infer other addresses from SystemConfig once MCP L1 is launched

          The goal of this file to serve as a reference and source of truth, which we verify in the `CheckSecurityConfigs` script? I ask because as of https://github.com/ethereum-optimism/optimism/pull/6555, we can now only define a chain's `SystemConfig` and then discover everything else. Wondering if we can leverage that in this repo (once everyone is on MCP L1 contracts)

Originally posted by @mds1 in https://github.com/ethereum-optimism/superchain-registry/pull/69#discussion_r1471464207

Jan 30 '24 16:01 zchn

The downside of this is that the other addresses will no longer be tracked in the repository, and therefore not inspectable by humans / services / software packages that want to read them.

Jul 08 '24 15:07 geoknee

@geoknee What do you mean exactly? We can, for example, only ask for their SystemConfig address if it simplifies the add chain process, but still generate output files that contain all other system addresses for humans / services / software packages that want to read them.

Jul 28 '24 15:07 mds1

Yeah you're right that should work well. I think I was skipping all the way to "only store the SystemConfig address" which is not what this ticket is about.

Aug 06 '24 14:08 geoknee