feat(Upgradable)!: use Acl for authorization #85
Merged
Conversation
Previously authorization was based on `Ownable`.
mrLSD
approved these changes
Jan 26, 2024
This was referenced Mar 27, 2026
Closed
Closed
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.
Previously
Upgradableauthorization was handled byOwnable. An explanation of how to useUpgradablewith Acl is available in the example contract.Acl Roles
Use cases which don’t require fine grained permissions can define only a single role and whitelist it for all
Upgradablefeatures. SeeRole::DAOin the example contract.The other roles show how to achieve more fine grained permissions by whitelisting a role only for a subset of the
Upgradablefeatures.Edit: Some advantages of using Acl: