-
Make it clear how this work is related to aries RFCs and didcomm wg at DIF.
-
This issue is to propose and formalize a work item under the DIDComm WG related to DIDComm Messaging over BLE. The process is described in the Work Item Life Cycle document - https://github.com/decent…
-
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…
-
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.
-
**Motivation**: Given that [Zero Trust architectures](https://www.nist.gov/publications/zero-trust-architecture) are becoming mandated by nation-states, most, if not all, Zero Trust architecture use c…
-
## Use Case
Consider the following situation:
- Alice has multiple `keyAgreement` keys of different types (X25519, P-256, P-384, etc.) in her DID DOC, possibly including some types (curves) that are…
-
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…
-
As been discussed in the Aries WG calls lately we want to move away from usage of unqualified dids. This issue focuses on usage of unqualified dids in didcomm, not in lower level objects (such as indy…
-
**Use case**
Let's assume Bob have multiple keys of different types. Alice also have multiple keys of different types (let's assume she has keys of same types for simplicity).
When Alice sends a mes…
-
Hello, Team
You are doing really great job!
I see that the main direction of project evaluation is related DIDComm messaging of the first version.
Do you have any plans regarding moving to the [sec…