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
We recently became aware of an issue regarding a newly introduced signature checker that caused interruptions for one of our ecosystem projects. The affected contract was compiled and deployed before Nov 2022 and contained a specific struct type ability error that wasn't prohibited completely by the old Move compiler. No new modules deployed after Nov 2022 would be subject to this problem as the updated compiler strictly prohibits this case. We have also verified all modules deployed in mainnet to ensure no other modules are affected.
The proposal is to disable signature checker v2 to allow the affected module to resolve the issue.
The text was updated successfully, but these errors were encountered:
We recently became aware of an issue regarding a newly introduced signature checker that caused interruptions for one of our ecosystem projects. The affected contract was compiled and deployed before Nov 2022 and contained a specific struct type ability error that wasn't prohibited completely by the old Move compiler. No new modules deployed after Nov 2022 would be subject to this problem as the updated compiler strictly prohibits this case. We have also verified all modules deployed in mainnet to ensure no other modules are affected.
The proposal is to disable signature checker v2 to allow the affected module to resolve the issue.
The text was updated successfully, but these errors were encountered: