-
When using negative numbers in `Value::from()` I get off by one (e.g. `Value::from(-3)` serializes to the bytes `22` which is negative 2). I think that's because this line is wrong; https://github.com…
hansl updated
2 years ago
-
## Issue Description
Test scripts appear to not deal correctly with a properly tagged (0) time string (https://datatracker.ietf.org/doc/html/rfc8949#section-3.4.1) according to RFC7049 (https://dat…
dirkx updated
3 years ago
-
**Internal/External**
*External* otherwise.
**Area**
*Native Tokens* Related to Native Tokens (Mary).
**Summary**
Not a bug per se, but at least complication/blocker when it comes to int…
-
Maybe I'm wrong but It seems to me currently there is no support for Date type.
Is it something planned to support date like defined in RFC7049§2.4.1 ?
-
Operations to support encoding and decoding CBOR
See https://tools.ietf.org/html/rfc7049
Danh4 updated
3 years ago
-
- [x] 1. -----
As noted by the shepherd, the document should point to 3205 in the abstract and in the introduction to mention it obsoletes it. From https://www.ietf.org/standards/ids/checklist/: "I…
-
I just checked the code for the preparation of the token bundle for Ledger: https://github.com/vacuumlabs/adalite/blob/develop/app/frontend/wallet/shelley/shelley-ledger-crypto-provider.ts#L206 and it…
-
CBOR can represent a time stamp both as an int and as a string. However, the schema states that timestamps should be strings:
```
"sc": {
"description": "Date/Time of Sample Coll…
-
Inspired partly by Carsten's work on the terminology, I noted [this text](https://httpwg.org/http-extensions/draft-ietf-httpbis-bcp56bis.html#name-defining-message-payloads):
> There are many poten…
-
At present, the deterministic canonical form for CBOR is meant to apply to all CBOR-based formats. The rules in the specification today are as follows:
Property names MUST be represented as text …