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
The comment above the dispatchable start_destroy which implies that the asset should be frozen in order to start destroying the asset, is not true. Either this comment should be removed or there is a bug.
The text was updated successfully, but these errors were encountered:
Fix#5184
`owner` can set himself as a `freezer` and freeze the asset so
requirement is not really needed. And requirement is not implemented.
---------
Co-authored-by: Bastian Köcher <git@kchr.de>
Co-authored-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
The comment above the dispatchable
start_destroy
which implies that the asset should be frozen in order to start destroying the asset, is not true. Either this comment should be removed or there is a bug.The text was updated successfully, but these errors were encountered: