rooooooooob

@anon-real Sorry for the delay, but can you post the JSON contents of the TX you sent to get this issue? I took a look at the UI code for...

@anon-real We just released a new Yoroi nightly. It has a fix for #2170 among other issues so it might be worth seeing if for some reason this issue is...

>current version of cml parsing fails at an early block in sancho @ecioppettini hopefully dcSpark/cardano-multiplatform-lib#324 will fix it. I'll test out syncing sancho later after I update multi-era (soon).

#210 addresses this for basic groups but the issue remains for other types e.g. `[uint]`. This is lower priority because the only time we've seen single element arrays like this...

It should be worth noting that `big_int` (defined in `conway.cddl`), while very similar, is _**NOT**_ the same as the `bigint` defined in the CDDL/CBOR RFC spec. ```cddl big_int = int...

@SebastienGllmt I updated this and fixed the issues we had with things like `shelley_ma`, etc. The general approach seems to be to either do `ShelleyMA` or for general cddl consistency/similarity...

It's not our code that is giving the errors, but the CDDL parsing library we use. I see you already made an issue there (anweiss/cddl/issues/199). Could you provide your own...

What do you want the output generated to look like for `CommandIDs`? The way we handle basic groups like that we tend to create a struct with the fields you...

@nslowell I got the array struct deserialization with optional fields working: #204 Note: regarding the `.le` on the integers we still generate without errors, they're just ignored. So the deserialization...

>I don't see anything in the RFC about using "; @ label" but I do seem sentences like: It's a non-standard thing. The RFC specifies comments as `;` but they...