-
Notifications
You must be signed in to change notification settings - Fork 23
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
[FR] - Capability to add additional data in a body content #600
Comments
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days. |
Following a discussion I had on Discord, it was confirmed that this feature is not currently present. I will work on a contribution to integrate it. |
Just realized that the issue is most likely the same when consuming inputs from pkh with a hashed datum. All indicate that there would currently be no way to provide the associated datum in the body. |
Closed by #640 |
Internal/External
External
Area
Plutus
Describe the feature you'd like
At the moment, it does not seem possible to pass additional data in the form of a correspondance between a datum hash and a datum in a transaction body, in addition to the one collected from the script witnesses in inputs, and the outputs of the body.
However, when referencing a utxo which happens to have a hashed datum, this is needed.
Indeed, in function
mkShelleyTransactionBody
we can see that theHashableScriptData
are derived from the body itself, from the two locations mentioned above, as follows:Then, the verification hash of the body is computed from these data using
convPParamsToScriptIntegrityHash
, and is wrapped as well in the Shelley transaction body. As a consequence, there seem to be no builtin way to have additional data in the resultingShelley
transaction body.My feature request is to have such a way of including additional data in the transaction body.
This could take several forms, such as:
TxBodyContent
structuremkShelleyTransactionBody
functionDescribe alternatives you've considered
For now, I have used the following work-around:
mkShelleyTransactionBody
convPParamsToScriptIntegrityHash
This does allow the ledger to generate the proper script context but it does not feel like the proper way to achieve this result.
The text was updated successfully, but these errors were encountered: