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
This action is quite critical and executes it without confirmation. If owner e.g. accidentally does this, contract will be immutable once and forever.
I believe existing TransferOwnership action can be adjusted by having new_owner: Option<String> instead of new_owner: String. Then in AcceptOwnership we just need to check whether sender is owner and then set owner None. This way RenounceOwnership would be obsolete.
I don't think this is worth changing the API for. Having the ability to do destructive actions will always be present when managing smart-contracts. It's up to the person(s) that manage these smart-contracts to ensure that only the correct calls are performed. Be it through the use of a multi-sig or other tooling.
This action is quite critical and executes it without confirmation. If owner e.g. accidentally does this, contract will be immutable once and forever.
I believe existing
TransferOwnership
action can be adjusted by havingnew_owner: Option<String>
instead ofnew_owner: String
. Then inAcceptOwnership
we just need to check whether sender is owner and then set ownerNone
. This wayRenounceOwnership
would be obsolete.@larry0x, wdyt?
The text was updated successfully, but these errors were encountered: