Skeleton of passing redeemers in TxInfo #2443
Closed
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.
@JaredCorduan this is as far as I've got, I'll see if I can do the conversion functionality after lunch, otherwise it's in your court!
The plutus commit is based on our
release/alonzo
branch, so should just be one commit on top of what you had previously, and all that does is add the extra field toTxInfo
.As we discussed, Jared, the type of
txInfoRedeemers
is[(ScriptPurpose, Redeemer)]
.(I'm targeting
plutus-staging
so we can review this PR independently without merging it into master, then we can mergeplutus-staging
into master if we decide to ship the change.)