-
Notifications
You must be signed in to change notification settings - Fork 86
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
Fanout and Decommit transactions don't include datum hash in outputs #1598
Comments
Hey @Micrograx thanks for reporting this! I've tried to put together some end-to-end tests on hydra to assert this behavior but could not reproduce the issue using all three ways (committing a script to a Head, decommiting a script UTxO and L2 transaction with datum hash in the output). Could you perhaps provide more info on your workflow, how are you constructing the transactions, which library and versions? Anything that could help us pinpoint where the issue might be? |
Hi @v0d1ch, thanks for your patience. We've continued our testing using inline datums as described in the workaround section. I'll try to reproduce the issue in the 0.19.0 version of the hydra node and share more details next week. In short we've been doing all transaction building with the cardano-cli, and we were using the |
No worries, thanks for the info 🙏 |
I was using version |
Going to close this now; but please do re-open if it occurs again! Thanks for reporting :) |
Context & versions
cardano-node: 9.1
hdyra-node: 0.18.1
cardano-cli: 9.2.1
Steps to reproduce
Actual behavior
The submission of the transaction to the L1 will fail because the datum hash will not be included in the script UTxO
Expected behavior
Transaction should be submitted without issues
Workaround
Use inline datums or modify the transaction cbor to include the datum hash in the output. For the latter, you can get the transaction cbor from the hydra-node logs.
The text was updated successfully, but these errors were encountered: