SOR support for wrapped rebasing tokens using the generic unbutton wrapper #224
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
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.
The unbutton wrapper is a ERC-20 wrapper which wraps any generic rebasing ERC-20 token into a non-rebasing, fixed balance version.
For example:
Wrapped Ampleforth (WAMPL) is a non-rebasing version of the AMPL ERC-20. LPs create BalV2 pools using WAMPL. When traders want to trade AMPL, the sor calculates the exchange rate between AMPL/WAMPL and routes trades through the WAMPL pools. (similar to the existing stETH/wstETH implementation).
The current will allow the SOR to handle any rebasing tokens as long as they use the the generic "unbutton" wrapper without any custom integration.