feat: check finalized on custom usdc bridge contract #169
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
✅ Deploy Preview for portal-sophon-testnet-xyz ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
AmarildoGrembi
requested changes
Sep 25, 2025
consvic
approved these changes
Sep 25, 2025
AmarildoGrembi
approved these changes
Sep 29, 2025
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.
"A user who claimed his fund on the official bridge is still being seen as claimable even if it's claimed"
For USDC, we need to check using the custom bridge contract. The issue is that the SDK uses the wrong bridge address for USDC. We need to call isWithdrawalFinalized on the correct bridge contract directly.