-
The work being done on DIDComm Messaging in the DIF DIDComm WG is creating a set of conventions similar, but not identical, to the DIDComm first popularized in Hyperledger Aries.
Protocol definitio…
-
Just checking to see if AFJ currently supports this RFC at all or if it could:
https://github.com/hyperledger/aries-rfcs/tree/main/features/0335-http-over-didcomm
We (BC Wallet team) are looking a…
-
This is kind of related to #46: When looking through the example in Aries [RFC 0067](https://github.com/hyperledger/aries-rfcs/blob/main/features/0067-didcomm-diddoc-conventions/README.md), I got a bi…
-
Hey there,
I've read the DIDComm spec and I felt it would be good to get some code running to understand communication between participants.
However on the didcomm.org website, the link to the `…
-
The service property for didcomm is out of alignment with the current state of [didcomm](https://identity.foundation/didcomm-messaging/spec/#service-endpoint)
-
In https://identity.foundation/didcomm-messaging/spec/#protocol-identifier-uri:
> The version numbers embedded in PIURIs and MTURIs MUST follow familiar [semver](https://semver.org/) rules
Do we r…
-
In [Resolver DID Document Format](https://github.com/sovrin-foundation/sovrin/blob/2ba78fd5225d51f22ed92be1ea967dcda7abbc0f/spec/did-method-spec-template.html#L241) section of the specification, it re…
-
## Bug overview
Accordingly to https://didcomm.org/pickup/3.0/ protocol, the `https://didcomm.org/messagepickup/3.0/delivery` response should have a field named `recipient_did` in the response body…
-
-
DIDComm WG as begun to try and standardize these. I'm going to try and get some of them to review here, and provide links to any test-vectors or source that can be used to ensure compatibility.