Minor README update after questions from a third party.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Fixes a small error in the message-relayer canary action that would
cause it to fail to build.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Adds a fault status API endpoint so people can easily query if the node
is currently diverged.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Makes finalizeWithdrawalTransaction not payable. Having this function be
payable created test failures because it was confusing whether funds
should be sent to that function.

Version Packages

Develop -> Master

* proxyd: Support per-RPC rate limits

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

op-chain-ops: cross domain message

Trigger Releases

Version Packages

Merge develop to master

op-bindings: l1xdm bindings

Implement encoding and hashing of `CrossDomainMessage`
structs. This includes some tests for both v0 and v1
that were generated using solidity.

This is required for the migration of withdrawal hashes.

Adds L1CrossDomainMessenger more bindings

op-chain-ops: parse t_bytes32

Updates the solidity version used for compiling
the `GovernanceToken`. This is an attempt to solve
the non deterministic binding generation.

Since `GovernanceToken` is already set as a predeploy,
this will only have an impact on new networks.

Adds extra type parsing to allow setting t_bytes32
in mappings.

op-chain-ops: modularize setting the state

The astids are non deterministic for some reason
in our toolchain but the storage layouts are always
the same. This adds some code to remove the nondeterminism
but we lose the ability to work with astids. This is fine
for the way that we are using the storage layouts.

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

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

Fixes a build error where files were being referenced that were not
included in the NPM build. CI did not catch this because CI operates on
what's in the monorepo, which included the relevant files.
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Blockes v0 messages from being relayed in Bedrock. As part of the
Bedrock migration, we will guarantee that all v0 (legacy) messages that
have not been successfully relayed will be transitioned into v1
messages. All other v0 messages will already have been relayed and
therefore do not need to be relayed again.

* feat(ctb): remove blockedSystemAddresses

Removes the blockedSystemAddresses in favor of a more flexible approach
that also removes most of the need for the initializer. We will be
following this up with a second PR that removes the initializer
entirely.

* contracts-bedrock: regenerate snapshot
Co-authored-by: Mark Tyneway <mark.tyneway@gmail.com>

Removes the dependency on the `foundry` container so that we can automate deployment of the ci-builder container.

This wraps some common functionality of state setting
into a single function so that it can easily be reused
in other components. I'd like to use this function as part
of testing, it can be used to populate a `SimulatedBackend`
with a set of contracts and their state pre-initialized.

contracts-bedrock: add in alpha-1 network

specs: this PR does fix a few typos

contracts-bedrock: CrossDomainOwnable

op-bindings: add back registry

op-bindings: regenerate

op-bindings: remove ast set to 0

op-bindings: regenerate

Adds 2 new contracts to the `L2` directory. Both contracts
extend OZ `Ownable` such that the `onlyOwner` modifer logic is
overwritten.

`CrossDomainOwnable` is designed for ownership of contracts on L2
when the communication goes directly through the `OptimismPortal`.
This is not safe for when the communication goes through the
`CrossDomainMessenger` system, as `msg.sender` would be the
address of the `L2CrossDomainMessenger` and if that is the owner
of the L2 contract then anybody going through the messenger system
would have owner permissions on the contract.

`CrossDomainOwnable2` is designed for ownership of contracts on L2
when the communication goes through the messenger system. It checks
for the L1 message sender value that is set in the
`L2CrossDomainMessenger` contract.

Both of these contracts include test coverage and are relatively simple.

contracts-bedrock: review fixes

contracts-bedrock: make the messenger value constant

contracts: fix

contracts-bedrock: update snapshot

lint

fix test