Open
Description
Neither of the two commands below is checking the tx-body/tx-file about a correct AuxDataHash for example.
$ cardano-cli transaction view ...
$ cardano-cli transaction txid ...
There is currently i think only the submit
stage that would unveil any inconsistency about that with a failing transaction.
But that could be way later in a processing chain and even more complicated with online/offline transactions.
So suggestion is to modify the commands above or introduce a new command like
$ cardano-cli transaction validate ...
with an errorcode return if a tx-body/tx-file cbor is completely valid in all points, including hashes before the signing.