Open leobel opened 1 month ago
Redeemer is not a part of transaction body but the witness set, and transaction hash is a transaction body hash. So if everything else in the tx is the same it's expected behavior.
Redeemer is not a part of transaction body but the witness set, and transaction hash is a transaction body hash. So if everything else in the tx is the same it's expected behavior.
script_data_hash
is part of transaction body, so changes on the redeemer should be reflected on the transaction hash: https://github.com/IntersectMBO/cardano-ledger/blob/7358718500e9bf1adc78092bdcf90ee9c2231df7/eras/conway/impl/cddl-files/conway.cddl#L359
; This is a hash of data which may affect evaluation of a script.
; This data consists of:
; - The redeemers from the transaction_witness_set (the value of field 5).
; - The datums from the transaction_witness_set (the value of field 4).
; - The value in the costmdls map corresponding to the script's language
; (in field 18 of protocol_param_update.)
; (In the future it may contain additional protocol parameters.)
Hi, I've noticed that for slightly changes in a redeemer, I've only testes with changing some digits in a json numeric property but could be something deeper, the resulting transaction hash received by Aiken is the same.
Lucid Evolution
@lucid-evolution/lucid = "v0.3.49"
Aiken
Here is the smart contract:
You can reproduce the issue with this code
You can try with redeemers:
and
Transaction hash will be the same:
C5863C120096F9400EBDBFE2FF58F6FA3909E770D1D990AFDF28064946FFE78E