`no_output_timeout` wasn't being honored because the deposit command produced output on each poll. Instead, use the `timeout` command to kill the process from within the job itself regardless of output.

* proxyd: Unwrap single RPC batches

* Update backend.go

Co-authored-by: Matthew Slipper <me@matthewslipper.com>

* style(specs): fix toc/lint in specs, update CI

style(specs): lint/toc/link fixes

style(readme): fix bedrock contracts link

chore(specs): specs lint scripts

chore(specs): update CI jobs to use new lint scripts and unsilence links linter

style(specs): fix toc, fix quotes in markdown lint script

* yarn: update linting dependencies

* specs: add minimal batch submitter spec, fix broken links
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Co-authored-by: Will Cory <willcory@Wills-MacBook-Pro.local>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

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

This will allow us to measure opnode throughput.

* op-node: Derivation metrics

Adds support for the following batch derivation metrics:

- 0/1 gauge for if the derivation is idle
- Count of total pipeline resets
- Count of total unsafe payloads received
- Count of total derivation errors
- Gauge tracking the various L1/L2 safe/unsafe heads

* review updates + more metrics

* op-node: Add channel frame serialization

This creates a struct & serialization & deserialization methods
for it. This is to replace the current serialization code which
is embedded in more complex methods.

The reading is done with a reader API instead of a bytes API because
the frame is variable length & is originally merged together with
other frames without a clean division. The writing API uses a
writer for simplicity (but is not required).

This lays the groundwork for easily switching to fixed int sizes.

* op-node: Use channel frame deserialization

This uses the new channel frame object for deserialization. Some
of the API interaction is a little weird in the channel_bank
IngestData loop, but the code is not able to be easily tested and
upgraded.

* op-node: Use channel frame in serialization

This uses the default implementation (through a struct) rather
than the custom logic. It might make sense to use a slightly
different API for serialization than deserialization given the
inputs, but splitting out the logic into it's own function is
still an improvement.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

* core-utils: add bedrock types

* sdk: implement bedrock functionality

* tests: update for bedrock

* sdk: add hardhat deposit task

* circleci: run deposit task in ci

* tsconfig: cleanup

* contracts-bedrock: make commitment interval larger

* changeset: add
Co-authored-by: Mark Tyneway <mark.tyneway@gmail.com>

* contracts-bedrock: add forge contract verification support

Add etherscan contract verification for the hh/foundry
compiler toolchain. This will eventually be upstreamed,
but is implemented here to ensure that it works thoroughly
first.

To run the task:

```
export ETHERSCAN_API_KEY=$(cat api-key.txt)
$ npx hardhat forge-verify --network goerli
```

In the future, other contract verification backends
will be added to forge and this task will be updated
to support them.

Example contract that was verified: https://goerli.etherscan.io/address/0x1234662682c85fa6fb375416d14db965eba222ba#code

An individual contract can be targeted instead of all of them
with the `--contract` flag. If hardhat deploy has configured
external deployments, forge will not be able to verify them.
It may be possible to implement that in the future.

* contracts-bedrock: modularize tasks

contracts-bedrock: L2ToL1MessagePasser event extension

Emit an additional event during `initiateWithdrawal` that includes
the withdrawal hash so that it is easy to observe changes to the
`sentMessages` mapping.

* op-node: Add p2p utils

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

This now uses a passed in timestamp for PreparePayloadAttributes.
This is important because when generating a payload attributes from
a batch it should be using the timestamp of the batch, not the
L2 parent + block time. When we are creating payloads based on the
L2 parent time, that is easy to set there instead of pulling it into
this function.

This enabled/exacerbated a divergence bug where the timestamp of the
batch was not the timestamp that was being set inside
PreparePayloadAttributes.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

This reverts commit f7fcf8a1.

* op-node: Add p2p utils

* Update op-node/cmd/p2p/cmd.go
Co-authored-by: Joshua Gutow <jgutow@optimism.io>

* Update op-node/cmd/p2p/cmd.go
Co-authored-by: Joshua Gutow <jgutow@optimism.io>

* lint

* fix devnet
Co-authored-by: Joshua Gutow <jgutow@optimism.io>

contracts-bedrock: fix deployment

contracts-bedrock: add watch task

ops-bedrock: simple config fixes

* add wsteth to sdk

* changeset
Co-authored-by: Will Cory <willcory@Wills-MacBook-Pro.local>

The gas snapshot check was disabled in CI because it
would cause a lot of merge conflicts. Now that there
is no rush to change the contracts, we should re-enable
the check. Also commit in the latest snapshot.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

contracts-bedrock: fix slither

Update to commit 64fe4acc97e6d76551cea7598c201f05ecd65639

https://github.com/foundry-rs/foundry/tree/64fe4acc97e6d76551cea7598c201f05ecd65639
https://github.com/foundry-rs/foundry/commit/64fe4acc97e6d76551cea7598c201f05ecd65639

This update is pulled in so that the new config file format can be
adopted.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

* ci: Tag cloudbuild images with the commit SHA

* contracts-bedrock: Fix provider usage in L2OutputOracle deployment script

`getDefaultProvider()` returns a fallback mainnet provider, which doesn't work.

Builds on #3147.

Also adds a new `deployer` network for use with automation.

`slither` crashes on new solidity features, one is used
in the forge tests. Not exactly sure what it is, but
this will prevent that problem by moving the tests
to a temp dir when running slither and then moving them
back.

deps: update excessively-safe-call

Deletes an old config option and also changes the poll
interval on the `op-proposer` to `1s` so that it submits
outputs faster. I found that the proposer will lag a lot,
especially if the commitment interval is small.

We need to carefully consider the implications of the commitment
interval and understand if it can be updated dynamically or not.

A hardhat task that lists off important information.
Very helpful for debugging live networks.

Usage:

```
$ npx hardhat watch --network devnetL1
```

It will print off information as the chain makes progress.

It was being deployed with the implementation address
of the `L2OutputOracle` instead of the proxy. This
was preventing output commitments to actually be posted.