feat(StakeManager) Implement Access Control system inside the StakeManager #253
Conversation
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.
Description
This PR implements RBAC inside StakeManager to be able to support new "guardian" role.
Implemented roles:
Admin (DEFAULT_ADMIN_ROLE) - Previously handled by Ownable contract, now Admin inside RBAC.
Rewards Supplier (REWARDS_SUPPLIER_ROLE) - Previously a simple variable with a setter, now handled by RBAC
Guardian (GUARDIAN_ROLE) - Newly introduced role which is able to put StakeManager into emergency state.
Change list:
TrustedCodehashAccess.sol, replaced withAccessControlUpgradeable.solChecklist
Ensure you completed all of the steps below before submitting your pull request:
pnpm adorno?pnpm verify?