Skip to content
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

Skeleton of passing redeemers in TxInfo #2443

Closed
wants to merge 2 commits into from

Conversation

michaelpj
Copy link
Contributor

@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 to TxInfo.

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 merge plutus-staging into master if we decide to ship the change.)

@michaelpj michaelpj changed the base branch from master to plutus-staging September 2, 2021 11:45
@JaredCorduan
Copy link
Contributor

The changes in this PR will appear in #2485.

@JaredCorduan JaredCorduan deleted the mpj/txinfo-redeemers branch August 10, 2022 02:03
@JaredCorduan JaredCorduan restored the mpj/txinfo-redeemers branch August 10, 2022 02:03
@JaredCorduan JaredCorduan deleted the mpj/txinfo-redeemers branch August 10, 2022 02:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants