Mark Tyneway

> This issue is caused by dependencies of sdk: [@eth-optimism/contracts](https://libraries.io/NPM/@eth-optimism%2Fcontracts) > > [@eth-optimism/core-utils](https://libraries.io/NPM/@eth-optimism%2Fcore-utils) > > These packages should be updated to use ethers^6. @eth-optimism/contracts is deprecated and we will want...

You should consider deploying to an orchestration framework like kubernetes instead of implementing that event handling yourself. Kubernetes is battle tested and it restarts containers when they fail

Yes you could likely do that although I do not have any good suggestions on how to do that off of the top of my head. It really depends on...

Not sure if fixed, I did add a commit trying to fix this

What would this impact? The relative path of reading in the p2p sequencer key? aka unsafe block signer key

You should consider migrating to viem as the sdk is going to be phased out eventually. viem natively supports op stack chains

I would be very supportive of breaking out the smart contract work into its own PR but I do understand how the other code depends on it

The solidity code looks good to me. I didn't go through the math super in depth or verify the upgrade transactions match exactly

@tarunkhasnavis looks like it needs a lint

Hey @saihaj! Thanks for opening this issue. I am curious how your solution would compare against the [blob archiver](https://github.com/base-org/blob-archiver) service that we already operate both in terms of cost and...