Conversation
…ct token approval
Contributor
|
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
Collaborator
Builds ready [0425660]
Page Load Metrics (584 ± 58 ms)
|
darkwing
approved these changes
Mar 30, 2021
Contributor
darkwing
left a comment
There was a problem hiding this comment.
Excellent, my swaps all worked great!
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Found during QA of v9.3.0
The problem was that we had one hard coded instance of the mainnet swaps contract address. This was being used when checking whether a token had been approved. This PR fixes the issue by making the contract address network specific via
SWAPS_CHAINID_CONTRACT_ADDRESS_MAP[chainId]