Sebastien Guillemot

I also ran into this issue. I was hoping to do something like ```typescript type Foo = string; Record ``` But not only does this not work, `{ [key: Foo]:...

Other than the `.dot` output format missing the proper tabbing, this worked perfectly for me! Thanks a lot

Seems this is a duplicate of https://github.com/dropbox/dropbox-sdk-js/issues/162#issuecomment-364779780 (and a few other ones like #82)

Yes, the fact that we have an accessor is fine. The idea that we have some nonce that updates based off some deterministic function is fine. It doesn't explain why...

I believe the actual definitions for `addrattr` and `protocolMagic` actually should be ``` addrattr = { 0 : bytes .cbor addrdistr , ? 1 : bytes ; HDAddressPayload (but may...

This is the CDDL definition that worked for me ```cddl blake2b-224 = bytes .size 28 addressId = blake2b-224 ; blake2b-224 of sha256 of cbor(addrtype, spendingData, addrAttributes) stakeholderId = blake2b-224 protocolMagic...

For your above point, I'll try and look into this Related, but I also noticed that the definition of byron witnesses in post-Shelley (https://github.com/input-output-hk/cardano-ledger/blob/master/eras/babbage/test-suite/cddl-files/babbage.cddl#L356) should be `bytes .cbor addrAttributes`

I noticed that in the definition `address = [ #6.24(bytes .cbor ([addressid, addrattr, addrtype])), u64 ]`, the `u64` at the end is actually a `crc32`. What's strange is that the...

1. Make sure to run prettier on your code to make sure it passes CI 2. Please add a test so it's easy to know what changed and help avoid...

1. You may need a polyfill for text-decoder. This is a common issue with WASM on older platforms 2. Haven't heard of this before. Probably it's caused by a different...