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
{{ message }}
This repository has been archived by the owner on Nov 22, 2023. It is now read-only.
Summary or problem description
The scenario is that a contract manifest has a faulty offset to a method. The offset points outside of the contract script's bounds. When deployed and invoked the neo-vm returns a null StackItem of type ANY and in state HALT.
Do you have any solution you want to propose?
In my opinion it is more reasonable and less confusing to return FAULT in such a scenario.
Additionally, as a developer making a invokefunction, call it is desirable to receive more information about why the neo-vm faulted. But that is not the main concern of this issue.
The text was updated successfully, but these errors were encountered:
Summary or problem description
The scenario is that a contract manifest has a faulty offset to a method. The offset points outside of the contract script's bounds. When deployed and invoked the neo-vm returns a null StackItem of type ANY and in state HALT.
Do you have any solution you want to propose?
In my opinion it is more reasonable and less confusing to return FAULT in such a scenario.
Additionally, as a developer making a
invokefunction
, call it is desirable to receive more information about why the neo-vm faulted. But that is not the main concern of this issue.The text was updated successfully, but these errors were encountered: