fix: sequential build and sign messages #7018
Merged
Conversation
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
bhavidhingra
force-pushed
the
coin-5426-sequential-receive-address-signing
branch
from
8d61575 to
c5ec2ad
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.
This pull request updates the message signing logic in
signAccountBasedMidnightClaimMessages.tsto improve reliability. The most significant change is switching from parallel to sequential processing of messages, which can help avoid issues related to concurrency and resource usage.Message signing logic:
Promise.all) to sequential iteration in thebulkSignAccountBasedMessagesWithProviderfunction, ensuring each message is signed one after another with a newWalletinstance.TICKET: COIN-5426