-
Notifications
You must be signed in to change notification settings - Fork 81
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
Support dry run mode in the FuelVM #691
Comments
We don't have plans to work on it before mainnet since it may bring vulnerabilities. |
Good job |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem overview
The FuelVM has many rules regarding transaction validity and requirements for using specific opcodes. Each opcode that touches the contract requires this contract's existence in the transactions' inputs. Another example is the
tro
opcode that requires the existence of theVariable
output.All those rules make the usage harder and require dry-running transactions many times on the SDK side to fulfill all rules.
Solution
The FuelVM may support dry run mode, in which all validity rules will not abort the execution immediately. Instead, we will keep a record of what rules are failing and provide feedback at the end of the execution with all problems.
The text was updated successfully, but these errors were encountered: