-
In DIDCommV1 we defined a semi-standard format for error reporting in [RFC 0035](https://github.com/hyperledger/aries-rfcs/tree/master/features/0035-report-problem). I think having a standard format w…
-
Hi,
According DID Spec KeyAgreement method is a pluggable specification, but I see we are trying force ECDH-1PU here despite a fact that method in examples forces direct ECDH.
-
[RFC 0360: `did:key` Usage](https://github.com/hyperledger/aries-rfcs/blob/main/features/0360-use-did-key/README.md) describes the usage of `did:key` DIDs as a replacement for base58 encoded ed25519 k…
-
Imagine you have the following service in the services section of Bob's DID Doc and this DID Doc was exchanged OOB with Alice:
```
{
"id": "did:example:bob#didcomm-1",
"type": "DIDCommMe…
awoie updated
3 years ago
-
My mental model of sending messages has been that they come from a key, and inbound messages are sent to a key (or several) at an endpoint. In a situation where I have an agent on my laptop, phone, an…
-
@awoie commented, in relation to references:
>add ISO 18013-5 ? NFC -> BLE/Wifi-Direct, QR Code -> BLE/Wifi-Direct
-
Currently, the spec requires a DID used to have an endpoint. Any DID without an endpoint would need to rotate to one that supports endpoints (including did:peer) to engage in DIDComm communication.
…
-
In WG Call 2020-06-08, we discussed using a detached compact jws as the `from_provenance` header attribute. The detached form makes the payload lighter by eliminating the double inclusion of the from …
-
This issue tracks a sister issue in Hyperledger Aries: https://github.com/hyperledger/aries-rfcs/issues/578
-
Opening this issue to track the unresolved problem of how to respond to a DIDComm message in which the `from` header contains a DID/DID-URL for methods that are self-certifying and do not depend on a …