This job isn't needed anymore since we're compiling the artifacts into the bindings.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Minor modification that puts the raw body as a string on the request
object. Useful for applications where the raw body is required rather
than the parsed JSON body as given by bodyParser. For example, this is
useful when verifying GitHub webhooks.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

* op-node: Fix OPB-07

Fixes Sigma Prime audit issue OPB-07: Private Key Stored Without Encryption. This PR requires reading the sequencer private key from an environment variable rather than a file on disk.

Fixes ENG-2616

* fix devnet

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

Adds consistency checks for L1 syncing nodes in the DTL. One of my
personal nodes seemed to halt with this error, so fixing it.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Adds versioning rules to the Bedrock contracts package.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

The tests run as part of `bedrock-go-tests` so no need
to have a task specific for `op-chain-ops`.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

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

Introduces a new task for validating the correctness of spacer
variables. Prevents future developers from accidentally moving spacers.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

* op-chain-ops: implement withdrawal hashing

Implement both the new hashing scheme and the legacy
hashing for withdrawals so that the withdrawals can
be migrated.

Also implement encoding and decoding of the withdrawals

* more tests

* op-chain-ops: code review fixes

* op-chain-ops: fix message passer

Now that the old message passer is being kept in the L2
state, be sure to the use legacy address. The new message
passer is at a different address.

* ci: Ignore l2geth coverage reports

* ci: Upload coverage reports in js-lint-test
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

* op-node: Fix OPB-10

Fixes OPB-10: No Checks for Deposit Transaction Type When Calling `L1InfoDepositTxData()`. This PR adds a check in `blockToBatch` that checks the type of the first transaction in the block, and returns an error if it isn't a deposit transaction.

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

The ownable upgradable modifier was not used anywhere
in the contract. The erc20 factory does not follow that
pattern. This change simplifies things by moving
values to immutables instead of being in storage.

This is a cleanup PR before migrating these contracts to
`contracts-bedrock`.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

* contracts-bedrock: add semver to erc20 factory

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

* proxyd: Add batch size metric and configurable max

The max batch size will be overwritten if it is over `MaxBatchRPCCallsHardLimit`.

Builds on https://github.com/ethereum-optimism/optimism/pull/3544.

* changeset

* fix lint

* fix test

* proxyd: Add customizable whitelist error message

Alchemy is asking for this so that we can include their affiliate link.

* add missing test case

* fix error message

* goimports

* fix(ct): bug in L2OutputOracle constructor

Fixes a small bug in the L2OutputOracle constructor where an assertion
was being made about the wrong value. Unlikely that this would've caused
any significant issues but worth fixing anyway.

* Update l1genesis generation code

Puts the genesis timestamp inside the simulator, and updates the simulator code to properly wait for blocks to be mined. See the comments in deployer.go and layer_one.go.

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

Version Packages

Trigger Releases 

Moves the L2ToL1MessagePasser to a new address and introduces the
LegacyMessagePasser to live at the old address.
Co-authored-by: Mark Tyneway <mark.tyneway@gmail.com>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

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

Update op-geth to the latest version on the `optimism-history` branch. This version exposes the customizable simulator backend that we need to merge https://github.com/ethereum-optimism/optimism/pull/3322.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

* op-node: Fix OPB-04

The length of the ExtraData field was not being checked, which could lead to panics in the MarshalSSZ function.

Fixes ENG-2614

* code review fixes

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

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

* contracts-bedrock: fix `OptimismMintableERC20Created`

The names of the event args were backwards from what they
were supposed to be. I noticed this while writing integration
tests for the sdk.

The event is used like this:

```solidity
emit OptimismMintableERC20Created(_remoteToken, address(localToken), msg.sender);
```

The event was updated to look like this:

```solidity
event OptimismMintableERC20Created(
    address indexed remoteToken,
    address indexed localToken,
    address deployer
);
```

The `remoteToken` is first and the `localToken` is second.

* ctb: Avoid extra casting from contract to address

* chore: Regen bindings and snapshot

* chore: Update bindings
Co-authored-by: Maurelian <maurelian@protonmail.ch>
Co-authored-by: Matthew Slipper <me@matthewslipper.com>

Standardizes storage spacer names and makes sure that storage spacers
are all using their original variable types.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Improves and simplifies metrics by using better metric labels.

* nft: L-13 Duplicated code

* nft: M-08 Upgradeability inconsistencies

* fix(ctp): change `CrossDomainEnabled` to `CrossDomainMessenger`

* fix(ctp): make `otherBridge` and `messenger` in nft bridge contracts immutable

* docs(ctp): update `ERC721Bridge` bridging function docs

* re-order `OptimismMintableERC721Factory` event args

* remove unnecessary `Initializable` import in nft bridges

* changed legacy `CrossDomainEnabled` call to `CrossDomainMessenger
Co-authored-by: Mark Tyneway <mark.tyneway@gmail.com>

* ctb: Naming and comments to clarify interfaces usage

The OptimismMintableERC20 token used two interfaces in its
supportsInterface() function. These were confusingly named
after the functions that they contain (ie. IL1Token, IRemoteToken),
rather than the contracts these interfaces represent.
The name has been tweaked slighly, and comments have been added to
clarify the intent.

fix(ctb): Clearer names for the mintable token iface

* ctb: Add bridge() to mintable erc20 interface

* chore: bindings

* op-chain-ops: implement pending withdrawal fetching

We need a list of pending withdrawals to be able to
migrate the withdrawal hashes to the new withdrawal
hash scheme. This commit implements the script for
fetching pending withdrawals as well as a unit test
for the function responsible for fetching pending withdrawals.

From within `op-chain-ops`, the script can be ran as follows:

```golang
$ go run cmd/withdrawals/main.go
```

lint

* op-chain-ops: go mod tidy
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Co-authored-by: Matthew Slipper <me@matthewslipper.com>