-
Notifications
You must be signed in to change notification settings - Fork 2.6k
[NFTs] Allow to set the role to None #13591
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love PRs that minimise trust.
bot rebase |
Rebased |
Curious why there isn’t any change to the logic that checks those roles, since they’re optional now - that should have reflected on the check logic? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good, would still be nice to make sure the answers to my questions make it to github for posterity.
That's the beauty of that PR :) All the business logic is already in place and was mostly set here: #13482, so now if you remove the Admin role and the previous admin will try to call some admin-related method, the validation won't allow that. |
Only the collection's owner could unset the admin. |
bot merge |
* Allow to unset the role * Chore * Array instead of vec --------- Co-authored-by: parity-processbot <>
* Allow to unset the role * Chore * Array instead of vec --------- Co-authored-by: parity-processbot <>
This PR allows setting the Issuer/Admin/Freezer accounts to
None
without the ability to change it back (except for root calls).This is useful for cases when the collection is created, all the items are minted and now we want to be 100% sure no one will mint any more items, or change the metadata, or disable some item's transfer.