Open
Conversation
Changelog ReminderReminder to update the CHANGELOG.md for any of the modified packages in this PR.
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
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 PR adds tooling for deploying and enabling yield backends.
Much of the code added here is generic and to be used for other ops too going forwarded (related to truffle being deprecated).
Typically setting up a yield backend involves the following steps:
(The second step is needed because unlike for
updateCode, there's no code in the host and governance contract for calling the permissioned functions for controlling a yield backend.Meaning, for SuperTokens using a yield backend, the governance owner directly interacts with the SuperToken contract, without the calls being routed through 2 other contracts. This may change in the future, e.g. in case many SuperTokens get a yield backend, and/or if the current contract size limit is lifted)
Here's the commands used to deploy yield backends and create related gov/admin actions for USDCx on 2 networks:
Aave yield backend for USDCx on base-mainnet
Spark yield backend for USDCx on eth-mainnet
More context: https://github.com/superfluid-org/protocol-monorepo/wiki/Yield-Backend