Refactor transaction processing to improve shard block fetching - #26
Merged
Conversation
- Introduced a new method `fetchNextShardBlock` to encapsulate the logic for fetching the next shard block, improving code readability and maintainability. - Replaced the previous inline logic with a Promise.all call to fetch shard blocks concurrently, enhancing performance. - Retained existing logging for debugging purposes while streamlining nonce handling logic.
stefangutica
approved these changes
Sep 10, 2026
claudiulataretu
approved these changes
Sep 10, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
fetchNextShardBlockto encapsulate the logic for fetching the next shard block, improving code readability and maintainability.