* Beacon node setup improvements

* Update op-node/flags/flags.go
Co-authored-by: protolambda <proto@protolambda.com>

* Add option to not half op-node startup on failed check

* Update op-node/flags/flags.go
Co-authored-by: protolambda <proto@protolambda.com>

* op-node: improve beacon-API configuration handling

---------
Co-authored-by: protolambda <proto@protolambda.com>

Bumps [@swc/core](https://github.com/swc-project/swc) from 1.3.100 to 1.3.104.
- [Release notes](https://github.com/swc-project/swc/releases)
- [Changelog](https://github.com/swc-project/swc/blob/main/CHANGELOG.md)
- [Commits](https://github.com/swc-project/swc/compare/v1.3.100...v1.3.104)

---
updated-dependencies:
- dependency-name: "@swc/core"
  dependency-type: direct:development
  update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [@wagmi/core](https://github.com/wevm/wagmi/tree/HEAD/packages/core) from 2.1.1 to 2.3.1.
- [Release notes](https://github.com/wevm/wagmi/releases)
- [Changelog](https://github.com/wevm/wagmi/blob/main/packages/core/CHANGELOG.md)
- [Commits](https://github.com/wevm/wagmi/commits/@wagmi/core@2.3.1/packages/core)

---
updated-dependencies:
- dependency-name: "@wagmi/core"
  dependency-type: direct:development
  update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* [op-conductor] use payload envelope

* address review comments

Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 5.0.11 to 5.0.12.
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/v5.0.12/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v5.0.12/packages/vite)

---
updated-dependencies:
- dependency-name: vite
  dependency-type: direct:development
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [@wagmi/cli](https://github.com/wevm/wagmi/tree/HEAD/packages/cli) from 2.0.3 to 2.0.4.
- [Release notes](https://github.com/wevm/wagmi/releases)
- [Changelog](https://github.com/wevm/wagmi/blob/main/packages/cli/CHANGELOG.md)
- [Commits](https://github.com/wevm/wagmi/commits/create-wagmi@2.0.4/packages/cli)

---
updated-dependencies:
- dependency-name: "@wagmi/cli"
  dependency-type: direct:development
  update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* contracts-bedrock: omit build-info

The `build-info` was required by the legacy hh deploy workflow.
It is no longer required and will save a lot of disk i/o by turning
off. `slither` uses build-info but it will clean and pass the cli
flag to `forge` directly. We do not need to create the build info
on each build. This should speed up foundry build times but not
by a huge amount.

* slither: fix

* op-e2e: update TestL1InfoContract to handle Ecotone

* op-e2e: fix some more delta tests to run with ecotone

* op-e2e: update system-fpp ecotone <> delta activation setup

* op-e2e: fix lint

This new method provides the option of setting the owner to a temporary deployer address.

* ci-builder: build python from source

* ci-builder: simplify install

slither only needs python3.8

* ci-builder: attempt fix

* op-node: Execution Layer Sync

This passes unsafe payloads directly the EngineController for immediate
insertion when Execution Layer sync is active. This tells the execution
client to sync to that target. Once the EL sync is complete, the last
unsafe payload is marked as safe. This is required when doing snap sync
because the EL does not have the pre-state required to do the engine
consolidation until the sync is complete.

* op-e2e: Snap Sync action test

* op-e2e: Actually run TestSystemE2E

* op-service/node: Add time.Since to Clock & use it

* ci: bump ci-builder to 0.38.0

Bumps to the latest ci-builder. This contains the new release
of foundry that contains the `vm.dumpState` cheatcode. This is
required for https://github.com/ethereum-optimism/optimism/pull/9091
to pass which fixes flakes in CI.

* ci: bump ci-builder

* ci-builder: v0.39.0-rc.1

Built from https://github.com/ethereum-optimism/optimism/pull/9099

* ci-builder: bump

* deps: bump again

Bumps [h2](https://github.com/hyperium/h2) from 0.3.21 to 0.3.24.
- [Release notes](https://github.com/hyperium/h2/releases)
- [Changelog](https://github.com/hyperium/h2/blob/v0.3.24/CHANGELOG.md)
- [Commits](https://github.com/hyperium/h2/compare/v0.3.21...v0.3.24)

---
updated-dependencies:
- dependency-name: h2
  dependency-type: indirect
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* op-node: Skip L2 Genesis Check when EL syncing

This is done because the transition block does not exist in a geth when
performing a snap sync and the actual genesis block header is pre-london
which breaks all of our fetching code.

* Update op-node/rollup/types.go

The coinbase fork of these scripts are now used in `superchain-ops`.
These scripts do not need to exist in the monorepo, they should live
in the `superchain-ops` repo. They are unused in the monorepo and there
is no reason to keep these scripts around as they only add to compile
time. They have not been maintained which is evident in the fact that
they still do not follow the style guide for import style. These scripts
were useful for a few upgrades but now that the coinbase fork of these
scripts are more maintained, there is no reason to keep these around.

Bumps [@vitest/coverage-istanbul](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-istanbul) from 1.2.0 to 1.2.1.
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v1.2.1/packages/coverage-istanbul)

---
updated-dependencies:
- dependency-name: "@vitest/coverage-istanbul"
  dependency-type: direct:development
  update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Replaces https://github.com/ethereum-optimism/optimism/pull/9089

We do not want to call the `FFIInterface` or other test contracts as part of the
invariant tests because it will create malformed inputs and cause
unrelated invariant tests to fail.

Co-authored-by: Luke <chenqun.l@kaitaitech.cn>

* op-e2e: revive original 4844 DA test
Co-authored-by: Roberto Bayardo <bayardo@alum.mit.edu>

* op-service: fix beacon API HTTP client encoding of query string, avoid malformatting due to path joining

* op-batcher: data-availability-type enum and generic flag

* op-e2e: eip4844 test improvements

* op-batcher,op-service: review fixes on 4844 api fix

* eth: Add tests of Beacon API response structs

* eth,sources,fakebeacon: Update Beacon API BlobSidecar format

* eth: Remove field BlobSidecar.BlockRoot

* eth: Fix BeaconBlockHeader json tag, test APIGetBlobSidecarsResponse

* eth: Simplify Beacon API types and tests

* op-service: fix bytes96 terminal stringer in op-service/eth/types.go

* op-service: fix comment lint

---------
Co-authored-by: Roberto Bayardo <bayardo@alum.mit.edu>
Co-authored-by: Sebastian Stammler <seb@oplabs.co>

Generating the allocs no longer relies on `geth` so we do not need to
install `geth` as part of bringing up the devnet. We also generate the
allocs once and then persist them to the CI workspace. This will save
~1-1.5 minutes per CI run by no longer installing `geth` as part of
the devnet.

* cannon: Allow stopping at first preimage read

* cannon: support stopping on preimage key and type

* contracts-bedrock: flake fix attempt

Progress towards fixing flakes in CI. Using `etch` to set contracts in
state instead of deploying will help to fix the nonce mismatches between
the L1 contract addresses and the L2 genesis that contains L1 contract
addresses.

Developers will need to run `forge clean` to remove artifacts for the
tests to pass after this commit is merged. It enforces a single version
of `FFIInterface` to be compiled instead of it being compiled with
multiple compiler versions. The `vm.getCode` family of cheats fail when
there are multiple compiled versions of the same contract because the
artfact has the compiler version appended to the name of the artifact.

This will also help to improve compiler time since the compiled
contracts do not need to include the compiled bytecode of the deploy and
ffiinterface contracts, the code is loaded dynamically instead of being
deployed with `CREATE`.

* contracts-bedrock: more cleanup

Deletes a dead file that is no longer needed and sets the deploy config
in state using `etch`. `DeployL2` is not used, we should be using the
`superchain-ops` repo for deploying new L2 contracts or deploy them
through L1. Since `DeployL2` used code using solc `0.8.19` (EAS) it
caused multiple versions of the `DeployConfig` to be compiled which
causes headaches when using `vm.getCode`.

* contracts-bedrock: update gas snapshot

* contracts-bedrock: more cleanup

* contracts-bedrock: gas-snapshot

* lint: fix

Introduces the infrastructure for monitoring large pre-image proposals, up to loading the list of in-progress games from the contract.
Actual content of the preimages is not yet loaded or checked.

* op-node: fix parent-beacon-block-root comparison check

* op-node: nit in op-node/rollup/derive/engine_consolidate.go
Co-authored-by: Sebastian Stammler <seb@oplabs.co>

* op-node: two-side nil parent beacon block root test case

---------
Co-authored-by: Sebastian Stammler <seb@oplabs.co>

* contracts-bedrock: hacky patch for CI failures

CI is consistently failing due to the L2 genesis generation happening
out of process using ffi. Ideally the genesis state could be ran a
single time once outside of the process ahead of time but the problem
with this approach is that the deployer nonce is not correct and the
L1 contract addresses in practice end up not matching the addresses
that are injected into the L2 genesis state. There are a few solutions
to this problem, one is deploying the proxies with create2 and another
is to ensure that the deployer does not deploy additional contracts
in the test case setup that are not deployed in the L1 genesis gen
setup so that we are guaranteed that the contracts have the same
addresses.

This is a hacky patch to attempt to fix the issue where it will wait
if the allocs file doesn't exist. Something with the process running in
parallel causes the file to not exist. The downside of this fix is that
CI may hang silently forever if the file is lost for some reason.

Another solution would be to return the JSON to solidity and then write
it to a temp file. This isn't ideal but could work in the short term.
We are working on a rewrite of the L2 genesis generation in solidity
that will fix this issue along with many other devex issues in the
monorepo.

* ctb: update gas snapshot

Bumps [github.com/onsi/gomega](https://github.com/onsi/gomega) from 1.30.0 to 1.31.0.
- [Release notes](https://github.com/onsi/gomega/releases)
- [Changelog](https://github.com/onsi/gomega/blob/master/CHANGELOG.md)
- [Commits](https://github.com/onsi/gomega/compare/v1.30.0...v1.31.0)

---
updated-dependencies:
- dependency-name: github.com/onsi/gomega
  dependency-type: direct:production
  update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* feat(op-challenger): Adds a helper to call the initLPP preimage oracle
contract call.

* fix(op-challenger): call init large preimage from the uploader

* fix(op-challenger): keep large preimage upload unsupported for the interim