fix(checkout-widgets): Fetch pending withdrawals from the bridge contract#2680
Merged
Conversation
|
View your CI Pipeline Execution ↗ for commit d3d4049
☁️ Nx Cloud last updated this comment at |
keithbro-imx
changed the title
jeetparikh
reviewed
Aug 18, 2025
| const pendingWithdrawals = await tokenBridge.getPendingWithdrawals({ recipient }); | ||
|
|
||
| const transactions = (await Promise.all(pendingWithdrawals.pending.map(async (withdrawal, index) => { | ||
| const tokenMapping = await tokenBridge.getTokenMapping({ |
Contributor
There was a problem hiding this comment.
nice this is how you get the mapping
jeetparikh
previously approved these changes
Aug 18, 2025
jeetparikh
approved these changes
Aug 19, 2025
nattb8
approved these changes
Aug 19, 2025
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.
Hi👋, please ensure the PR title follows the below standards:
type(scope): message. For example:feat(passport): my new feature!after thetype(scope), for examplefeat(passport)!: my new breaking featureSummary
Replaces calls to the Checkout API with a direct calls to the RPC.
Detail and impact of the change
Added
Changed
Deprecated
Removed
Fixed
Security
Anything else worth calling out?