-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RPC test invokes running out of GAS #396
Comments
RpcServer should still have some GAS limit to protect itself from malicious script hogging CPU, but yeah, it should allow more than 10 GAS. |
It's up to owners of RPC nodes to allow more than 10 GAS at this point. Nodes default to 10 to protect from long running scripts on public nodes by default. |
Would it be an idea for NEON and other wallets to use |
* started changing en version * italian version * small changes
Users in the Discord #support channel have reported instances of Neon token balances not displaying, while NEO/GAS balances were correct. I traced this to an RPC issue in Neo 2.9.0 nodes.
Due to the refactoring that occurred in (#288)
ApplicationEngine.Run
can now be passed the optionaltestMode
flag directly, which defaults to false.However, the
invoke*
RPC calls in RpcServer.cs still callApplicationEngine.Run(script)
only, meaning the invocation will not run in test mode, and will abort after exceeding 10 GAS in execution time.The token balance query in Neon requires far more than 10 GAS to execute due to the large number of NEP-5 contracts now deployed on the network. So the FAULT condition in 2.9.0
invokescript
calls leads to no tokens being displayed.I believe the
GetInvokeResult
call in RpcServer.cs should passtestMode=true
toApplicationEngine.Run
to return to the previous behavior.The text was updated successfully, but these errors were encountered: