Latest L1->L2 transactions

[saimeunt]

Latest L1->L2 transactions

⚠️ Reading contributors guidelines to get assigned is MANDATORY!

Read contributors guidelines

User stories

• As a user, I want to see the 6 latest L1->L2 transactions (mainly bridging assets from L1 to L2) when I access the homepage, with the L1 block number and tx hash along with the corresponding L2 tx hash.

Validation

At the moment, the frontend part is fully functional and fed with placeholder data in the accompanying util function fetchLatestL1L2Transactions in src/lib/utils.ts. You only need to implement this util function properly to return the same transactions displayed on Etherscan.

Implementation

In the long run we'd like this data to be consumed from an indexer but we can build a functional POC to help us better understand how to retrieve the needed info from the blockchain. We will reuse this logic later when we build the indexer. My take on this is to fetch the logs from the latest 1000 blocks both on the L1 and L2 chain and perform a matching between the SentMessage/SentMessageExtension1 events emitted on L1 by L1CrossDomainMessenger and RelayedMessage emitted on L2 by L2CrossDomainMessenger. The contracts ABI and viem encapsulation is already available under src/lib/contracts. The correct way to perform the matching is to recompute the msgHash emitted in RelayedMessage from the arguments of SentMessage and SentMessageExtension1. Feel free to propose and implement an alternative method if you find something more simple and straightforward.

Resources

• OP Stack docs about message passing between L1->L2: https://specs.optimism.io/protocol/messengers.html#message-passing
• L1CrossDomainMessenger on Etherscan: https://etherscan.io/address/0x25ace71c97b33cc4729cf772ae268934f7ab5fa1
• L2CrossDomainMessenger on Etherscan: https://optimistic.etherscan.io/address/0x4200000000000000000000000000000000000007
• SentMessage and SentMessageExtension1 emitted here: https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/universal/CrossDomainMessenger.sol#L194-L195
• RelayedMessage emitted here: https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/universal/CrossDomainMessenger.sol#L295
• msgHash computed here: https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/libraries/Hashing.sol#L100

[EjembiEmmanuel]

@saimeunt I'd love to work on this. I'm an experienced frontend developer and have made contributions to several projects on OnlyDust. I can get it done in 2-3 working days. You can view my public profile at https://app.onlydust.com/u/EjembiEmmanuel.

[melnikga]

Hi, can I take this? I have been a contributor to several projects of the walnut team. My profile on onlydust: https://app.onlydust.com/u/melnikga

[danielcdz]

Hello, @saimeunt @mazurroman My name is Daniel Calderon I'm a software developer focused on backend and data development, in the last months I started to contribute through OnlyDust to multiple projects, here you have my OD Profile: https://app.onlydust.com/u/danielcdz, to solve this issue I will try the following:

• I will implement the function fetchLatestL1L2Transactions in src/lib/utils.ts to fetch the logs from the latest 1000 blocks both on the L1 and L2 chain and perform matching between the SentMessage/SentMessageExtension1 events emitted on L1 by L1CrossDomainMessenger and RelayedMessage emitted on L2 by L2CrossDomainMessenge just as you mentioned in the description.
• I will remove the placeholder data.
• I will perform the correct matching to get the data.
• Then I will filter the records to leave just the latest 6 L1 - L2 transactions Also, I would like to research and investigate other ways to retrieve the data, having another approach at least documented can be useful in the long run and when building the indexer.

[saimeunt]

@danielcdz Assigning it to you, good luck!

[danielcdz]

Thank you @saimeunt!