didcomm-messaging
didcomm-messaging copied to clipboard
decentralized-identity
Noticed when reading through that we're specifying the file extensions, but not sure if these need to be registered anywhere. I couldn't find any where they needed to be, so...
Using the [Alice / Bob Identities and secrets (private keys) that already exist in the spec](https://identity.foundation/didcomm-messaging/spec/#appendix-a-secrets-for-test-vectors), encrypt the following DIDComm message: ``` { type: 'https://didcomm.org/trust-ping/2.0/ping', from: 'did:example:alice', to: 'did:example:bob', id:...
This just popped in my head. Has anyone thought about how we'd list multiple URLs in order to send different DIDComm Messages. I'd suspect we could go two ways. Either...
I'm wondering if there's a particular reason why triples are preferred for the `l10n` extension in the `inline` strategy. Why not resort to maps for less duplication and simpler translation...
It seems that a similar issue has already been discussed here in #294, but the fix in #352 doesn't solve the problem as far as I understand. See for further...
In [9.5.3 Message Correlation](https://identity.foundation/didcomm-messaging/spec/#message-correlation) we read: **_"The id of the message passed in a URL or a QR code is used as the pthid on a response sent by the...
Is the above attachment content really valid? (i.e. a string value for type `json`) If not, Base64 URL Encoded value cannot be right. [didcomm-jvm](https://github.com/sicpa-dlab/didcomm-jvm/blob/main/lib/src/main/kotlin/org/didcommx/didcomm/message/Attachment.kt#L25) does not accept it CrossRef: https://github.com/tdiesler/nessus-didcomm/issues/6
https://github.com/decentralized-identity/didcomm-messaging/blob/main/didcomm-logo.svg https://identity.foundation/didcomm-messaging/guide/ https://github.com/decentralized-identity/didcomm-messaging/blob/main/docs/guide-files
I might be missing this please let me know if it's in there.. Should the message be in the `data.json` or ~`data.jwe`~? Assuming json for now but this should be...
Hi, i would like to clarify the following: - `to` - OPTIONAL. Identifier(s) for recipients. MUST be an array of strings where each element is a valid [DID](https://www.w3.org/TR/did-core/) or [DID...
