-
When attempting to use did methods other than `did:key`, it is common that,
did !== publicKey.id && did === publicKey.controller
The controller is expanded here:
https://github.com/digitalbaz…
-
This issue was found by @mickrau.
An ACA-Py agent has been given a DIDDoc from a mobile agent that has both a recipientKey and a routingKey. When a message is sent by the ACA-Py agent to the mobile…
-
Context, @mattcollier and I were discussing "how do you get a capability invocation key instance from a DID Doc (so you can pass it to jsonld-signatures etc)", and currently we're doing it like this:
…
-
Does metadata about the DID Document (such as [when it was created](https://github.com/w3c/did-spec/pull/28), [updated](https://github.com/w3c/did-spec/pull/27), or [who it was signed by](https://gith…
-
From the discussion on #115
https://github.com/hyperledger/aries-rfcs/pull/115/files#r304002908
If the "magic" DID were a peer DID (or another non-globally resolvable namespace), there could be…
-
When `--public-invites` is enabled, using the admin interface to retrieve an invite URL returns a string that looks something like the following:
```
?c_i=
```
The encoded invite is correct; it on…
-
The current selection of filename seems to be introducing a lot of complexity. [From the DID Dir Spec](https://github.com/dhuseby/did-git-spec/blob/master/did-dir-spec.md#diddir-structure):
> The n…
-
Recently there's been discussion to update this work to be fully JWE compliant. One of the proposed solutions that's come up is to generate the following format:
```json
{
"protected": base64…
-
@llorllale @cywolf @tplooker I'm moving the discussion from the PR over here, so that the PR wouldn't linger.
-
Currently at the envelope level of did comm messages, when senders and recipients are referred to, public keys are used. For example in [RFC](https://github.com/hyperledger/aries-rfcs/tree/master/feat…