[ENG-2202]: handle InboxMessageDeliveredFromOrigin event

[jorgemmsilva]

Ticket

• Related Linear Ticket: ENG-2202: Update translator and proposer to handle sendL2MessageFromOrigin events

What does this PR do?

• Summary:
  adds support for the InboxMessageDeliveredFromOrigin to the read loop (ingestor + translator in particular).
  It works by making the ingestor keep the tx_hashes for each log in the partial blocks and then translator can fetch the necessary calldata once it sees a log of the InboxMessageDeliveredFromOrigin type

[calebguy]

With this PR do we want to go back to using the non-forked version of the nitro contracts? Currently we deploy our forked version of the contracts from your PR here.

[jorgemmsilva]

That's an excellent point @calebguy. In practice yes, we can just use the vanilla contracts.
The gas savings are not so big that it justifies keeping a forked version of the contracts IMO, but that's something to discuss with the team 👍

[tsite]

That's an excellent point @calebguy. In practice yes, we can just use the vanilla contracts. The gas savings are not so big that it justifies keeping a forked version of the contracts IMO, but that's something to discuss with the team 👍

Think it's the other way around - the forked contracts use more gas, but allow for faster syncing of appchains as individual transactions no longer need to be fetched, just event logs. That said, removing the fork makes it easier to use arbitrum tooling to upgrade the contracts, so I'm in favor of that once this pr is merged.

[jorgemmsilva]

Yes @tsite, you're right - thanks for correcting this. Anyway, it probably doesn't justify keeping the fork.

[tsite]

a huge improvement! I left a couple comments, but this is great and removing the forked nitro contracts will make upgrades and maintenance a lot simpler