Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.19.0 to 0.20.0.
- [Commits](https://github.com/golang/crypto/compare/v0.19.0...v0.20.0)

---
updated-dependencies:
- dependency-name: golang.org/x/crypto
  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>

Fixes a bug in the SDK that would cause it to be unable to prove
certain types of withdrawals. Bug can be easily fixed on the
client side by adding an extra proof element in certain cases.

The new challenger algorithm may post some claims that the exhaustive test was posting.

* Prevent duplicate steps

* Prevent duplicate step claims

* op-challenger: Load maximum safe head from op-node RPC

* op-challenger: Remove no longer required code to find guaranteed safe head.

* op-e2e: Enable safe db

* op-challenger: Only counter claims that are either the child of an honest claim or are a sibling to the left of an honest move.

* op-challenger: Stop evaluating claims if an error is encountered since we will not be tracking the honest actions.

Includes rules to confirm that every move performed by the challenger would succeed as a call to contracts
Verifies that the game resolves correctly and the challenger is paid for every move it makes.

* op-challenger: Use opts pattern for claim builder

* op-dispute-mon: Track left most claim when resolving games.

also udpate op-geth dependency while we're at it

We keep reimplementing this logic so just add it to the game and test it properly.

Co-authored-by: will@2012 <xibaow2020@qq.com>

* feat(proxyd): improved consensus HA error reporting

* error metric should be a counter

* op-dispute-mon: Fix resolution to respect step actions
op-challenger: Add skipped game_solver tests for freeloader claims

* op-challenger: Add addition freeloader test.

* feat: add op-plasma data availability challenge contract

* fix: usePlasma and remove plasma template

* add DAC to Spec.t.sol

* add DAC to initialize config

* fix tests

* formatting

* add setter for plasma mode

* use alternative approach for enabling plasma mode in tests]

* extend test config output

* regen bindings

* add usePlasma to config.go

* add usePlasma to config.go

* allow enabling plasma in test environment

* initialize data availability challenge contract in constructor

* use proxy in DAC test

* fix spec test

* update bindings

* update type of usePlasma in config.go

* skip DAC in setup.go check for now

* skip DAC in setup.go if UsePlasma is wrong

* forge fmt

* gas snapshot

* add semver lock

* add snapshot

* improve comments

* absolute import

* bound refund percentage

* turn DAC test into a CommonTest

* set semver to 1.0.0

* add versioned commitments

* regenerate bindings

* regenerate snapshots

* update spec

* update gas snapshot

* add DAC to SystemConfig

* update semver

* update gas snapshot

* invariant

* snapshot

* bindings

* reorder deployment to have the DAC address before SystemConfig

* update spec

* move the DAC test to test/L1

* update snapshots

* add precision to the variable resolution cost

* regen artifacts

* semver lock

* bindings

* revert system config changes

* validate commitment length

* rebuild go bindings

* update constants

* remove indexed from commitment event

* semver lock

* add balance changed event to withdraw

* add method to get challenge status

* use basefee instead of gasprice

* use existing dac in test

* add sane default values to deploy config

* pre-pr

* go bindings

* assume challenger and resolver are different entities for balance checks in the resolver test

* add test for validate commitment, move out _getCommitmentType

---------
Co-authored-by: tchardin <tdotchardin@gmail.com>

* op-node: Add option to enable safe head history database.

Currently it just logs the information and has no actual database.

* op-node: Introduce pebble db to store safe head updates

* op-node: Reset the pipeline if safe head updates fail to be recorded

* go mod tidy

* op-node: Truncate when L1 head is reduced.

* op-node: Record accurate safe head data when restarting

* op-node: Ensure the latest safe head update is reset on a pipeline reset.

* op-node: Improve thread safety of safedb

* op-node: Add L2 block number to stored data

* op-node: Add API method to retrieve safe head at an L1 block number

* op-node: Tidy up key handling in safedb.

* op-node: Use an explicit reset event to clear entries invalidated by a pipeline reset

Add action test to confirm reorgs are correctly handled.

* op-node: Undo changes to start. We always step the safe head back at least one block.

* op-node: Simplify error message when requested record is prior to start of history

* op-node: Improve log message

* op-node: Tidy up

* op-node: Include L1 block number in response.

* op-node: Add missing AssertExpectations

* op-node: Verify key prefix

* contracts-bedrock: modularize config

All env var based config for the deploy scripts is centralized
into a single library called `Config`. Any `vm.env` or `vm.envOr`
calls should be added here so that it is easy to track the full
set of configuration options. Having this library makes configuration
much more self documenting for the deploy scripts.

This modularization is meant to make the migration away the old
hardhat deploy style architecture much easier. Now that we have
a canonical set of config values, we can be sure that anything
behind the abstraction is applied properly across the codebase
when it is changed.

There is a bunch of deprecated config, that will be able to
be deleted after https://github.com/ethereum-optimism/optimism/pull/9315
is merged along with some changes around where the default output
location for deploy artifacts is. Right now it is in the deployment
context directory, which the entire concept of deployment context
comes from hardhat deploy, which doesn't necessarily make sense
anymore. Right now it ends up in `deployments/<deploy-context>/.deploy`.
In the future, it will likely end up in the root of the contracts
directory by default and then an override can be provided where
the override is expected to be the absolute path to the desired
output location. This will greatly improve the devex and maintainability
of the deploy script.

* lint: fix

* fix(op-challenger): Packed Claim Clock

* fix(op-dispute-mon): port types to pointers

* op-node: Add flag categories

* op-node: Order categories & move some beacon flags to L1 RPC

* ci: use ci-builder image for slither

* Update slither.yml

---------
Co-authored-by: Raffaele <151576068+raffaele-oplabs@users.noreply.github.com>

Adds the cancun specific changes to the genesis block.
Cancun is coupled to ecotone so using `IsEcotone` to
see if the fields should be added to the genesis.
Is it a bad assumption to assume that cancun execution
is coupled to ecotone optimism network upgrade?

Bumps [github.com/hashicorp/raft](https://github.com/hashicorp/raft) from 1.6.0 to 1.6.1.
- [Release notes](https://github.com/hashicorp/raft/releases)
- [Changelog](https://github.com/hashicorp/raft/blob/main/CHANGELOG.md)
- [Commits](https://github.com/hashicorp/raft/compare/v1.6.0...v1.6.1)

---
updated-dependencies:
- dependency-name: github.com/hashicorp/raft
  dependency-type: direct:production
  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>

* op-e2e: Fix flaky TestOutputCannonStepWithKZGPointEvaluation test

* fault-proofs: Fix on-chain KZG precompile oracle

* fix for flakes in CI

and add nil check when logging oracleKey

* chore: update dependency on superchain-registry

* update references to chainConfig.SystemConfigAddr

* refactor: simplify extraction of addresses

* update dependency on superchain-registry/superchain

* go mod tidy

Bumps [nx-cloud](https://github.com/nrwl/nx) from 16.5.2 to 18.0.0.
- [Release notes](https://github.com/nrwl/nx/releases)
- [Commits](https://github.com/nrwl/nx/compare/16.5.2...18.0.0)

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

Bumps [@types/semver](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/semver) from 7.5.6 to 7.5.7.
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/semver)

---
updated-dependencies:
- dependency-name: "@types/semver"
  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 [ip](https://github.com/indutny/node-ip) from 1.1.8 to 1.1.9.
- [Commits](https://github.com/indutny/node-ip/compare/v1.1.8...v1.1.9)

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