-
Notifications
You must be signed in to change notification settings - Fork 35
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
TransactionHash Mistmatch #314
Comments
@rooooooooob is this the same as the other issue you've been investigating? |
@SebastienGllmt no it's not. Mine was I think a Plutus script hash mismatch or missing witness (due to script hash mismatch I think because it was there) or something to do with Plutus. |
This issue happens when you make a time lock script (native minting policy) , and you add the minted asset to the Tx, when you remove the mint field the Tx hashes from lucid and CML match, but when you add the mint field they returned different hashes.
so basically the time lock script needs requires these 2 fields, 3 ->
. I can send you the Tx example, if needed |
This only concerns the free-floating `hash_transaction()`. Fixes #314
@solidsnakedev immediate workaround: use For some reason the free-floating one was hashing the canonical CBOR. You would want to have canonical CBOR for e.g. hardware wallets, but your entire TX should be canonical not just when you go to hash it or otherwise it won't match up with the CBOR. Eventual fix: #321 |
* TX hash mismatch for non-canonical TXs This only concerns the free-floating `hash_transaction()`. Fixes #314 * *TxBody.hash() for multi-era rework Use `TransactionBody` instead of of [u8; 32] to be consistent with `hash_transaction()`. Moves all the functions that were added directly to `mod.rs` in #298 files to `utils.rs` files where they should be since they aren't auto-generated.
I'm not sure why CML produces a different tx hash compared to Lucid CML
CML example
the output is the following
txhash CML 3ea6919295e402b9cf13afdc0f45104f9a91d299b896812f363bb8cc0f80f0a3
Lucid example
the output is the following
lucidTxHash 2548148ad0fb809b5756c6f8b8e1d3e705f0c4cda44af6163d6b766786d061ec
The problem I have is when using CML, Blockfrost returns the following error
The text was updated successfully, but these errors were encountered: