Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
👋 aelmanaa, thanks for creating this pull request! To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team. Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks! |
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
2 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.
This pull request adds support for the FUSD (FinChain Dollar) token across multiple mainnets in the configuration files. The changes include defining FUSD token metadata for several networks and configuring its rate limiter settings in the
lanes.jsonfile.Token configuration additions:
avalanche-mainnet,mainnet,solana-mainnet, andsonic-mainnetintokens.json, including details likedecimals,name,symbol,poolAddress, andtokenAddress.Rate limiter configuration:
lanes.jsonwith arateLimiterConfigwhere both inbound and outbound limits are disabled (isEnabled: false,capacity: "0",rate: "0"), ensuring no rate limiting is applied to FUSD transfers. [1] [2] [3] [4] [5] [6]