You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For future use cases related to permission management, it is useful to have the ability to change the owner of the contract.
Additional context
This is likely needed for Zedger as well.
Possible Solution
Add an uplink API function which will provide the ability to change/set another owner. This is sufficient for contracts to incorporate a more sophisticated ownership management. Any contract using uplink can then expose functions that verify that the owner is calling a change owner function, and only then call the actual change function, or other two-step approaches (change & accept).
The text was updated successfully, but these errors were encountered:
After some consideration, I think that we should not add contract's ability to change/set its owner. In some likely scenarios users may want to deploy some contracts whose code they do not understand and do not control. They would only trust that the contract works as advertised and that they remain the owner of it. It would be against interest of such users that the contract can free itself of their ownership. Hence, in my opinion such api should not be allowed and the corresponding (to this issue) scenarios should be realised by other means.
In other words verification that the party changing the owner is the current owner cannot be performed at contract's discretion, it needs to be done at the system level IMO.
Summary
For future use cases related to permission management, it is useful to have the ability to change the owner of the contract.
Additional context
This is likely needed for Zedger as well.
Possible Solution
Add an uplink API function which will provide the ability to change/set another owner. This is sufficient for contracts to incorporate a more sophisticated ownership management. Any contract using uplink can then expose functions that verify that the owner is calling a change owner function, and only then call the actual change function, or other two-step approaches (change & accept).
The text was updated successfully, but these errors were encountered: