Matt Solomon
Matt Solomon
My thinking would be "standard chain candidates" (and stricter, so standard chains also), but would like to confirm with @ajsutton
@klkvr Potentially related to https://github.com/foundry-rs/foundry/issues/8639?
@maurelian has been working on integrating OPCM into this file recently so likely will know better than me
Just adding some extra details: - For chains on contract versions earlier than `op-contracts/v1.6.0` we still expect a single DelayedWETH - For each chain on `op-contracts/v1.6.0`, there should be two...
Historically the superchain registry has served as a reference of all contract addresses for a chain, and other tools consume this data and treat it a a source of truth....
> Given that superchain-registry is regularly out of date like this (ie after pretty much every upgrade for at least a short period), I don't think it makes a very...
Thanks for these details, this logic makes sense to me and I'm onboard simplifying the superchain registry maintenance by only storing `DisputeGameFactory` As for when to do it, I'll defer...
Before this, we should consider another check that lives in the monorepo since that is closer to the source and we can improve the storage layout collision detection there
I'm not sure if we have an issue for this, but a related idea I've had was: when running a forge script, if the RPC URL is localhost, instead of...
That's also a nice UX, I. like the idea. It does feel like being able to pull in deployments/ABIs from dependencies like that is very related to package management ideas...