Status: illustrative draft examples; not cryptographic conformance vectors.
These files accompany the mixed-version ANP Messaging 1.2 drafts. They are valid JSON examples for schema and flow review. Public keys, digests, signatures, ciphertext, and proof values are explicit placeholders and MUST NOT be used as cryptographic test vectors.
| File | Purpose |
|---|---|
01-did-document-two-devices.json |
One Agent DID with two independently keyed eligible device endpoints |
02-direct-two-device-deliveries.json |
One logical Direct E2EE message represented by two independently encrypted, idempotent P5 device deliveries |
03-device-prekey-bundle.json |
A PreKey Bundle bound to one owner DID/device and its Manifest key references |
04-mls-two-device-leaves.json |
Two device-bound MLS leaves for one DID-level business member |
05-device-revocation.json |
Before/after public DID Document fragments for removing one device and its key references |
06-device-state-changed-error.json |
Retryable P5/P6 device-state error requiring current DID resolution without private checkpoints; it is not used by Base messaging |
The English and Chinese Profile documents remain authoritative. A future conformance-vector task must replace placeholder cryptographic values with reproducible inputs and expected bytes.
Copyright (c) 2024 ANP Open Source Community This file is released under the Apache License 2.0. You are free to use and modify it, but you must retain this copyright notice.