sdk: add hh task for finalizing withdrawal#3638
Conversation
Now we no longer need to use one off scripts for testing this kind of thing. The hh task will check to see the status of a transaction hash and then finalize the withdrawal on L1 if the message status is ready for relay. It does this by creating a `CrossChainMessenger`.
|
|
This PR changes implementation code, but doesn't include a changeset. Did you forget to add one? |
maurelian
left a comment
There was a problem hiding this comment.
Just a question for now.
|
This PR has been added to the merge queue, and will be merged soon. |
|
This PR has been added to the merge queue, and will be merged soon. |
|
This PR is next in line to be merged, and will be merged as soon as checks pass. |
Now we no longer need to use one off scripts for testing this kind of thing. The hh task will check to see the status of a transaction hash and then finalize the withdrawal on L1 if the message status is ready for relay. It does this by creating a `CrossChainMessenger`. Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Description
Now we no longer need to use one off scripts for testing this kind of thing. The hh task will check to see the status of a transaction hash and then finalize the withdrawal on L1 if the message status is ready for relay. It does this by creating a
CrossChainMessenger.