feat(rollup): add fallback if TransactionByHash fails in getting commitBatch calldata #601
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.
1. Purpose or design rationale of this PR
The transaction indexing of a geth node is controlled by
--txlookuplimit
flag, which indicates the number of recent blocks to maintain transactions index, thus in some cases, the l2geth node cannot successfully fetch old transactions to get commitBatch's calldata. To solve this issue, this PR:TransactionByHash
fails in gettingcommitBatch
calldata.Related issues and discussions:
TransactionByHash returns null
TransactionReceipt returns null
Local test (you may need to tweak some code to go into fallback path):
2. PR title
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:
3. Deployment tag versioning
Has the version in
params/version.go
been updated?4. Breaking change label
Does this PR have the
breaking-change
label?