relayer: use resolver block number per chain #1961
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
GabrielBuragev
force-pushed
the
relayer/fix-ethereum
branch
from
90141bd
to
307ed8a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, the ethereum relayer service was only able to recover the L1 transaction hash for relays that happened on Mainnet as it was only using the
RESOLVER_DEPLOY_BLOCK_NUMBERfor L1 Mainnet.This PR adds the capability of recovering the L1 transaction hashes both on Testnet and Local net.
Note: This is properly addressed in #1804 by pulling the deployment infos from the npm package instead of having them hardcoded, so consider this a quick & temporary fix.