Problem

#4277 and #4284 were recently merged, enabling fraud proofs to be proven and attributed on the origin chain

#4319 and others enable withdrawal messages over the native L2 bridges (OP and arb flavors atm)

We would like to be able to communicate the result of fraud proof attributions via messages over the native L2 bridges

Solution

We should implement a FraudProofRouter contract to benefit from Router hook and ISM configurability

The message content can look something like the following

struct FraudMessage {
  address signer;
  unt48 timestamp;
  FraudType fraudType;
}

We would like client contracts (eg slashers in Eigenlayer/Symbiotic/etc) to read remote proven fraud attributions from this

We need infra or CLI support for

• configuring this contract
• deploying these contracts
• relaying these messages