validate tx in evaluateTransactionExecutionUnits #2522
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This add one sanity check for the tx given to evaluateTransactionExecutionUnits, with the possibility of adding more later.
Jimbo4350
approved these changes
Nov 1, 2021
iohk-bors
bot
deleted the
jc/evaluateTransactionExecutionUnits-check-inputs
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds one sanity check for the transaction given to the helper function
evaluateTransactionExecutionUnits, with the possibility of adding more later.In particular,
evaluateTransactionExecutionUnitscurrently only checks for inclusion in the UTxO on those transaction inputs that are pointed at by some redeemer pointer in the transaction. This has the unfortunate side effect of havingtxinfosilently drop transaction inputs that are not legitimate when passing information to plutus.