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.

* op-batcher: Enable optional pprof server

* op-proposer: Enable optional pprof server

* op-node: Eanble optional pprof server
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

* test(ctb): change gasLimit arg to uint256

* test(ctb): Set maximum diff fuzz gasLimit to 30MM

* test(ctb): Set maximum diff fuzz value to 120MM eth

* ctb: Address compiler warnings
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

* ops: Use starting L1 Block for timestamp everywhere

This transitions the starting timestamp to a new flow. The L2 rollup
is anchored on a L1 block. The L2 genesis block & rollup config use
the timestamp of the L1 start block as the their time. Properly
threading this through the HH tasks is a little tricky but possible.
This is because we have two flows: creating a L1 network & placing
the rollup on that and creating a rollup on an existing L1 network
(like goerli). There is still a L1 starting time for the first flow.

This also fixes a circular dependcy that previously existed. The
starting timestamp was provided and served as the starting timestamp
for the L1 genesis & the "L2 Starting Time" in the L2 Output Oracle.
The actual L2 genesis & rollup start time were based on when the
Optimism Portal contract was deployed (after the L2 Output Oracle
contract must have been deployed). The rollup is resilient to being
started before contracts are fully deployed, so using a specific
L1 block as the start is the cleanest solution I have seen.

* Fix lint

* Update packages/contracts-bedrock/deploy-config/goerli.ts

* Add undefined checks to l1StartingBlockTag

* lint

* fix checks
Co-authored-by: Matthew Slipper <me@matthewslipper.com>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Fixes foundry config issue so that warnings go away during
compilation. Also cleans up warnings when running tests.

https://github.com/nomad-xyz/ExcessivelySafeCall/commit/81cd99ce3e69117d665d7601c330ea03b97acce0

contracts-bedrock: in place handling of immutables

This updates the hardhat task `genesis-l2` to handle
setting the immutables in the deployed bytecode. This
is necessary because the predeploys "live" in the L2
state and are not deployed. Any immutables must be manually
placed into the bytecode by looking at the compiler output
and then finding the offsets and slicing in the values.

A high level API is exposed for setting arbitrary immutables
with the `replaceImmutables` function. This was inspired by
smock's `computeStorageSlots`.

Longer term, this code will be rewritten in go and be able to
operate on either a LevelDB database (upgrade an existing system)
or a `genesis.json` (good for starting a new network). This is
a requirement because the state surgery is large enough such that
it must bind directly to LevelDB and be in a language that is
relatively fast.

core-utils,contracts-bedrock,ci: OpNodeProvider + check

makefile: `clean-node-modules`

integration-tests: modularize

Bedrock goerli 96f44f79

contracts-bedrock: modularize build

Move away from using a nested api on the messenger
and instead use an imported function