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
In C1.0 contract update validator, If there is a custom type change rule, always use that, and only that.
i.e: Mandate using the custom type change rule, if exists.
Do not use that as the back-up, or do not fall-back to the "default" type equality checking, as it will allow two-paths/two-ways of updating the contract, which may not be supported by the storage value migrations.
Suggested Solution
No response
The text was updated successfully, but these errors were encountered:
Issue to be solved
In C1.0 contract update validator, If there is a custom type change rule, always use that, and only that.
i.e: Mandate using the custom type change rule, if exists.
Do not use that as the back-up, or do not fall-back to the "default" type equality checking, as it will allow two-paths/two-ways of updating the contract, which may not be supported by the storage value migrations.
Suggested Solution
No response
The text was updated successfully, but these errors were encountered: