Setup Admin and Oracle Authority #15
Merged
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.
Reworks the existing authorities to a more generic setup:
admin: for config field updates. This can be a multisig.
oracle_authority: for updates of history data. This has to be a hot wallet.
With the previous configuration, the stake_authority had the power to change itself. Because it had to be a hot wallet, it's much more likely to get compromised and could then update itself to an attacker's personal wallet with no recourse from the team. In this configuration, the admin multisig could set the oracle_authority to a new hot wallet if the current one has been compromised.