MultiOffRamp - configurable metadataHash

[elatoskinas]

Motivation

Due to the different encoding schemes on non-EVM chains, the conversion of the MultiOffRamp requires making the metadataHash not tied to the abi encoding scheme.

Solution

Makes the metadataHash configurable with a uniqueness check

[github-actions]

I see you updated files related to contracts. Please run pnpm changeset in the contracts directory to add a changeset.

[github-actions]

Go solidity wrappers are out-of-date, regenerate them via the make wrappers-all command

[github-actions]

LCOV of commit ebbea12 during Solidity Foundry #5858

Summary coverage rate:
  lines......: 99.0% (1733 of 1751 lines)
  functions..: 96.7% (326 of 337 functions)
  branches...: 91.8% (731 of 796 branches)

Files changed coverage rate: n/a

[elatoskinas]

This is the metadataHash logic from the OnRamp. Would it be simpler if we also make this configurable on the MultiOnRamp? Then we could re-use the same hash compute logic off-chain - it would be less error-prone that way.

[connorwstein]

I think in practice we can just read directly the metadata hash onramp when we configure on the offramp

[elatoskinas]

Yeah that's less error prone, true. We'll have to change this prefix to EVM_2_ANY_MESSAGE_HASH though

[elatoskinas]

Closing - reworking to use OnRamp address without a configurable metadataHash