Cardano Stack Exchange is a question and answer site for users and developers of the Cardano cryptocurrency ecosystem. It only takes a minute to sign up.
Sign up to join this community
I noticed that TxInfo datatype has a txInfoData field which carries a list of mappings from datum hashes to datum values. This seems very useful for validating transactions with multiple input UTxO's.
Where and how is this list provided while creating a transaction?
There are at least two reasons for that field to be a list:
Using cardano-cli transaction build, we can provide a datum value for each input UTxO with --tx-in-datum-file (or --tx-in-datum-value). And also, for each output UTxO we can provide a datum value with --tx-out-datum-embed-file (or --tx-out-datum-embed-value).
--tx-out-inline-datum-file and --tx-out-inline-datum-value will also be available.
TxInfoData can be obtained via the ScriptContext that is included as part of every transaction. The list of datum and datum hashes is created when the transaction is submitted and made available to the plutus script. Here are the relevant plutus docs https://playground.plutus.iohkdev.io/doc/haddock/plutus-ledger-api/html/Plutus-V1-Ledger-Contexts.html Hope this helps.
