Freeze bank settings #261
Merged
Freeze bank settings #261
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.
Adds the ability for the group/bank admin to freeze a bank's settings, preventing them from ever being configured again. This will be used in permissionless pools to prevent the pool administrator from trolling by setting interest to 400%, replacing the oracle, etc.
Fixes a bug where config did not update the origination fee rate.
Updates TS test suite with new reference types to be ported to the package for updates to date.
Possible TODO: add an unfreeze that can only be executed by the org's multisig to handle edge specific edge cases.