You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
dev
9ac9cd952f
|
1 week ago | |
|---|---|---|
| .. | ||
| DateKeys_Protocol_Specification_v0.8.2.md | 1 week ago | |
| README.md | 1 week ago | |
| datekeys.cddl | 2 weeks ago | |
README.md
Specification
DateKeys_Protocol_Specification_v0.8.2.md: frozen copy of the normative draft v0.8.2 (28 September 2026) implemented by this module. SHA-256:5cfa32034ea2ba02e77676e015cad7bba09796383afdda6634aaa017a5a23351. v0.8.2 replaces v0.8.1 with a normative change to extensions, refined before release (error precedence, trust model, extension order, and rules the reference had applied without normative text), amended (the canonical encoding of BLS12-381 points and the tlock stanza body) and corrected in two rounds of a formal review (an invalid release from a network source, the objects and arrays where each extension may appear, which an encoder must respect, the serialization of GT in the tlock H2, and a single code for any failure of a release source), all recorded with their reproducible cases in the specification's §76.datekeys.cddl: the CBOR schemas of the specification as implemented, with the encoding rules CDDL cannot express.
The specification is licensed under the Creative Commons Attribution 4.0 International License (CC-BY-4.0): https://creativecommons.org/licenses/by/4.0/. The code of this repository is licensed separately under Apache-2.0.
Changes to the specification follow its §76: a normative change should answer a reproducible case found through the reference implementation, the CDDL, a fixture, a mutation test, an interoperability test, fuzzing, a second implementation or an external review.