cBRL core contracts deployment#8803
Closed
luisgj wants to merge 10 commits intocelo-org:masterfrom
Closed
Conversation
yorhodes
approved these changes
Oct 20, 2021
Contributor
yorhodes
left a comment
yorhodes
left a comment
There was a problem hiding this comment.
Looks great!
We will need to make changes at the SDK level too
Contributor
|
#8334 fixes the exchange init params issue with the zero address for stableToken address |
Collaborator
|
We're gonna use #8831 instead |
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
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.
Description
Adds Proxy and Implementations for the
cBRLExchangeandStableTokencore smart contracts.Other changes
Adds migrations support for the cBRL token deployment process.
Tested
Testing ongoing.
Related issues
Backwards compatibility
This is backwards compatible as it does not introduce any changes to any core contract logic but rather just add new ones inheriting from their base implementations.
Documentation
Not sure yet.