Mark Tyneway
Mark Tyneway
Looks like this needs a rebase
> this means any change to the set, including removals, correct? Removals of a chain in a cluster are not in scope. Its just too complex to decouple the assets....
We are in the process of deprecating the docker composed based devnet in favor of using kurtosis. See https://github.com/ethereum-optimism/optimism/issues/11562 for details
Needing to implement chain specific logic for safe depth could be implemented in a more generic way if the corresponding blockhash is stored locally and always checked against the remote...
I would love to merge this but ideally it uses `uv` instead of `pip`
This is sick
> May I work on this issue? Sure - can we work on a small design doc here before starting? It should include specifics around the implementation, like an overview...
Please follow up with a design doc directly in this thread, we are not at a stage where we can provide individual support
This is a duplicate of https://github.com/ethereum-optimism/optimism/issues/10890
Closing due to the access list design