-
Notifications
You must be signed in to change notification settings - Fork 156
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
Comments
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. |
Would you be open to removing this restriction?
|
This would be a possible alternative to adding something like `dataHash :: BuiltinData -> BuiltinByteString` to UPLC as a built-in.
|
@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. :) |
Thanks! Considering we seemingly already have the approval for adding `dataHash`, I'll just do that.
Wasn't sure where to post this initially, didn't know there was an active stack exchange.
|
Np, glad you are interested in Plutus and how we can make it better! |
@L-as you'll be happy to see this: cardano-foundation/CIPs#218 :) |
Are there any restrictions on what can be put in
txInfoData
? Can we put arbitrary extra data into it for use in scripts?The text was updated successfully, but these errors were encountered: