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

Question about txInfoData #2649

Closed
L-as opened this issue Feb 8, 2022 · 7 comments
Closed

Question about txInfoData #2649

L-as opened this issue Feb 8, 2022 · 7 comments

Comments

@L-as
Copy link

L-as commented Feb 8, 2022

Are there any restrictions on what can be put in txInfoData? Can we put arbitrary extra data into it for use in scripts?

@JaredCorduan
Copy link
Contributor

No, there is no way to put any extra/auxiliary data into the transaction context. Any data that you want to pass to a Plutus script should be passed via the redeemer.

@L-as
Copy link
Author

L-as commented Feb 8, 2022 via email

@L-as
Copy link
Author

L-as commented Feb 8, 2022 via email

@JaredCorduan
Copy link
Contributor

@L-as in general, https://cardano.stackexchange.com is a better place to ask questions, the issues here are really for the ledger team to track work. And CIPs are the better place to propose new ideas: https://cips.cardano.org

I think it is more likely that we would add a builtin hash function for Plutus than that we would allow data in addition to the redeemer, just for the purposes of getting a hash. But this is just my first impression, take it with a grain of salt. :)

@L-as
Copy link
Author

L-as commented Feb 8, 2022 via email

@JaredCorduan
Copy link
Contributor

Np, glad you are interested in Plutus and how we can make it better!

@JaredCorduan
Copy link
Contributor

@L-as you'll be happy to see this: cardano-foundation/CIPs#218 :)

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

No branches or pull requests

2 participants