How do I get the Prove transaction hash, given a withdraw initiated in the L2 ?

[gndelia]

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

I had this question created as an issue ethereum-optimism/optimism#9974
I'm using the OP SDK (I know it's deprecated), and given a completed withdrawal transaction hash, I know I can use getMessageReceipt to get the Claim transaction hash.

const l1Rcpt = await crossChainMessenger.getMessageReceipt(l2TxHash)
const l1TxHash = l1Rcpt.transactionReceipt.transactionHash

How can I get the prove transaction hash? I can't find a method in the docs that returns so. Should I do a mix of different calls?

Thanks

Additional Information

I'm using @eth-optimism/sdk v3.2.1

Feedback

No response

[joohhnnn]

Hi there if the prove transaction hash you mentioned here is fault proof distribute game hash, you can find it by the specify game, and you can find every games by game factory. you can refer this diagram.

[gndelia]

Hey @joohhnnn ! Thanks for answering. I am a bit of a newbie on the whole OP flow, so I am sorry if what follows is not correct 😅 .

I am not doing this on Optimism but on a Forked L2 from OP.

The prove step I am referring to is this one, after calling proveMessage.

I think this forked L2 is not using dispute games (Our L2 is not using FPAC contracts yet)

[joohhnnn]

oh I think I got your question
PLZ check this diagram

If I understand correctly you need user's withdraw Application transaction hash, you can make a filter with user address and L1StandardBridge address. If not, you can refer this way to get any data you wanted. First, you need to get a clear understanding of how the components interact with each other. The diagram above is a great starting point.

[gndelia]

Sorry for the delay, I've been working on other things 😓 Perhaps you can still help me

@joohhnnn what I need is something like this:

This is a withdrawal initiated in an L2 0xdbd2f1d46a2f508a6db03e7e5fcfd8a482c1461cc5b3db5a99311fd5b9b55469 (for all purposes, it's a fork from Optimism)
Now, I've just proved that withdrawal. Here in Sepolia 0xa2312f662244db3aa8c09251da5dd396e9c03784a865b21768d65b6e699f9806 is the transaction hash.

Now, let's assume I have a page that wants to show this information from scratch (so the 3 transactions are shown in some kind of flow graph). I have a subgraph that, given the user wallet on the L2, gets me the first transaction hash. So I have 0xdbd2f1d46a2f508a6db03e7e5fcfd8a482c1461cc5b3db5a99311fd5b9b55469 ( the withdrawal initiated in the L2) . What I don't know how to do is to get from there to the Prove transaction hash (0xa2312f662244db3aa8c09251da5dd396e9c03784a865b21768d65b6e699f9806).

I just tried creating a subgraph on the L2 bridge, and monitoring the WithdrawalProven events, only to find out that the withdrawalHash that's emitted is a hash of the Withdrawal object, and not the TX the user itself got.

This fork is not using Dispute games yet.

Can you help me getting that information? I'm a bit lost.

Thanks 🙏🏽

edit: In addition to that, I also need to get the claim transaction. I just claimed (after writing that) that transaction in Sepolia, and I got the has 0x3aac9720293c8521190cc274b184ddf1ba301e616d4cf9c6fe853e88ae31296c. The idea would be to also get this hash starting from the withdrawal hash from the first transaction

edit2:
I was able to generate that withdrawalHash by doing this (with viem)

const encoded = encodeAbiParameters(
    parseAbiParameters('uint256, address, address, uint256, uint256, bytes'),
    [
      nonce,
      sender,
      target, // transaction.target,
      value,
      gasLimit,
      data,
    ],
  )
const withdrawalHash = keccak256(encoded)

So I guess I could still use my subgraph that's filtering events, and match by that 🤔