This repository has been archived by the owner on Jan 24, 2024. It is now read-only.
fix(compound): Remove dangerous catch statement when retrieving underlying token address #869
Conversation
This file contains 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
volt62
pushed a commit
to volt62/zapper-studio
that referenced
this pull request
Aug 2, 2022
…lying token address (Zapper-fi#869)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
If the underlying address throws for whatever reason (even a timeout), we're defaulting to the zero address, and that ends up resolving to the ETH address, which bubbles up the wrong prices through the token structure.
Checklist
How to test?