rooooooooob
rooooooooob
@MartinSchere @shroomist can you provide the utxos where you aren't able to?
@uac-nhan-nguyen see #246 we used to respect insertion order but we later made things be ordered canonically as several places require this ordering in order to work properly on Cardano....
>I understand from draft CIP 27 that this is an attempt to reduce size of the transaction message by removing the duplicate keys. It's not about the size. It's about...
@vsubhuman Can we close this please? We're already updated to `0.3.2` as of #154 in May.
I think it's a fair assumption that supplied inputs will be unique. We could also do the check earlier in `TransactionUnspentOutputs::add()` or do we have any reason to have duplicate...
At the very least we'll want to better document this quirk.
Hi @olliejm I'm on vacation right now but I did see your issue in the message signing lib. I'm not up to date with to what degree Nami follows the...
Maybe I'm misunderstanding it, but does [NativeScript::hash()](https://github.com/Emurgo/cardano-serialization-lib/blob/master/rust/src/lib.rs#L1618) help you? e.g. (the below code is for the rust lib not the wasm bindings) ```rust let script = NativeScript::from_bytes(hex::decode("cbor hex bytes go...
Hi @tankangliang this might be related to an open PR we have here #208 which due to a change in the alonzo format to add a field while keeping the...
@tankangliang are you still getting this issue? the linked PR was put into `9.1.2` release since that last comment and I believe that's likely the fix but it would be...