You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not an actual bug (I think, unless the feature is missing), but a question. According to this, given a L2 transaction hash for a withdrawal, we can use
and l1TxHash will be the finalized tx hash on L1. How can we get the Tx hash of the "Prove Withdraw" operation in L1 ?
If the withdrawal is not finalized, would that l1Rcpt.transactionReceipt.transactionHash be empty, or would it be the Prove hash? If so, how can I get both transaction hashes once the withdrawal is finalized?
The text was updated successfully, but these errors were encountered:
Not an actual bug (I think, unless the feature is missing), but a question. According to this, given a L2 transaction hash for a withdrawal, we can use
and
l1TxHash
will be the finalized tx hash on L1. How can we get the Tx hash of the "Prove Withdraw" operation in L1 ?If the withdrawal is not finalized, would that
l1Rcpt.transactionReceipt.transactionHash
be empty, or would it be the Prove hash? If so, how can I get both transaction hashes once the withdrawal is finalized?The text was updated successfully, but these errors were encountered: