-
Notifications
You must be signed in to change notification settings - Fork 94
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
continue-on-error foundations: refactor verification to a separate trait #918
Conversation
fuel-vm/src/verification.rs
Outdated
where | ||
Self: Sized + Seal, | ||
S: InterpreterStorage, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need S
here at all? Based on the use cases that we discussed, it looks like we don't need it anymore=)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
True. Removed in 9cc0677.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me=)
Co-authored-by: Green Baneling <[email protected]>
Co-authored-by: Green Baneling <[email protected]>
Co-authored-by: Green Baneling <[email protected]>
Co-authored-by: Green Baneling <[email protected]>
Co-authored-by: Green Baneling <[email protected]>
Co-authored-by: Green Baneling <[email protected]>
…un (#2840) This change starts using the FuelLabs/fuel-vm#918 feature for the `asemble_tx` endpoint. --------- Co-authored-by: Mårten Blankfors <[email protected]> Co-authored-by: AurelienFT <[email protected]> Co-authored-by: Aaryamann Challani <[email protected]>
Work towards #691
Follow-up: #915
Moves some parts of tx verification logic to a separate trait so it can be replaced. This initial PR only moves "is contract in inputs" check. More rules can be migrated as they are needed.
This is a breaking change, as we need to add a new type parameter to the VM. While the default value keeps the same behavior, existing trait implementations might still break.
The new trait is fully sealed: it cannot be implemented outside fuel-vm, and it's methods cannot be called outside it. This means adding or removing methods is not a breaking change in the future.
In addition, an internal
InputContracts
type is removed and it's field flattened on the containing structs.Checklist
Before requesting review