CombinedRateProviderFactory #12
Open
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
Adds contract for CombinedRateProviderFactorty and CombinedRateProvider. The purpose of these contracts is to combined two rates in scenarios where the common denomination of assets is not uniform. For example, a rate provider denominated in wstETH and another in wETH cannot be used in a pool pairing. Combining the wstETH denominated rate with wstETH's known rate provider solves this issue with a new contract.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds contract for CombinedRateProviderFactorty and CombinedRateProvider. The purpose of these contracts is to combined two rates in scenarios where the common denomination of assets is not uniform. For example, a rate provider denominated in wstETH and another in wETH cannot be used in a pool pairing. Combining the wstETH denominated rate with wstETH's known rate provider solves this issue with a new contract.
Verified Deployments:
Base
Factory: https://basescan.org/address/0x40b48e1eb72c62f7201b4c2621df7d822ccb9944#code
Deployment https://basescan.org/address/0xbB44C335593C79b4807cb76e5EBC3a4fF5c9b8B8#code
OP
Factory: https://optimistic.etherscan.io/address/0x7d9507014cc564e3b95e4d0972a878d0862af7ae
Deployment: https://optimistic.etherscan.io/address/0x75ab951aec0ff692225e440f96d3f5a16befac3b
Arbitrum
Factory: https://arbiscan.io/address/0x26dec0e6a4249f28e0f16a1a79808bf9ba308310#code
Deployment: https://arbiscan.io/address/0x998DE64cB90EdF3d205CFDB864E199fDA4d55710#code
Mainnet
Factory https://etherscan.io/address/0xd2cd8027f8c4b8ddcd1bfcd4e47587f41f2712f2
Deployment https://etherscan.io/address/0x3ba1a97D96F53611C4b2A788A5aa65c840d94c54