soyboy

@nitantchhajed I'm not sure why its panicking, but the first thing I'd like you to check is your engine-api connection, because it appears the `op-node` and `op-geth` cannot talk to...

@nitantchhajed okay let me get some protocol engineer eyes on this, I'll see if someone can take a look today, but I also have some synchronous time with them tomorrow...

@nitantchhajed can you specify your versions you're using: - op-node, op-batcher, op-proposer: [v1.7.2](https://github.com/ethereum-optimism/optimism/releases/tag/v1.7.2)? - op-geth: [v1.101308.2 ](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101308.2)?

@nitantchhajed oh cool! Do you know what was causing the panic? We'll work on figuring out why the go-lang tests aren't passing

Hey @atenjin, this PR is not passing some tests, but I noticed that you submitted this PR as a `standard` chain. The current [Standard Configuration Requirements](https://specs.optimism.io/protocol/configurability.html) have data availability limited...

We're making some changes to this repository and we've paused adding new chains for now. We'll reopen this process once the repository is ready. The Superchain itself, of course, remains...

Hey @alvrs! To add a new chain, you can follow the steps here in the [contributing doc](https://github.com/ethereum-optimism/superchain-registry/blob/main/CONTRIBUTING.md#adding-a-chain). Given redstone is running with alt-da, you'll want to specify `frontier` when running...

Hey @karooolis, to fix the codegen error you can run the following from the root of the repo: `pnpm codegen`. That should generate the missing lines that the CI is...

Fantastic, from the technical side we're all clear. I'm asking internally for the BD/Partnerships sign off

We're making some changes to this repository and we've paused adding new chains for now. We'll reopen this process once the repository is ready. The Superchain itself, of course, remains...