# atproto spaces test vectors Test vectors for the building blocks `SPACES.md` defines, one file each: | File | Holds | | --- | --- | | `kem.json` | the KEM shared secret, HPKE's secret export, from an author's P-256 private key and a syncer's key share; the first case is RFC 9180's test vector A.3.1 (DHKEM(P-256, HKDF-SHA256)), and the second HPKE's own test vector for the Export-only ciphersuite | | `lthash.json` | LtHash digests, and one whole state | | `mac.json` | commit and record MACs: the request, the covered header, the signature base, the MAC and the response headers; and `Accept-Signature` headers read | | `http-signature.json` | the HTTP Message Signature of a request made with a space credential, valid or not | | `repo-star.json` | space repos as STAR archives (profile `atproto-space-repo`), to write, to read, and to refuse | Each file's `description` says how to read its cases. Binary values are lower-case hex. Every case agrees with the reference library (`@atproto/space` and `@atproto/star` of the pinned spaces alpha) and with the harness's own code written from `SPACES.md`: `harness/spaces/vectors.mjs check` holds each to both, and `make` writes them again; the one case the reference library cannot take, `kem.json`'s second, whose `info` is its own, is held to the harness's code alone. Private keys here are made from fixed strings for these vectors alone. Made for this repository, and licensed as the rest of `interop/` is (`../LICENSE-CC0`), except the RFC 9180 values in `kem.json`, and its HPKE test vector (`../../spaces/README.md`), which are the IETF Trust's (`../../spaces/rfc9180.txt`).