SuperchainRegistry: establish pattern for reading data from chains with different contract deployments
Closed this issue · 0 comments
geoknee commented
This will be useful anywhere we are reading data from chain, including in the script which adds new chains and also in the validation suite.
This could be a set of shared helper functions or data structures. It should be architected such that it as easy as possible to maintain when new contract sets are released and used.