-
In prior work we implemented Step 1 of the DID Message type change over, enabling the receipt of DID messages using either message type format -- https or did:sov. For the next step in the process, p…
-
In adding the DIDComm Presentation Submission example, it wasn't clear to me why there was no comparable example for Presentation Definition. Should there be?
Also, it seems to me that the target …
-
Work was done previously to ensure that we support the receipt of either "did:sov:" or "https://didcomm.org" as the prefix of a message type.
We need to make absolutely sure that we can receive the n…
-
Per discussion on Slack, it has been suggested that we leverage the `initial-state` matrix parameter to represent service block info when unattached to a DID. This is common both in the invitation sta…
-
from #18
> DIDComm is lower level than the problem domain of this spec. It allows transmission of arbitrary content, so it is capable of carrying the data formats described here, in the same way y…
-
With AuthN Adopted, it is now time to discucss credential exchange / delivery.
There are Agents and Hubs, as well as HTTP, Identity Wallets, all will have opinion about how they would like to recei…
-
Test case:
```go
ariesCtx := createAriesContext()...
peerDID, err := ariesCtx.VDRIRegistry().Create(
"peer",
vdri.WithServiceEndpoint("http://example.com/didcomm"),
)
bits, err := peerDID.J…
-
In other popular secure messaging protocols such as [signal](https://signal.org/docs/) the ability to send a secure message from the first exchange is a critical feature, this is often referred to in …
-
Let use consider the case of using OIDC SIOP QR Codes, separate from potential DIDComm QR Codes.
OIDC SIOP does not have a concrete implementation yet: https://github.com/decentralized-identity/int…
-
There are currently two id properties in PE
- `id` - The Presentation Definition MUST contain an id property.
- The Input Descriptor Object MUST contain an `id` property.
I am sure some use-cas…