The history consists of a set of JSON-formatted arrays. Each line is in the format: [version hash, version ID, timestamp, params, data, proofs] Within each line the properties are as follows: version hash : The hash corresponding to the current line. See version hash calculation. version ID : An incrementing integer value corresponding to the line index. The first line is index 1.

Header line first line of the log establish log format and base protocol place to override parameters like the hash function used list any relevant extensions Examples: ["history:1", "did:webnext:1", {}] ["history:1", "did:webnext:1", {"ext": ["ML-KEM"]}]

--- tags: aries --- # DIDcomm Envelope Structure notes ## Outer Envelope ```jsonc { "protected": { // Encoded a base64-url string "typ": "prs.hyperledger.aries-envelope", "cty": "msgpack", "alg": "ECDH-ES+XC20PKW", "enc": "XC20P" }, "recipients": [ // CEK encrypted to each recipient // Includes ephemeral (anoncrypt) or sender key (authcrypt) ], "aad": "", // AEAD authenticated data (possibly implicit) "ciphertext": "", //

--- tags: aries --- # Indy SDK method dependencies ## Crypto `create_key` - `crypto_service.create_key` - `wallet_service.add_indy_object` (pub/priv key) `crypto_sign` - `crypto_service.validate_key` (NYI) - `wallet_service.get_indy_object` (key by verkey) - `crypto_service.sign` (uses libsodium) `crypto_verify` - `crypto_service.validate_key` (NYI) - `crypto_service.verify` (uses libsodium) `set_key_metadata` - `crypto_service.validate_key` (NYI) - `wallet_service.upsert_indy_object`

--- tags: aries --- # Aries Queue Management Protocol (Draft) An agent may choose to provide a message queue for other agents it has formed pairwise connections with. This protocol provides a way to inspect or change the properties of that queue and request for messages to be returned. ## Requesting the current queue status The `status-request` message is used to inquire about the current queue status. It does not take any properties. For example: ```json { "@id": "123456780", "@typ